skill-author
The skill-author Claude Code skill generates or updates SKILL.md documentation for new or modified Mnemon skills. Use this skill when a curator proposal, user request, or approved lifecycle change requires a concrete skill definition draft that includes YAML frontmatter, trigger description, boundary section, and procedural steps. The skill writes drafts to a proposals directory without modifying active skill structures, leaving formal lifecycle management to the skill-manage tool.
git clone --depth 1 https://github.com/mnemon-dev/mnemon /tmp/skill-author && cp -r /tmp/skill-author/harness/loops/skill/skills/skill-author ~/.claude/skills/skill-authorSKILL.md
# skill-author Use this skill when a curator proposal, user request, or approved lifecycle change needs a concrete `SKILL.md` draft. ## Boundary This skill authors skill content only. It does not decide lifecycle placement and does not activate, stale, archive, restore, or delete skills. Write drafts under: ```text $MNEMON_SKILL_LOOP_PROPOSALS_DIR ``` Approved lifecycle placement is applied later with `skill-manage`. ## Procedure 1. Confirm the target skill id is hyphen-case: lowercase letters, numbers, and `-`. 2. Confirm the skill captures a reusable procedure, not project facts, preferences, credentials, raw transcripts, or one-off task context. 3. Draft a complete `SKILL.md` with: - YAML frontmatter containing `name` and `description` - a short trigger-oriented description - a clear boundary section - a concise procedure section - safety or validation notes only when they change behavior 4. Keep the skill focused. Prefer one workflow per skill. 5. Use project-neutral language. Do not embed current branch names, temporary tokens, credentials, private URLs, or task-specific facts. 6. Save the draft as a proposal artifact such as: ```text $MNEMON_SKILL_LOOP_PROPOSALS_DIR/<skill-id>.SKILL.md ``` 7. Leave `skills/active`, `skills/stale`, `skills/archived`, and host skill surfaces unchanged unless the user explicitly asks to use `skill-manage` after approval. ## Quality Checklist - The description tells the host when to use the skill. - The body teaches reusable judgment or procedure the model would not reliably infer from the current task alone. - The content is short enough to load on demand. - The skill avoids duplicated policy already covered by `GUIDE.md`. - The draft is safe to review before activation.
Analyze Mnemon harness eval reports, classify outcomes, and extract improvement evidence.
Turn stable Mnemon harness eval findings into scoped project, loop, adapter, docs, or eval asset improvements.
Design a scenario-driven Mnemon harness eval with target, hypothesis, HostAgent, loop configuration, evidence, and rubric.
Execute or supervise a planned Mnemon harness eval run in an isolated HostAgent workspace.
Manage project-scoped Mnemon goal state, evidence, verification, completion, blockers, and host goal links.
Recall long-term memory from Mnemon when GUIDE.md indicates that prior memory may help the current task.
Maintain prompt-facing working memory by editing MEMORY.md when GUIDE.md indicates that durable information should be kept.
Start a low-frequency review of skill evidence and canonical skill lifecycle state.