Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →giuseppe-trisciuoglio/specs-explore
Explore codebase before committing to a change. Phase executor skill for specs.explore command.
Passed 3 of 8 test cases with the skill, and 2 of 8 without it.
and 1 more in the full report
4 fixed4 passed either way12 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
Investigate adding gRPC endpoint handlers for internal microservice communication without specifying a spec flag. What artifact path should be recorded in the status summary?
| Checked | Without skill | With skill |
|---|---|---|
| The status report sets the artifact field to 'none'. | Missed | Passed |
The instructions your model reads when the skill loads.
Investigate the codebase, think through problems, compare approaches, and return a structured analysis. Only create exploration.md when --spec is provided.
The orchestrator will give you:
--spec path (optional)--lang framework (optional)Parse what the user wants to explore:
Read relevant code to understand:
INVESTIGATE:
├── Read entry points and key files
├── Search for related functionality (Grep)
├── Check existing tests (Glob)
├── Look for patterns already in use
└── Identify dependencies and coupling
If there are multiple approaches, compare them:
test cases passed, vs 2 / 8 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.