Content
82%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 strong, highly actionable instruction-only skill: exact API payloads, deterministic grouping rules, and literal output templates leave nothing to interpretation. The notable gaps are the unaddressed pagination case and a mapping table with redundant rows.
Suggestions
Add a pagination step: after get_memories, if the result count equals page_size, continue fetching with subsequent page/cursor parameters (or raise page_size) so the 349-memories case in the example is actually reachable.
Collapse the duplicate mapping-table rows (technology/professional_details already fold into Tooling & Setup via the tooling_setup row) into one combined row to trim tokens.
State how to obtain active_user_id and active_project_id (e.g. from the platform context/session), since every filter payload depends on them but no source is given.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense operational instruction with no explanations of concepts Claude already knows (exact filter JSON, display templates, empty-state copy). Minor tightening is possible: the filter JSON blocks are repeated nearly verbatim across sections and the category mapping table duplicates two rows that map to Tooling & Setup. | 4 / 5 |
Actionability | Guidance is fully executable: exact `filters` JSON payloads, `page_size`/`top_k`/`rerank` values, deduplicate-by-ID rule, literal output templates with format specs (e.g. `<number>. [<type>] <content, 80 chars> (<date>) [mem0:<short_id>]`), and exact empty-state text to print. | 5 / 5 |
Workflow Clarity | Mode dispatch (all-projects → peek → full tour) and Steps 1–6 are clearly sequenced with an explicit empty-state branch; the operation is read-only so no destructive-validation cap applies. However, pagination is unaddressed — the example output itself shows 349 memories against `page_size=100/200` with no instruction to fetch subsequent pages, so the 'fetch ALL memories' step may silently miss most of the store. | 4 / 5 |
Progressive Disclosure | A single well-sectioned file with no bundle files (no references/, scripts/, or assets/ exist), so no nested references to score. At ~156 lines, the category mapping table and display-format templates are borderline candidates for a references/ file, but keeping one cohesive operational file is defensible. | 4 / 5 |
Total | 17 / 20 Passed |