Conciseness

The ~40-line body is lean: five short sections, no explanation of REST/HTTP basics, and the one positioning sentence ("REST is agentmemory's primary surface. MCP is a bridge on top of it.") is project-specific knowledge Claude cannot infer. Every section earns its place; no over-explanation was found that would justify anchor 4.

Actionability

"curl -fsS http://localhost:3111/agentmemory/livez", the POST /remember and POST /smart-search examples with full JSON bodies, the concrete auth header ("Authorization: Bearer $AGENTMEMORY_SECRET"), and the 201/200/400 status conventions are copy-paste ready and cover the common cases (liveness, save, recall). Matches anchor 5.

Workflow Clarity

The Quick start sequences a liveness check before save/recall — an explicit validation checkpoint — and status-code conventions give feedback on outcomes. However, there is no error-recovery loop (e.g., 401 → AGENTMEMORY_SECRET not set; connection refused → wrong --port), which keeps it at anchor 4 ("most checkpoints present; minor validation gaps") rather than 5. It is a reference-style skill with no destructive or batch operations, so the workflow-clarity cap at 3 does not apply.

Progressive Disclosure

The body is a clean overview that defers bulk content appropriately ("The full endpoint list with methods lives in REFERENCE.md") with clearly signaled, one-level-deep references plus sibling-skill "See also" pointers. However, no bundle files exist (no references/, scripts/, or assets/ directories) and REFERENCE.md is not present anywhere in the bundle, so the skill's core payload — the full endpoint list — is unreachable. The structure itself is anchor-5 quality; the dangling primary reference is more than a minor organization gap but the in-file organization and signaling are solid, placing it between anchors 4 and 5, at 4.

Specificity

"The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server" names the domain precisely and conveys one concrete action (HTTP calls to the memory server), but never enumerates what the API actually does (e.g., save, search, recall memories). It is above anchor 2 ("names the domain but actions are minimal or generic") because the protocol surface and role are sharply defined, but below anchor 4 because no specific operations are listed.

Completeness

The "what" is explicit ("The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server") and the "when" is explicit with three concrete trigger conditions in the "Use when..." clause. Both are answered clearly with concrete trigger phrases, matching the anchor-5 example's structure; anchor 4 would require the "when" to be less explicit, which it is not.

Trigger Term Quality

Trigger phrases "calling agentmemory over HTTP", "when MCP is unavailable and you need a fallback", and "integrating a host that does not speak MCP" are natural things a caller would say in this domain. Good coverage of agentmemory/HTTP/REST/MCP/fallback, but a few natural variants ("endpoints", "curl", "REST API reference") are missing, so it falls short of anchor 5's comprehensive synonym coverage.

Distinctiveness Conflict Risk

The description carves out a clear niche (REST/HTTP) and explicitly disambiguates from the sibling MCP path ("when MCP is unavailable and you need a fallback", "a host that does not speak MCP"). Minimal conflict risk with agentmemory-mcp-tools or agentmemory-config; it is clearly distinguishable.