mcpField
W
write-agentmemory-skill

write-agentmemory-skill

github.com/rohitg00Agent workflows30.0k10.9k installsUpdated today
Repository

About write-agentmemory-skill

A style and maintenance guide for authoring agentmemory skills. It defines a consistent file layout, content structure, and generated-facts workflow to keep skills concise and synchronized with source code.

Key features

  1. 01Tiered skill file layout
  2. 02Required section order and content rules
  3. 03Frontmatter and description guidance
  4. 04Generated reference data
  5. 05Generator and CI drift checks

Use cases

  1. 01Create a new agentmemory skill
  2. 02Move dense facts into reference files
  3. 03Check skills for generated-data drift

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rohitg00/agentmemory --skill write-agentmemory-skill

After installing, type/write-agentmemory-skillin Claude Code to confirm it loaded.

Bundled filesTROUBLESHOOTING.md

Details

From the project README

agentmemory skills follow one tiered format so they stay skimmable, accurate, and current. Match it exactly.

Directory layout

plugin/skills/<name>/
  SKILL.md      (required, under 100 lines)
  REFERENCE.md  (optional, dense facts; auto-generate data tables)
  EXAMPLES.md   (optional, worked transcripts)
  TROUBLESHOOTING.md (generated support file)

SKILL.md rules

  • Frontmatter: name, description, optional argument-hint, and user-invocable. Set user-invocable: true only for skills the user runs as a slash command; reference and knowledge skills are false.
  • Description is two sentences and the only thing the agent sees when deciding to load the skill. Sentence one states the capability. Sentence two starts "Use when" and lists concrete triggers. Keep it distinct from sibling skills, under 1024 chars, third person.
  • Body order: Quick start (one concrete example), Why (the governing principle), Workflow (numbered steps with decision gates), Anti-patterns (a WRONG vs RIGHT callout for the top mistake), Checklist, See also (cross-link siblings), Reference or Troubleshooting pointer.
  • Stay under 100 lines. Move dense facts to REFERENCE.md and examples to EXAMPLES.md.
  • Keep supporting files inside the skill directory so each skill works when installed separately. Link TROUBLESHOOTING.md; the generator copies shared recovery instructions into each skill root.

Keep it current

Facts that exist in source (tool names and parameters, REST endpoints, env vars, connect adapters, hook events) are generated, never hand-typed. Edit the source, then run npm run skills:gen. CI runs npm run skills:check and fails on drift, so generated tables cannot fall behind the code.

Style

No external or competitor product names. No emojis. No em-dashes. No filler. State the thing and stop.

Checklist

  • Description has a "Use when" sentence with real triggers.
  • SKILL.md is under 100 lines.
  • No time-sensitive claims and no duplicated troubleshooting block.
  • Concrete example present; generated facts come from the generator.
  • Cross-links resolve and go one level deep.

Comments

Markdown supported