메뉴
Display a terminal scorecard of benchmark results showing pass rates, scores by difficulty, and per-test breakdowns. Use when the user asks about benchmark results, scores, or wants to see how their SDK performed.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Initialize a new agentic-usability benchmark pipeline project. Use when setting up a new SDK benchmark, creating a config.json, or starting a new evaluation project.
Launch an interactive shell inside a microsandbox for debugging. Supports bare mode, executor setup, or judge setup with optional test case scaffolding.
Run the full evaluation pipeline (execute, judge, report) for an SDK usability benchmark. Use when running a complete benchmark end-to-end, resuming an interrupted pipeline, or checking pipeline status.
Execute benchmark test cases in sandboxed environments with AI agents. Spins up microsandbox containers for each test case and extracts solutions.
Export a benchmark pipeline as a zip file for sharing or archiving. Excludes cache and large snapshots.
Generate SDK usability test cases by exploring source code. Use when creating benchmark test suites, generating test cases for an SDK, or when the user wants to create evaluation scenarios.
| name | report |
| description | Display a terminal scorecard of benchmark results showing pass rates, scores by difficulty, and per-test breakdowns. Use when the user asks about benchmark results, scores, or wants to see how their SDK performed. |
| argument-hint | [project-directory] [--json] [--run runId] |
| allowed-tools | Bash(agentic-usability *) Read Glob |
Display the benchmark scorecard for the pipeline.
agentic-usability report -p $ARGUMENTS
--json: Output raw structured JSON instead of the colored table--run <runId>: Show results for a specific run (default: latest)results/<runId>/
report.json # Aggregate scorecard
<targetName>/<testId>/
judge.json # Per-test judge scores
generated-solution.json # Agent's solution
agent-notes.md # Agent's working notes
| Dimension | Range | What it measures |
|---|---|---|
apiDiscovery | 0-100 | Found correct SDK endpoints/methods? |
callCorrectness | 0-100 | API calls constructed correctly? |
completeness | 0-100 | All requirements handled? |
functionalCorrectness | 0-100 | Code runs and produces correct output? |
overallVerdict | boolean | Solution works? (pass/fail) |
The report aggregates these across all test cases and breaks them down by difficulty (easy/medium/hard).
Runs are stored as subdirectories in results/ containing run.json:
{ "id": "run-2026-04-25T10-30-00-000Z", "createdAt": "...", "targets": [...], "testCount": 15, "label": "..." }
To list all runs, look for results/*/run.json files.
Present the results to the user. If they want deeper analysis, suggest using the insights skill.
For detailed file inventory, see pipeline-guide.md.