Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kdlbs/using-agent-skills
Discover and choose the right Kandev agent skill for a task.
Passed 23 of 24 test cases with the skill, and 6 of 24 without it.
and 27 more in the full report
17 fixed6 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
An engineer needs to inspect the native Codex app-server protocol messages during local development. Which specific local workflow command should be used for this task?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies /codex-app-server-debug. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this as the routing map for Kandev's local skills. Prefer the repo's existing skills over importing adjacent upstream names.
Task arrives
|
|-- Standalone interview or stress test? --> /interview-me
|-- Feature/fix planning assumptions? -----> /interview-me (question only material unknowns)
|-- Large initiative with dependent unknowns? -> /interview-me decision-mapping reference
|-- Create/change/fix/publish Kandev plugin? -> /create-kandev-plugin plus /fix or /tdd as needed
|-- New feature or behavior-changing fix? --> /spec-driven-development
|-- Bug regression? ------------------------> /fix -> requirement/design check -> fix plan/work orders -> /tdd
|-- Running/debugging Kandev locally? ------> /debug
|-- Inspecting native Codex app-server protocol? -> /codex-app-server-debug
|-- Need focused context setup? ------------> /context-engineering
|-- Code change with test coverage? --------> /tdd
|-- Browser/E2E coverage? ------------------> /e2e
|-- Seed isolated product demo data? -------> /product-demo-seeding
|-- Record landing/product media? ----------> /product-demo-seeding -> /product-video-capture (always in that order)
|-- Frontend/UI change? --------------------> /mobile-parity plus /e2e as needed
|-- High-impact security boundary/concern? -> pause for a strong-model review per /planner-orchestration
|-- Test strategy or coverage gaps? --------> /tdd or /e2e in the current conversation
|-- Add debug logs? ------------------------> /debug
|-- Add Jira/Linear-style integration? -----> /add-integration
|-- Add/roll out/promote/graduate/remove a runtime feature flag or release toggle? -> /runtime-feature-flags
|-- Validate implementation? ----------------> /tdd plus exact task-defined tests/E2E
|-- Need local QA/review/simplification? ----> only on explicit user request or PR finding
|-- End-of-session retrospective? ---------> /retro (explicit request only)
|-- Improve skills/agents/commands? --------> /harness-improvement
|-- Record decisions/specification changes? -> /record
|-- Public docs impact? --------------------> /docs-maintainer -> /diagram-design when a visual helps
|-- Commit/push/PR? ------------------------> /commit -> /push or /pr
`-- Release/versioning? --------------------> /release
When runtime-flag work also matches new behavior or validation, compose
/runtime-feature-flags with /spec-driven-development and /tdd as needed.
test cases passed, vs 6 / 24 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.