Content
78%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, dense body with excellent token efficiency and copy-paste invocations, and a clear report-writing sequence. The main weakness is structural: the skill's essential synthesis rules live in an unbundled file referenced via a fragile cross-directory path, and one referenced output field (`citations`) is never shown.
Suggestions
Bundle the report-writing rules inside the skill (e.g., references/synthesis.md) and reference it with a path relative to SKILL.md, so the core workflow doesn't depend on sibling-directory layout.
Add the `citations` field to the output example so step 6 ('Cite with [N] format from citations') is grounded in the documented schema.
Add a brief finishing check to the report workflow (e.g., confirm every sub-query and named entity is either covered or listed in sections.gaps before completing).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and dense throughout: a compact invocation quick-reference, a depth table instead of prose, a skeletal output schema with inline comments, and terse anti-pattern bullets. Nothing re-teaches concepts Claude already knows; every section earns its place. | 5 / 5 |
Actionability | The Quick Reference gives copy-paste-ready invocations covering standard, comprehensive, quick, domain-scoped, and schema-constrained cases, plus a concrete depth/max_sources tuning knob. Not a 5: step 6 says 'Cite with [N] format from `citations`' but a `citations` field never appears in the output example, and the actual synthesis instructions are delegated elsewhere. | 4 / 5 |
Workflow Clarity | 'Writing the Report' gives a clear numbered 6-step sequence with each step mapped to its source field, and the gaps guarantee ('never silently dropped') acts as a soft completeness check. Not a 5: there are no explicit validation checkpoints (e.g., verifying every sub-query is covered before finishing), though the non-destructive nature means the missing-validation cap does not apply. | 4 / 5 |
Progressive Disclosure | The body is short and well-sectioned with clearly signaled references, but the bundle contains no reference files at all, and the core report-writing rules are delegated to '../wigolo/rules/synthesis.md' — a relative path outside the skill's own directory that does not resolve within this bundle. Navigation therefore depends on unverifiable sibling layout rather than a bundled references/ file, which is more than a minor organization gap. | 3 / 5 |
Total | 16 / 20 Passed |