Conciseness

Every sentence carries project-specific facts (port arithmetic, lifecycle stages, namespace conventions) and assumes Claude's competence — no space is spent explaining what REST, MCP, or BM25 are. Lean throughout with no padded sections.

Actionability

Concrete, usable specifics abound: exact ports ("REST is the anchor at 3111... engine = N+46023 (49134)"), the env var `EMBEDDING_PROVIDER=local`, the viewer URL, and the `mem::*`/`api::*` namespaces. Not 5 because "configure a remote provider" and "their relevant options" are vague pointers without naming the variables or examples.

Workflow Clarity

This is a single-purpose architecture reference with no multi-step process; the body is unambiguous for its task and well-sequenced (primitives → retrieval → storage → ports → viewer → cross-references). The lifecycle (capture, compress, consolidate, forget) is stated in clear order, and no destructive or batch operations require validation checkpoints.

Progressive Disclosure

The body is under 50 lines with no need for external reference files (none exist in the bundle), and it is organized into clean single-topic sections. The 'See also' list clearly signals one-level-deep sibling skills (agentmemory-mcp-tools, agentmemory-rest-api, agentmemory-hooks, agentmemory-config).

Specificity

Enumerates several concrete facets — "the iii engine primitives it runs on, its storage model, ports, and the viewer" — plus "how memory is stored or retrieved end to end". Not 5 because it describes topical coverage rather than concrete actions and omits surfaces like REST/MCP (minor gaps).

Completeness

Clearly answers what ("How agentmemory is built, the iii engine primitives it runs on, its storage model, ports, and the viewer") and explicitly when via a concrete "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" clause. Third-person voice throughout.

Trigger Term Quality

Natural phrases users would say are present: "how memory is stored or retrieved", "extending the system", "how agentmemory works under the hood". Not 5 because common synonyms like "recall", "remember", or "architecture" are missing.

Distinctiveness Conflict Risk

Names the specific system (agentmemory) and scopes triggers to it (storage/retrieval reasoning, extending, under-the-hood questions), creating a clear niche with minimal overlap risk against generic memory or config skills.