Content
65%Reviews 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 held back by repetition of the source/venue ladders and by keeping reference-worthy material inline instead of pointing to the existing bundle files. Adding a verification checkpoint and offloading venue/source-policy detail to the references would lift the weaker dimensions.
Suggestions
Add an explicit verification step to the workflow (e.g., 'Before producing the table, confirm each paper's relevance and that de-duplication against Zotero/local hits is complete') to satisfy the batch-operation feedback-loop expectation.
Replace the inline 'Venue Priority' tier lists and 'Source Selection'/'External Search Policy' detail with one-line pointers to venue-tiering.md and source-policy.md, signaling the existing reference files from the body.
De-duplicate the repeated zotero→obsidian→local→ieee→sciencedirect→acm→web ladder so it appears once, removing the conciseness drag from restating it in Retrieval Order, External Search Policy, and Step 1.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | It avoids explaining concepts Claude already knows, but the source ladder (zotero, obsidian, local, ieee, sciencedirect, acm, web) and venue tiers are restated across 'Retrieval Order', 'External Search Policy', and 'Step 1', so it could be tightened. | 2 / 3 |
Actionability | Concrete, specific instruction guidance throughout: enumerated source values, named venue tiers, a fixed paper-fact extraction list, an explicit output table with columns, and a defined synthesis/output ordering. | 3 / 3 |
Workflow Clarity | Steps 0a/0b/0c/1/2 are clearly sequenced, but this batch literature scan has no explicit validation or verification checkpoint before final output; per the rubric, batch operations missing feedback loops cap at 2 rather than 3. | 2 / 3 |
Progressive Disclosure | The body is well-sectioned and reference files exist (venue-tiering.md, source-policy.md, output-template.md, domain-taxonomy.md), but venue tiers and source policy are fully inline and the body never signals the reference files, so content that should be separate is inline and references are not clearly signaled. | 2 / 3 |
Total | 9 / 12 Passed |