Content
75%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 tight, well-structured instruction skill: it gives a clear research-then-build workflow with concrete section templates and table schemas, without padding or explaining known concepts. The main improvements are a validation step for research currency and one filled-in example to anchor output quality.
Suggestions
Add a validation step after research, e.g. 'Before writing, confirm pricing and feature claims against at least two current sources; note the as-of date on the card' — this would lift workflow_clarity to 5.
Include one worked example (e.g., a filled Quick Comparison row and one objection/response pair) so reps and the model have a concrete quality bar for tone and depth, lifting actionability.
Trim the 'Keep it scannable' rationale and the Further Reading link (or fold it into a references/ file) — each is a small token cost with little guidance value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient — it wastes no tokens explaining what a battlecard is or how web search works, and the section templates are the actual deliverable structure, so they earn their place. Not 5: minor trimmable material remains ('Sales reps need to reference this during calls' justification, 'Format for easy printing or sharing in Notion/Confluence', and a Further Reading link of marginal value); not 3: there is no genuinely unnecessary explanation. | 4 / 5 |
Actionability | Concrete, executable guidance for an instruction-only skill: exact section names, table schemas (Quick Comparison, Objections & Responses), placeholder-driven templates, and a prioritized research list with named sources (G2, Capterra, Reddit). Not 5: everything is a placeholder — no single filled-in example row or worked snippet showing the expected quality of a 'Where We Win' bullet; not 3: the guidance is specific and immediately actionable, not pseudocode-level hints. | 4 / 5 |
Workflow Clarity | Clear three-step sequence — (1) research competitor via web search (with sub-checklist), (2) build the battlecard from templates, (3) keep it scannable and save as markdown. Not 5: there are no validation checkpoints (e.g., verify competitor pricing/claims are current before writing, or sanity-check the comparison table against research); not 3: this is a non-destructive, non-batch task so the validation cap does not apply, and the sequence itself has no gaps. | 4 / 5 |
Progressive Disclosure | Well-organized single-file skill with no bundle files (references/, scripts/, assets/ do not exist), so all content appropriately lives inline; sections are clearly headed and navigable. Not 5: the body is ~72 lines, just over the under-50-lines exception, and the lone 'Further Reading' external link is weakly justified; not 3: structure is good and nothing that belongs in a separate file is inlined. | 4 / 5 |
Total | 16 / 20 Passed |