diff --git a/skills/automate-me/SKILL.md b/skills/automate-me/SKILL.md
index 2cf7c7f..6888532 100644
--- a/skills/automate-me/SKILL.md
+++ b/skills/automate-me/SKILL.md
@@ -69,12 +69,12 @@ Author the skill per the **authoring-a-skill** playbook and Droid's skill anatom
 - Path: preserve an existing mode skill's category. For a new mode, use `.factory/skills/<handle>/<handle>-mode/SKILL.md` when the repo has an established personal category for that handle. Otherwise default to `.factory/skills/<handle>-mode/SKILL.md` in the project (or `~/.factory/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 the **authoring-a-skill** playbook's YAML rules. Keep `description` as one YAML scalar. Quote it or use `description: >-` with indented continuation lines when punctuation or wrapping requires it.
+- Frontmatter formatting: keep `description` as one YAML scalar. Quote it or use `description: >-` with indented continuation lines when punctuation or wrapping requires it.
 - Frontmatter `disable-model-invocation: true` by default. Opt out only if the user explicitly wants their mode to apply on every turn.
 
 ### 5. Iterate on prose
 
-Apply the **unslop** skill and the **authoring-a-skill** playbook's writing guidelines to every line.
+Apply the **unslop** skill and the prose rules in the **authoring-a-skill** playbook to every line.
 
 Show the draft to the user and take feedback. Expect multiple iterations. Cut ruthlessly. A mode skill is not a manual.
 
diff --git a/skills/reflect/SKILL.md b/skills/reflect/SKILL.md
index aee55fd..8426846 100644
--- a/skills/reflect/SKILL.md
+++ b/skills/reflect/SKILL.md
@@ -51,8 +51,8 @@ File each Backlog item to your team's devex or backlog tracker without waiting.
 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 **authoring-a-skill** playbook (`../poteto-mode/playbooks/authoring-a-skill.md`) and run its draft / test / iterate loop.
-- `tune description: <skill path>` (the skill exists but didn't trigger when it should have): hand to the **authoring-a-skill** playbook and run its description-optimization loop.
+- Substantive existing-skill edit (a new section, a new pattern table, more than ~10 lines): hand to the **authoring-a-skill** playbook (`../poteto-mode/playbooks/authoring-a-skill.md`).
+- `tune description: <skill path>` (the skill exists but didn't trigger when it should have): hand to the **authoring-a-skill** playbook.
 - `new skill: <kebab-name>`: hand creation to the **authoring-a-skill** playbook. Do not invent the shape ad hoc.
 
 Validate every touched skill with `/skills` before declaring done.