Content
76%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 highly actionable, well-structured instruction skill: exact command syntax, per-command numbered procedures, a concrete data schema, and explicit storage layout. Its main weakness is absent validation/feedback loops for the JSON database mutations (status changes, won/lost transitions, note appends), which caps workflow clarity.
Suggestions
Add validation checkpoints to database-mutating workflows: verify the prospect exists before updating, confirm the JSON parses after each save, and confirm with the user before irreversible won/lost transitions.
Include an error-recovery path for common failures (unknown ID/domain, prospects.json missing or corrupted) so Claude knows to re-check and retry rather than proceed blindly.
Trim the second ASCII mockup in '/geo prospect pipeline' or the duplicated list output, since both illustrate the same rendering style and partially repeat the same information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Efficient and free of concept over-explanation, but the two long ASCII output mockups and the full example JSON record duplicate information and could be trimmed, keeping it below the lean anchor 5 while clearly above anchor 3's unnecessary explanations. | 4 / 5 |
Actionability | Copy-paste-ready command table, numbered orchestration steps per command, exact storage paths, a concrete mkdir command, and a specific decision threshold ("If score < 55…") fully cover the common cases for an instruction-only skill. | 5 / 5 |
Workflow Clarity | Steps are clearly sequenced per command, but every workflow mutates the prospects.json database with no validation checkpoints — no existence check before updates, no post-save verification, and no confirmation before semi-destructive won/lost transitions — which per the scoring notes caps database-operation workflows at 3. | 3 / 5 |
Progressive Disclosure | No bundle files exist, and the body is well organized into clearly navigable sections (Commands, Data Structure, Orchestration Instructions, Storage, Stage Definitions) with only minor organization gaps such as interleaving output examples with instructions. | 4 / 5 |
Total | 16 / 20 Passed |