Conciseness

Every line carries non-obvious information (e.g., 'REST is the anchor at 3111. Streams = N+1 (3112), viewer = N+2 (3113), engine = N+46023 (49134). `--instance N` shifts the whole block by N*100') with zero padding and no explanation of concepts Claude already knows.

Actionability

Guidance is concrete and usable — port arithmetic, the 'new capability is a new function plus a trigger' rule, the mem::/api:: namespace conventions, and the viewer URL — but it is descriptive architecture rather than executable steps, leaving minor gaps against the fully-executable anchor.

Workflow Clarity

This is a single-purpose architectural reference under 50 lines with an unambiguous purpose (explaining how agentmemory works end to end); the simple-skill exception applies, and the lifecycle sequence (capture, compress, consolidate, forget) is stated coherently.

Progressive Disclosure

Well-organized short sections with no need for external references, and the 'See also' list points one level deep to clearly-named sibling skills (agentmemory-mcp-tools, agentmemory-hooks, agentmemory-config) for the detailed surfaces.

Specificity

The description lists several specific coverage areas — 'the iii engine primitives it runs on, its storage model, ports, and the viewer' — rather than generic claims, but they are topics rather than concrete actions, leaving minor gaps versus the comprehensive anchor.

Completeness

Both parts are explicit: the 'what' enumerates the subsystems covered, and the 'when' opens with 'Use when reasoning about... when extending the system, or when answering how agentmemory works under the hood' — three concrete trigger scenarios matching the top anchor.

Trigger Term Quality

Natural phrases like 'how agentmemory is built', 'memory is stored or retrieved end to end', 'extending the system', and 'under the hood' match what a user would actually say; a few common variations (e.g., 'extend agentmemory', 'how memory works') are missing, so it falls just short of the comprehensive anchor.

Distinctiveness Conflict Risk

'Under the hood' / 'how it is built' framing carves a clear niche apart from the sibling surface skills (mcp-tools, rest-api, hooks), but the memory-retrieval trigger could plausibly fire for those closely related siblings, so minor overlap risk remains.