Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .agents/skills/automate-me/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ This skill orchestrates three others: an inline mining pass (see step 1), the av

### 0. Check for an existing skill

Look for `.agents/skills/*-mode/SKILL.md` and `~/.agents/skills/*-mode/SKILL.md` matching the user's handle. Keep each skill one directory below the skill root. If one exists, confirm intent with `AskQuestion` (unless they already said "update my skill" or similar):
Look recursively for `.agents/skills/**/*-mode/SKILL.md` and `~/.agents/skills/*-mode/SKILL.md` matching the user's handle. Mode skills can live in a personal category directory (`.agents/skills/<handle>/`), not only at the top level. If one exists, confirm intent with `AskQuestion` (unless they already said "update my skill" or similar):

- Update the existing skill (default for repeat runs)
- Start fresh (rare, ask why before doing it)
Expand Down Expand Up @@ -67,7 +67,7 @@ The **poteto-mode** skill shows the shape. Read it for granularity. Don't copy i

Use the available `skill-creator` skill to author the skill. Placement:

- Path: `.agents/skills/<handle>-mode/SKILL.md` in the project, or `~/.agents/skills/<handle>-mode/SKILL.md` if the user prefers a personal skill. Keep existing supported locations and avoid nested category directories.
- Path: preserve an existing mode skill's category. For a new mode, use `.agents/skills/<handle>/<handle>-mode/SKILL.md` when the repo has an established personal category for that handle. Otherwise default to `.agents/skills/<handle>-mode/SKILL.md` in the project (or `~/.agents/skills/<handle>-mode/` if the user prefers a personal skill).
- Handle: the user's first name or chosen identifier.
- Frontmatter `description`: trigger on their name + `/<handle>-mode` + "work in their style", not on generic keywords like "write code" or "review PR".
- Frontmatter formatting: follow `skill-creator`'s YAML rules. Keep `description` as one YAML scalar. Quote it or use `description: >-` with indented continuation lines when punctuation or wrapping requires it.
Expand Down
4 changes: 2 additions & 2 deletions .agents/skills/reflect/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,9 +54,9 @@ Never edit a skill under `plugins/cache/`. Before approval, show its destination
Follow each approved row's Routing exactly:

- Trivial existing-skill edit (a one-line bullet, a tightened sentence, a stale fact corrected): the parent does it directly.
- Substantive existing-skill edit (a new section, a new pattern table, more than ~10 lines): hand to the available `skill-creator` skill skill and run its draft / test / iterate loop.
- Substantive existing-skill edit (a new section, a new pattern table, more than ~10 lines): hand to the available `skill-creator` skill and run its draft / test / iterate loop.
- `tune description: <skill path>` (the skill exists but didn't trigger when it should have): hand to `skill-creator` and run its description-optimization loop.
- `new skill via create-skill: <kebab-name>`: hand creation to `skill-creator`. Do not invent the shape ad hoc.
- `new skill via skill-creator: <kebab-name>`: hand creation to `skill-creator`. Do not invent the shape ad hoc.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this token no longer matches what references/synthesizer.md emits (new skill via create-skill: in the existing-skill-first bullet and the Accepted table row). rename those three to skill-creator in this PR.


If your environment ships a SKILL.md validator, run it on every touched skill before declaring done.

Expand Down
4 changes: 2 additions & 2 deletions .agents/skills/reflect/references/synthesizer.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Apply each criterion to every finding:

- Durability: still true in 6 months once paths, SHAs, tool versions, and code shapes have changed.
- Specificity: broad enough to apply across tasks, precise enough that a future agent recognizes when to use it. Reject vague platitudes ("write good code") and hyper-specific facts ("`<specific-skill-name>` has 175 tokens at limit 80").
- Existing-skill-first: propose `new skill via create-skill:` only when no existing skill is a real home, the pattern recurs, and the topic deserves its own skill.
- Existing-skill-first: propose `new skill via skill-creator:` only when no existing skill is a real home, the pattern recurs, and the topic deserves its own skill.
- Convergence: findings echoed by 2+ reviewers carry higher confidence. Singletons must clear a higher bar on the other criteria.
- Decision-changing: a future agent does something different because of the edit, not just reads more text.
- Structural-mechanism check: route to Backlog when a lint rule, script, metadata flag, or runtime check already enforces the rule or could enforce it cheaply. Skill prose is for things mechanisms cannot enforce.
Expand All @@ -41,7 +41,7 @@ Output exactly the format below. No preamble, no narration. One sentence per cel
|---|---|---|
| <failure mode in a skill the parent used> | <change to that skill's body> | <skill path + section> |
| <skill existed but didn't trigger> | <tune the skill's description so it fires next time> | <tune description: <skill path>> |
| <new pattern, no existing skill is a real home> | <draft a new skill via create-skill> | <new skill via create-skill: <kebab-name>> |
| <new pattern, no existing skill is a real home> | <draft a new skill via skill-creator> | <new skill via skill-creator: <kebab-name>> |

One row per finding. The user approves row by row.

Expand Down
Loading