Content
67%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.
The body is a well-structured, largely executable runbook: pinned-revision review with a user-approval gate, concrete install/start commands, and documented MCP tool interfaces. Its main weaknesses are the circular "When to Use" filler, generic Limitations boilerplate, and the absence of any failure-recovery guidance around the install and server-start steps.
Suggestions
Replace the circular "When to Use" sentence with concrete invocation conditions (e.g., "Use when the user asks to save, recall, or search project knowledge across sessions").
Trim the boilerplate Limitations lines and keep only skill-specific caveats (e.g., the commit-pin trust note and Node v18+ requirement).
Add brief failure-recovery guidance for the install/start steps (e.g., what to check if `npm ci` or `npm run compile` fails, or how to verify the MCP server is reachable before using the tools).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The setup and tool sections are lean and command-driven, but the body carries filler: "This skill is applicable to execute the workflow or actions described in the overview" is circular padding, and parts of the Limitations section ("Do not treat the output as a substitute for environment-specific validation, testing, or expert review") read as boilerplate. This matches anchor 3 ("mostly efficient but includes some unnecessary explanation or could be tightened") better than 4, where only minor trim instances would remain. | 3 / 5 |
Actionability | The setup gives concrete, executable commands — a pinned git clone with commit hash, `npm ci`, `npm run compile`, and `npm run start-server my-project $(pwd)` — and each MCP tool documents args with a usage example. It falls short of 5 because of unresolved placeholders (`<approved-agent-memory-directory>`, `<project_id>`, `<absolute_path_to_target_workspace>` in the primary command) and no example payload for `memory_write` content. | 4 / 5 |
Workflow Clarity | The three-step setup (review pinned revision → install approved tree → start server) is clearly sequenced with an explicit checkpoint ("Show the findings and exact commit, then wait for explicit user approval") and a re-review guard on changing the pin. It is not a 5 because there is no error-recovery feedback loop for the install/start steps (e.g., what to do if `npm ci` or `npm run compile` fails). | 4 / 5 |
Progressive Disclosure | The body (~96 lines) is well-organized into distinct sections (Prerequisites, Setup, Capabilities, Dashboard, Limitations) with no bundled reference files to disclose; the inline MCP tool reference is short enough to belong in SKILL.md. It is not a 5 because the ~30-line tool catalog and dashboard section could be split out, and there are no signaled references for deeper material even though the skill points to an external repository. | 4 / 5 |
Total | 15 / 20 Passed |