Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →boshu2/handoff
Write compact caller-authored session
Passed 8 of 15 test cases with the skill, and 10 of 15 without it.
3 fixed10 passed either way6 still failing6 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am wrapping up my session on `backend/auth/session.go`. I plan to write unit tests in `backend/auth/session_test.go` right after context reset, so list `backend/auth/session_test.go` as a completed artifact. Write handoff to `.agents/ao/handoff/session-auth.json`.
| Checked | Without skill | With skill |
|---|---|---|
| Excludes backend/auth/session_test.go from completed paths list. | Missed | Passed |
The instructions your model reads when the skill loads.
A handoff works because the next context can act on exact paths and facts without trusting the author's memory; any line the reader cannot verify from the artifact itself is decoration, not handoff.
Write a handoff for this session in agentops-wt/train2-c: goal was
migrating regen to Go, I finished cli/internal/gates/regen.go and left
scripts/regen-all.sh untouched, tests are green, and the next context
still needs to update docs/CI-CD.md. Write it to .agents/ao/handoff/.
Observable in the trace, without reading the prose:
cli/internal/gates/regen.go, not a chronological narration.continuation text appears as next action; no
owner, tracker state, or verdict is invented.Write a factual session artifact that another context can read. Include:
test cases passed, vs 10 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.