Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/_dispatch
Core router. Always active. Auto-invokes matching skill before every response. Runs confusion protocol on high-risk ambiguity.
Passed 12 of 19 test cases with the skill, and 6 of 19 without it.
and 4 more in the full report
7 fixed7 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We added a new exported HTTP handler function to our public SDK library. Which rule applies?
| Checked | Without skill | With skill |
|---|---|---|
| Invokes the document skill for modified public interfaces. | Missed | Passed |
The instructions your model reads when the skill loads.
CRITICAL: When accessing harness data, run HARNESS_DIR=$(epic-harness path) first. NEVER use .harness/ in the project directory.
You have access to the following skills. Invoke the matching skill BEFORE responding or taking action. Even a 1% chance of relevance means you should invoke it.
| Context Signal | Invoke Skill |
|---|---|
| New feature implementation starting | tdd |
| Test failure, error, or unexpected behavior | debug |
| Auth, DB, API, infra, or secrets code touched | secure |
| Loops, queries, rendering, or data processing code | perf |
| File > 200 lines or high cyclomatic complexity | simplify |
| Public API/function added or changed | document |
| Before completing /go or /ship | verify |
| User wants to commit changes | commit |
| Context window > 70% used | context |
| User request is vague, unfocused, or presents a solution without a clear problem | discover |
| User shares code for review, mentions code smells, or asks to refactor/analyze | episteme → analyze_code + suggest_refactorings → feed results into go:plan mode |
User invokes /reflect, asks about AI usage quality, "am I using AI well", "thought amplifier", or requests AI usage self-assessment | reflect |
| Session start (project has harness-mem psychographic node) | Call mem_query type=psychographic → apply 5-dimension profile to all subsequent skill dispatch |
Orchestration run active ($HARNESS_DIR/orchestrator/run.json exists with status "running") | orchestrate |
| Agent tool output received with inter-agent message | orchestrate |
User runs /intervene | orchestrate |
| 요구사항 정의 필요, 스펙 없음 | spec |
| 빌드/구현 시작, 스펙 승인됨 | go |
| 리뷰/감사/테스트 필요 | audit |
| PR 생성 / CI / 배포 준비 | ship |
Users can still type legacy command names. Map them:
/spec → invoke skill spec directly/go → invoke skill go directly/audit → invoke skill audit directly/ship → invoke skill ship directly/discover → invoke skill discover directly/intervene → invoke skill orchestrate (intervene mode)test cases passed, vs 6 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.