Conciseness

The body is lean and assumes Claude's competence: "REST is agentmemory's primary surface. MCP is a bridge on top of it" and short sections (Quick start, Auth, Conventions, See also) with zero padding or explanations of concepts Claude already knows. Every token earns its place, matching the anchor "Lean and efficient; assumes Claude's competence". Not a 4 because there are no instances of over-explanation to trim.

Actionability

Fully executable, copy-paste-ready curl commands cover the common cases: livez check, bearer-auth POST to `/agentmemory/remember` and `/agentmemory/smart-search`, plus a working secret-loading idiom (`agentmemory_secret="${AGENTMEMORY_SECRET:-$(cat "$HOME/.agentmemory/secret")}"`). Matches the anchor "Fully executable; copy-paste ready code or commands; specific examples cover the common cases". Not a 4 because there are no gaps in the shown commands; not below 5 since the endpoints shown are concrete and complete.

Workflow Clarity

A coherent sequence is present (liveness check → load secret with an explicit guard `test -n "$agentmemory_secret" || exit 1` → save → recall), and status-code conventions ("Save returns `201`, reads return `200`, validation errors return `400`") act as implicit checkpoints. Matches "Clear sequence with most checkpoints present; minor validation gaps". Not a 5 because error recovery is delegated to a TROUBLESHOOTING.md link that does not exist, leaving a missing feedback loop; not a 3 because the sequence and the secret guard are explicit, and this is not a destructive/batch operation requiring the level-3 cap.

Progressive Disclosure

Sections are well-signaled, but the only deep-dive pointers — "See [TROUBLESHOOTING.md](TROUBLESHOOTING.md)" and "The full endpoint list with methods lives in REFERENCE.md" — point to files that do not exist anywhere in the bundle (no references/, scripts/, or assets/ directories). Scoring against the actual bundle structure, navigation is broken: the reference surface the skill defers to is missing. Matches the anchor "Minimal structure; ... references are buried" in effect, since the promised reference layer is absent. Not a 3 because the problem is not unclear signaling but dangling references; not a 1 because the body itself is well organized with no nested chains.

Specificity

The domain is clearly named — "The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server" — with one concrete action implied ("calling agentmemory over HTTP"), but no specific operations (remember, search, endpoints) are listed. Matches the anchor "Names domain and 1-2 concrete actions, but not comprehensive". Not a 4 because it describes what the surface is rather than several specific actions it enables; not a 2 because the domain is named precisely, not minimally.

Completeness

Both questions are answered explicitly: what — "The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server"; when — "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", with three concrete trigger phrases. Matches the anchor "Clearly and explicitly answers both what AND when with concrete trigger phrases". Not a 4 because the 'when' clause is already fully explicit and multi-scenario, not merely adequate.

Trigger Term Quality

Good natural keyword coverage: "calling agentmemory over HTTP", "MCP is unavailable and you need a fallback", "integrating a host that does not speak MCP" — phrases a user would plausibly say in exactly those situations. Matches "Good keyword coverage; a few natural terms missing". Not a 5 because terms like "endpoints", "curl", or the concrete operation names (save/recall) that a user might naturally use are absent; not a 3 because the included terms are natural, not jargon-only.

Distinctiveness Conflict Risk

It carves out a clear niche and actively disambiguates from the sibling MCP skill via the conditions "when MCP is unavailable and you need a fallback, or when integrating a host that does not speak MCP". Matches "Clear niche with distinct triggers; minimal conflict risk". Not a 4 because the MCP-vs-REST boundary is stated in the description itself, leaving little overlap ambiguity.