Skip to content

Job pack · harness

Skill pack

Progressive-disclosure expertise. Write descriptions that trigger. Distill from traces. Do not flood the constitution.

When: You are packaging how an agent should do a job for a repo or a team.

Description first (what + when). Body as a playbook. references/ on demand. Trigger-test five phrasings.

GET /api/canon/jobs/skill-pack?format=md

Matching skill · Write a skill

Playbooks

Doctrine to load

Refuse

  • Unowned prompt. The policy lives in a framework black box you cannot diff, test, or revert.
  • Context hoarding. Raw HTML, full CI logs, six PDFs, entire JSON envelopes stuffed 'just in case'. The goal is the first thing forgotten.
  • Memory as unfiltered logs. Session transcripts stuffed into the next session. The user cannot inspect or delete them.

Checklists

Skill quality

  • name + description say what it does and when to use it, with trigger contexts.
  • SKILL.md under ~500 lines. Depth in references/, deterministic work in scripts/.
  • Imperative voice. Explain why. No ALWAYS/NEVER wallpaper.
  • One job. No overlap that makes the model pick none.
  • Does not duplicate AGENTS.md. The constitution points; the skill teaches.

Recipes

Default corpus

anthropic-skillsaddy-agent-skillsopenai-skillscontext-engineering-skills