Skills
A skill is a set of instructions the agent loads only when a task calls for it. Name one, or describe the situation. Action skills stop at a defined point and ask; read-only skills change nothing.
Memory
Read and write your Obsidian vault with the agent's own file tools. New notes go only to the inbox.
- brain-setupCreate a vault from the template or connect yours, with the config edits shown as a diff first."set up the vault", "create a vault"
- brain-searchAnswer from your notes only, citing each note's path; inbox claims marked unreviewed."what did we decide about X", "what do we know about X?"
- brain-captureSave a decision, lesson or reference to the inbox, secrets redacted."remember this", "capture the decision"
- brain-reviewSummarize the inbox and promote, merge or reject only the notes you name."review the brain inbox", "what is in the inbox"
- brain-gardenA vault health report: stale notes, broken links, bad frontmatter, duplicates, orphans."clean up the vault"
- brain-compileSynthesize several notes on one topic into one compiled note in the inbox, sources listed.
Engineering
From a spec to a merge verdict, with evidence on every finding and an approval before every edit that matters.
- specInterview you, inspect the repository, write a spec and plan, hand implementation to a fresh session.
- code-reviewReview a diff, commit or PR: P0–P3 findings and a merge verdict, with an independent reviewer for this session's code."review the last commit", "review my changes"
- audit-to-backlogParallel specialist reviews with file-and-line evidence, deduplicated into a backlog."audit this repo", "audit the code"
- implement-backlogWork through backlog items in small batches, validated, reviewed and committed only when green."fix everything with multiple agents", "implement the backlog"
- pr-cycleMerge the base in, resolve conflicts, review, fix approved findings, run the gates, update the PR body."merge fresh dev in"
- fix-prAddress every unresolved review thread, asking before each edit, commit, push and resolution."fix the PR comments", "address the review comments"
- bug-triageSeverity, reproduction, ranked hypotheses, root cause, mitigation and a regression test."we have a bug in production"
- deploy-checklistA repository-specific GO/NO-GO checklist with post-deploy checks and rollback."can we deploy"
Project hygiene
Keep docs, instructions and plans in step with the code.
- docs-syncCheck docs against code, scaffold missing pieces, refresh the current state, report drift."are the docs up to date"
- project-baselineCheck a repository against a baseline of engineering practices and propose what is missing."what is the repo missing", "check the project standard"
- instruction-reviewPropose a minimal, evidence-backed diff to CLAUDE.md or AGENTS.md."improve CLAUDE.md", "review the project instructions"
- plan-statusMeasured open, done and blocked counts, and the open decisions as A/B/C questions."what is the status", "what is left"
Session and communication
End sessions cleanly, see what is used, talk to clients plainly.
- session-retroCheck for unpushed work and running tasks, give the status block, keep a few lessons, apply only what you approve."wrap up the session", "is everything done"
- skill-usageHow often each skill fired in local session history, with a keep, merge or remove verdict."which skills work"
- client-replyA reply to a client in plain business language, in your voice. Drafts only, never sends."reply to the client", "write to the client"
Conventions
Stack- and file-specific rules that load only when the work matches.
- typescript-conventionsComposition, small single-purpose functions, tests for new functions, formatter and import aliases.
- nextjs-conventionsSchema-validated input, Server Components by default, typed Server Actions, forward-only migrations.
- testing-conventionsPin the contract in tests with absolute-instant fixtures and partial module mocks.
- error-handling-conventionsCause chains, typed results, one API error envelope, no log-and-throw, no empty catch.
- monitoring-conventionsAlert on symptoms, avoid alert fatigue, link runbooks, separate health from readiness.
- comments-conventionsNo comment by default, and the few that earn their place kept current.
- defensive-coding-conventionsDefect classes that ship past review: mismatched conditions, unisolated webhooks, unvalidated JSON.
The contract of every skill, with what it writes and where it asks, is in the functional specification. Agents the skills dispatch are on the agents page.