write-agentmemory-skill

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

call the REST API directly:

1. Set `AGENTMEMORY_URL` to the daemon base URL (default `http://localhost:3111`).
2. The REST API requires a bearer credential

and do not read local credential files.

Audit 0.4.1 · source sha 2e5491e1aacf · 31 Oct 2026Report an issue or request a re-scan

• Publisherrohitg00 GitHub userOwner of the repository this skill is read from
• Source folderrohitg00/agentmemory/plugin/skills/write-agentmemory-skillThe exact folder we audited
• LicenceApache-2.0As the repository states it
• Commit pinned for this verdict2e5491e1aacfA new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

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

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

## 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](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.

Excerpt, first 2,407 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

1. 2026-10-31
   ✓SAFE B 89 / 100

   first audit · source 2e5491e1aacf

Questions about write-agentmemory-skill

• github.com/rohitg00/agentmemory/tree/main/plugin/skills/write-ag — the audited source at commit 2e5491e1aacf and every finding aboveObserved · 31 Oct 2026

Spotted something wrong? Report a correction · Methodology