메뉴
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.
| name | write-agentmemory-skill |
| description | 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. |
| user-invocable | false |
agentmemory skills follow one tiered format so they stay skimmable, accurate, and current. Match it exactly.
plugin/skills/<name>/
SKILL.md (required, under 100 lines)
REFERENCE.md (optional, dense facts; auto-generate data tables)
EXAMPLES.md (optional, worked transcripts)
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.../_shared/TROUBLESHOOTING.md, never inlined.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.
No external or competitor product names. No emojis. No em-dashes. No filler. State the thing and stop.
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.
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.
agentmemory configuration, environment variables, ports, and feature flags. Use when enabling a feature, changing ports, setting an API key, configuring auth, or explaining why a feature is off by default.
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.
Map of every agentmemory MCP tool, what each does, and its parameters. Use when choosing which memory tool to call, when a tool name or argument is unclear, or when answering what agentmemory can do via MCP.
The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server. Use when calling agentmemory over HTTP, when MCP is unavailable and you need a fallback, or when integrating a host that does not speak MCP.