josedowski/axioma/gentle-ai-bench
Claude Code and agent skill by josedowski/axioma
- community
Checking that the SKILL.md file is still in the repository.
Trigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution.
Install
npx vskill@latest install josedowski/axioma/gentle-ai-benchSKILL.md
The same SKILL.md was published earlier as josedowski/axioma/gentle-ai-bench.
Activation Contract
Load when touching bench/ in gentle-ai, adding or changing a journey, changing a product semantic a journey might pin, or diagnosing a bench failure in CI's Unit Tests job.
Hard Rules
go test ./benchvalidates corpus declarations only. It does NOT execute journeys. The only driven proof is building the harness and the product binary and running the harness against it; a greengo test ./benchclaims nothing about execution.- Reproduce CI, do not guess invocations: read the Unit Tests step in
.github/workflows/ci.ymland copy its exact build andgentle-ai-bench run --binary ...commands. Use--only <journey-id>to drive one journey. - Journey IDs are unique across every
journeys_*.gofile. The collision guard fails loudly naming both files; pick an unused ID by reading the corpus, never reuse a retired one. - Every
executetransition must carry a runnable command; the dead-execute guard fails the run otherwise. - When a ratified product semantic changes, grep the corpus for journeys pinning the OLD behavior before shipping. The corpus is a second test surface beyond unit tests; a journey asserting the defect keeps the defect green.
dead_endprintsn/aunless the run actually measured one. Never fabricate a value to move the column.- A
by_designexemption costs a shape from the closed vocabulary plus a verified quote of the product's own next-action text. If the quote no longer tells the operator what to do, it is a defect wearing an exemption. - Prefer a NEW
journeys_*.gofile when the shared ones are owned by open PRs; bump the core journey-count pin in the same change.
Execution Steps
- Read the corpus area you touch and the CI invocation before writing.
- Author or adapt the journey; update its title, step names, and comment to say WHY the expectation holds (cite the issue or ratified decision).
- Run
go test ./...inbench/for declarations, THEN the driven harness for execution; both results go in the PR body. - On semantic changes, list the journeys you checked for stale pins.
Output Contract
PR evidence includes the driven-mode summary line (completed / unsupported / failed counts) from a locally built binary, not only go test output.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/gentle-ai-bench/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/josedowski/axioma/gentle-ai-bench)