Skip to content
Marketplace

write-agentmemory-skill

by rohitg00

The house format and rules for writing or updating an agentmemory skill. Use when adding a new skill, restructuring an existing one, or reviewing a skill contribution for consistency.

Overview

SKILL.mdRead at 007a1a7

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)

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.
  • Cross-references link one level deep only. Shared recovery steps live in ../_shared/TROUBLESHOOTING.md, never inlined.

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.

Files 1 file

Install it by hand

Deska runs this for you, for every agent you pick. To run it yourself in a terminal:

npx skills add rohitg00/agentmemory --skill write-agentmemory-skill

More from rohitg00

  • rememberrohitg00Save an insight, decision, or learning to agentmemory's long-term storage with searchable concept tags. Use when the user says "remember this", "save this", "note that", "don't forget", or wants to preserve knowledge for future sessions.13.2K installs on skills.sh0
  • recallrohitg00Search agentmemory for past observations, sessions, and learnings about a topic using hybrid BM25 plus vector plus graph search. Use when the user says "recall", "what did we do about", "did we ever", "have we seen", or needs context from past sessions.13.1K installs on skills.sh0
  • forgetrohitg00Delete specific observations from agentmemory after showing them and getting explicit confirmation. Use when the user says "forget this", "delete memory", "remove that note", or wants to scrub specific data for privacy.13K installs on skills.sh0
  • session-historyrohitg00Show what happened in recent past sessions on this project as a clean timeline. Use when the user asks "what did we do last time", "session history", "past sessions", or wants an overview of previous work.13K installs on skills.sh0
  • commit-contextrohitg00Trace 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.12.9K installs on skills.sh0
All skills by rohitg00