rohitg00/agentmemory

write-agentmemory-skill

The house format and rules for writing or updating an agentmemory skill.

Zobacz źródło

Jak używać

  1. Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
  2. W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
  3. Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/rohitg00/agentmemory --skill write-agentmemory-skill

Przed rozpoczęciem

  • Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
  • Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

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

Directory layout

text
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.

Powiązane zadania

z tego samego repozytorium

Więcej Skills

Wszystkie Skills
rohitg00
Społeczność

agentmemory-agents

How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.

instalacje
3
GitHub Stars
29,9 tys.
Aktualizacja
25 paź
rohitg00
Społeczność

agentmemory-architecture

How agentmemory is built, the iii engine primitives it runs on, its storage model, ports, and the viewer. Use when reasoning about how memory is stored or retrieved end to end, when extending the system, or when answering how agentmemory works under the hood.

instalacje
3
GitHub Stars
29,9 tys.
Aktualizacja
25 paź
rohitg00
Społeczność

agentmemory-hooks

The agentmemory plugin hooks that capture observations automatically across the agent session lifecycle. Use when explaining how memory gets captured without manual saves, when debugging missing observations, or when tuning what gets recorded.

instalacje
3
GitHub Stars
29,9 tys.
Aktualizacja
25 paź
rohitg00
Społeczność

commit-context

Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.

instalacje
3
GitHub Stars
29,9 tys.
Aktualizacja
25 paź