Content
78%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A largely excellent, actionable configuration guide with concrete commands and a clear check-first diagnostic workflow. Its main weaknesses are a dangling REFERENCE.md reference (the file is absent from the bundle), some duplicated gating explanations, and an overstuffed step 4 in the connection workflow.
Suggestions
Ship REFERENCE.md alongside SKILL.md (or inline the recognized-variable list) so the 'full recognized-variable list' pointer in the Reference section resolves to a real file in the bundle.
Split step 4 of the connection checklist into separate sub-steps for auth secret resolution, custom ports, and the HTTPS/loopback rule so each concern is individually actionable.
State the LLM-provider gating once (in Defaults worth knowing) and trim the redundant restatement in the Optional richer memory section to save tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with tool-specific facts and assumes competence (no explanations of what MCP or env vars are), but the LLM-provider gating is stated twice ("A provider key in the environment does nothing until AGENTMEMORY_LLM_PROVIDER names that provider" and again under Defaults) and step 4 is a run-on paragraph, so it is efficient with minor trimming possible rather than fully lean. | 4 / 5 |
Actionability | Guidance is fully executable: concrete commands (`agentmemory status`, `node dist/cli.mjs status`, `agentmemory connect codex --with-hooks`, `--port <N>`), exact variable names and values, a copy-paste `env` block, and the `agentmemory://status` resource cover the common configuration and diagnostic cases. | 5 / 5 |
Workflow Clarity | "Check the connection first" gives a clear numbered diagnostic sequence with a validation-first step, an explicit failure branch ("If it fails, check Node.js 20+ and `agentmemory status`"), and a decision point for duplicate connections; step 4 crams auth, ports, and HTTPS rules into one paragraph, leaving minor sequencing gaps versus the 5-anchor. | 4 / 5 |
Progressive Disclosure | Sections are well organized and the variable list is appropriately deferred rather than inlined, but the primary deferred target "The full recognized-variable list lives in REFERENCE.md" is dangling — no REFERENCE.md or references/ directory exists in the bundle, so the flagged deep content is unreachable; that is more than the 4-anchor's 'minor organization gaps'. | 3 / 5 |
Total | 16 / 20 Passed |