Content
86%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, highly actionable body: executable invocation examples for every mode, a concrete depth/source table, and a clean pointer to synthesis rules. The main issues are the redundant split between 'Anti-Patterns' and 'When NOT to use', and the unexplained MCP-sampling-available output branch.
Suggestions
Merge the 'Anti-Patterns' and 'When NOT to use wigolo-research' sections into one section — both cover the same single-shot/simple-lookup exclusion and the duplication wastes tokens.
Briefly state what the output looks like when MCP sampling IS available, since 'When MCP sampling is unavailable (common case)' implies an alternative result shape that is never described.
Clarify the relationship between the 'highlights' and 'key_findings' brief fields (both appear in the output schema and the description) so the report-writing steps map unambiguously onto the brief.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean — JSON quick-reference examples, a compact depth table, a commented output schema, and terse numbered steps — with no re-teaching of concepts Claude knows. However, the 'Anti-Patterns' bullet 'DON'T use for single-URL lookups — use fetch instead' and the 'When NOT to use' section 'You want a single-shot search result... use search' redundantly cover the same not-for-this guidance and could be merged into one section. | 4 / 5 |
Actionability | Provides copy-ready invocations for all depth levels plus domain-scoped and schema-output variants, a concrete 'max_sources' cap of 50, a 6-step report-writing procedure keyed to specific brief fields, and explicit alternative tools (fetch, agent, search) for each anti-pattern. | 5 / 5 |
Workflow Clarity | The report-writing sequence is clearly ordered and the guarantee that gaps are 'never silently dropped' acts as a completeness check. But 'When MCP sampling is unavailable (common case)' implies an alternative output shape that is never described, leaving an unaddressed branch in the workflow. | 4 / 5 |
Progressive Disclosure | A short (~80 line), well-sectioned overview that keeps detail in one-level-deep, clearly signaled references (wigolo/rules/synthesis.md and the sibling skill docs) while inlining only the 'Quick version' of the report procedure — easy to navigate with no buried or nested references. | 5 / 5 |
Total | 18 / 20 Passed |