plugins/plugin-eval/skills/plugin-eval/SKILL.md
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 dev skill", "why did this score that way", "what should I fix first", "measure the real token usage of this skill", or "what should I run next?".
npx skillsauth add openai/plugins plugin-evalInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this as the beginner-friendly umbrella entrypoint for local Codex skill and plugin evaluation.
plugin-eval start <path> --request "<user request>" --format markdown
plugin-eval analyze <path> --format markdown, then initialize a benchmark and show the setup questions needed to tailor benchmark.jsonplugin-eval analyze <path> --format markdownplugin-eval analyze <path> --format markdownplugin-eval analyze <path> --format markdownplugin-eval explain-budget <path> --format markdownplugin-eval measurement-planplugin-eval start <path> --request "What should I run next?" --format markdown../improve-skill/SKILL.md.../metric-pack-designer/SKILL.md.~/.codex/skills/<skill-name> firstskills/<skill-name> directory.plugin-eval/benchmark.jsonGive me an analysis of the game dev skill.Evaluate this skill.Evaluate this plugin.Why did this score that way?What should I fix first?Explain the token budget for this skill.Measure the real token usage of this skill.Help me benchmark this plugin.What should I run next?plugin-eval start <path> --request "Evaluate this skill." --format markdown
plugin-eval start <path> --request "Give me a full analysis of this skill, including benchmark setup." --format markdown
plugin-eval analyze <path> --format markdown
plugin-eval explain-budget <path> --format markdown
plugin-eval measurement-plan <path> --format markdown
plugin-eval init-benchmark <path>
plugin-eval benchmark <path> --dry-run
plugin-eval benchmark <path>
At a Glance, Why It Matters, Fix First, and Recommended Next Step.why content terse and easy to skim.plugin-eval start command that routes it, and the first local workflow command behind it.../evaluate-skill/SKILL.md.../evaluate-plugin/SKILL.md.../../references/chat-first-workflows.md../../references/technical-design.md../../references/evaluation-result-schema.mddevelopment
Use when the user wants to spin up / create / launch / provision a DigitalOcean droplet (or "a remote dev box on DO") and connect to it from Codex as a remote SSH workspace.
data-ai
Search through Microsoft Teams chats or channels, triage unread or recent activity, draft follow-ups, and manage Planner tasks through connected Teams data.
tools
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
development
SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.