Help us improve
Share bugs, ideas, or general feedback.
From plugin-eval
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.
npx claudepluginhub robinebers/converted-plugins --plugin plugin-evalHow this skill is triggered — by the user, by Claude, or both
Slash command
/plugin-eval:evaluate-pluginThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when the target is a plugin root with `.codex-plugin/plugin.json`.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Use this skill when the target is a plugin root with .codex-plugin/plugin.json.
plugin-eval start <plugin-root> --request "<user request>" --format markdown first so the user sees the routed local path.plugin-eval analyze <plugin-root> --format markdown.Fix First before drilling into manifest findings, nested skill findings, and code or coverage details.plugin-eval compare.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?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
../../references/chat-first-workflows.md