Skills
Skills are the intent router below the SOP. The SOP says "load the matching skill"; each skill says what to do for that intent.
| Slice | Covers |
|---|---|
| Review and delivery | reviews, GitHub, PR/issue text, communication |
| Repo workflow and code intelligence | git/worktrees, semantic tools, clone research, cleanup scanners |
| Elastic and Kibana | domain overlay, Buildkite, labels, ownership, backports, kbn-standup |
| External tools and media | Google Workspace, flights, browser control, image generation |
Entry contract
Every skill should make four things obvious near the top:
| Field | Purpose |
|---|---|
Use when | routing triggers |
Do not use | boundaries and escalation |
First actions | mandatory first probes or skill loads |
Output | expected deliverable |
The description frontmatter is the primary routing signal. For non-manual skills, include the concise Use when trigger there; the body is only available after routing has already loaded the skill. Body Use when blocks may stay as detailed post-load applicability checks, but no routing trigger should exist only in the body. Keep descriptions specific, include non-obvious trigger words, and state repo/org constraints when a skill is gated.
Source map
| Surface | Path |
|---|---|
| Source | home/exact_dot_agents/exact_skills/ |
| Target | ~/.agents/skills/ |
| Entrypoint | SKILL.md in each skill folder |
| References | optional references/ under the skill folder |
Cross-skill hygiene
- Composition skills sanitize public GitHub text before drafting or posting.
k-compose-pr,k-compose-issue, andk-githubreuse review's GitHub context intake when output depends on existing PR/issue/comment context.- Generic skills own portable mechanics only. If a rule names an org, repo, product, team, label, bot login, CI instance, PR template, live-UI target, ownership policy, or release-note/backport rule, put it in a verified domain overlay or dedicated domain skill.
- Generic skills may dispatch to a domain overlay after verifying the target; they must not inline Elastic/Kibana or other domain defaults.
- GitHub issue worktrees prefer
,gh-worktree issue <owner/repo> <issue_number> --branch <branch-base-name>.
Credits
Four skills are adapted from Matt Pocock's mattpocock/skills (MIT-licensed). Attribution lives here rather than inline in each SKILL.md so it does not consume model context when the skill loads.
| Skill | Adapted from |
|---|---|
k-writing-great-skills | k-writing-great-skills |
k-codebase-design | k-codebase-design |
k-diagnosing-bugs | k-diagnosing-bugs |
k-prototype | k-prototype |