local-evaluate-plugin-cf170bc7
/local-evaluate-plugin-cf170bc7
Evaluate a local Codex plugin in engineer-friendly language. Use when the user says "evaluate this plugin", "audit this plugin", "why did this score that way", "what should I fix first", "help me benchmark this plugin", or asks for a plugin-wide report before comparing versions.
- Author
- creativekamrul ↗
- Repository
- ai-dev-toolkit ↗
- Licence
- MIT
- Last repository change
- 01.11.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Evaluate a local Codex plugin in engineer-friendly language. Use when the user says "evaluate this plugin", "audit this plugin", "why did this score that way", "what should I fix first", "help me benchmark this plugin", or asks for a plugin-wide report before comparing versions.
Triggers from the description
Original author description
Evaluate a local Codex plugin in engineer-friendly language. Use when the user says "evaluate this plugin", "audit this plugin", "why did this score that way", "what should I fix first", "help me benchmark this plugin", or asks for a plugin-wide report before comparing versions.
How it works
- Workflow
- Chat Requests To Recognize
- Commands
- Reference
SKILL.md preview
--- name: local-evaluate-plugin-cf170bc7 description: Evaluate a local Codex plugin in engineer-friendly language. Use when the user says "evaluate this plugin", "audit this plugin", "why did this score that way", "what should I fix first", "help me benchmark this plugin", or asks for a plugin-wide report before comparing versions. --- # Evaluate Plugin Use this skill when the target is a plugin root with `.codex-plugin/plugin.json`. ## Workflow 1. Treat "Evaluate this plugin." as the default entrypoint. 2. If the request comes in as natural chat language, use `plugin-eval start <plugin-root> --request "<user request>" --format markdown` first so the user sees the routed local path. 3. Run `plugin-eval analyze <plugin-root> --format markdown`. 4. Read `Fix First` before drilling into manifest findings, nested skill findings, and code or coverage details. 5. If the plugin contains multiple skills, summarize the strongest and weakest ones explicitly. 6. If the user wants measured usage, switch to "Help me benchmark this plugin." and use the starter benchmark flow. 7. If the user wants trend data, compare two JSON outputs with `plugin-eval compare`. ## Chat Requests To Recognize - `Evaluate this plugin.` - `Audit this plugin.` - `Why did this score that way?` - `What should I fix first?` - `Help me benchmark this plugin.` - `What should I run next?` ## Commands ```bash plugin-eval start <plugin-root> --request "Evaluate this plugin." --format markdown plugin-eval analyze <plugin-root> --format markdown plugin-eval start <plugin-root> --request "What should I run next?" --format markdown plugin-eval compare before.json after.json plugin-eval report result.json --format html --output ./plugin-eval-report.html plugin-eval init-benchmark <plugin-root> plugin-eval benchmark <plugin-root> --dry-run ``` ## Reference - `../../references/chat-first-workflows.md`
Files in this package (5)
- SKILL.md 2 KB
- TOOLKIT-LICENSE-EVIDENCE.json 1 KB
- TOOLKIT-PROVENANCE.json 1 KB
- TOOLKIT-UPSTREAM-LICENSE.txt 1 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named local-evaluate-plugin-cf170bc7.
Database snapshot: 13.11.2026 · package version fc4e5c151790 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100local-evaluate-skill-c8912f39
Evaluate a local Codex skill in engineer-friendly terms. Use when the user says "evaluate this skill", "give me an analysis of the game dev skill", "audit this skill", "why did this score that way", "what should I fix first", or asks for a skill-specific report before benchmarking it. - 100local-plugin-eval-85338f56
Help engineers evaluate a local skill or plugin, explain why it scored that way, show what to fix first, measure real token usage, benchmark starter scenarios, or decide what to run next. Use when the user says things like "evaluate this skill", "give me an analysis of the game… - 100evaluate-plugin
Evaluate plugin quality. Use when user says \"evaluate plugin\", \"review plugin quality\", \"score my plugin\", \"check plugin\", \"rate plugin\". - 100evaluate-plugin
Audit a local Claude Code bundle that has .claude-plugin/plugin.json: validate the manifest, lint hooks, check mcp/lsp servers, monitors, and agents, then rank fixes. Use when the user says "audit this", "validate the manifest", "lint the hooks", "why did it score that way", or "benchmark this". - 100cc-plugin-eval
Analyze, lint, and check a local Claude Code add-on or capability, explain the result, and rank the top fixes first. Use when the user says "audit this", "why did it score that way", "what should I fix first", "validate the manifest", "lint the hooks", or "benchmark the real token usage". - 100evaluate-plugin-batch
Batch evaluate every skill in a plugin and produce a plugin-level report. Use when auditing an entire plugin's quality or validating before a release.