Generate comprehensive market research reports (50+ pages) in the style of top consulting firms (McKinsey, BCG, Gartner). Features professional LaTeX formatting, extensive visual generation with scientific-schematics and generate-image, deep integration with research-lookup for data gathering, and multi-framework strategic analysis including Porter Five Forces, PESTLE, SWOT, TAM/SAM/SOM, and BCG Matrix.
80
72%
Does it follow best practices?
Impact
96%
2.00xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/market-research-reports/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent specificity, rich trigger terms, and a clearly distinctive niche. Its primary weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill over others. Adding that clause would elevate this from a good description to an excellent one.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for market research, industry analysis, competitive landscape reports, or consulting-style strategy documents.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and outputs: generating 50+ page market research reports, LaTeX formatting, visual generation, data gathering via research-lookup, and names five specific strategic frameworks (Porter Five Forces, PESTLE, SWOT, TAM/SAM/SOM, BCG Matrix). | 3 / 3 |
Completeness | The 'what' is thoroughly covered with specific capabilities and frameworks, but there is no explicit 'Use when...' clause or equivalent trigger guidance telling Claude when to select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'market research', 'consulting', 'McKinsey', 'BCG', 'Gartner', 'Porter Five Forces', 'PESTLE', 'SWOT', 'TAM/SAM/SOM', 'BCG Matrix', 'strategic analysis', and 'LaTeX'. These cover a wide range of terms a user requesting this type of work would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a very clear niche: comprehensive consulting-style market research reports with specific frameworks, LaTeX formatting, and named tool integrations. This is highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable with excellent executable examples and a well-structured workflow with proper validation checkpoints. However, it is severely bloated—much of the content explains frameworks and concepts Claude already knows, and detailed per-chapter content requirements should be offloaded to reference files rather than included inline. The skill would be significantly more effective at roughly one-third its current length.
Suggestions
Move the detailed chapter-by-chapter content requirements (Chapters 1-11 with their 'Content Requirements', 'Key Data Points', 'Analysis Frameworks' subsections) to the referenced `references/report_structure_guide.md` file, keeping only a brief table of chapters with page targets in the main SKILL.md.
Remove explanations of well-known frameworks (what PESTLE stands for, what Porter's Five Forces is, what TAM/SAM/SOM means) — Claude already knows these. Just reference them by name.
Cut the 'When to Use This Skill' section entirely — the overview already makes the use cases obvious, and listing 10 scenarios adds no value.
Consolidate the three separate checklists (Quality Review in Step 10, '50+ Page Validation', and Quality Standards) into a single concise checklist to eliminate redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 500+ lines. Massive amounts of content that Claude already knows (what PESTLE stands for, what TAM/SAM/SOM means, what Porter's Five Forces is, general writing guidelines like 'use active voice'). The section-by-section breakdown with 'Content Requirements' and 'Key Data Points' for every chapter is largely redundant information that any competent analyst would know. The 'When to Use This Skill' section lists 10 obvious use cases. | 1 / 3 |
Actionability | Provides fully executable bash commands for visual generation, complete LaTeX code examples for figures/tables/box environments, specific compilation commands, and concrete project structure. The code examples are copy-paste ready with realistic parameters and file paths. | 3 / 3 |
Workflow Clarity | Clear 5-phase workflow (Research → Analysis → Visual Generation → Writing → Compilation & Review) with explicit validation checklists at the end. Step 10 includes a comprehensive quality review checklist, and the compilation steps include the correct multi-pass LaTeX/BibTeX sequence. The troubleshooting section addresses common failure modes. | 3 / 3 |
Progressive Disclosure | References external files appropriately (FORMATTING_GUIDE.md, report_structure_guide.md, visual_generation_guide.md, etc.), but the main SKILL.md itself is monolithic with enormous inline content that should be in those referenced files. The detailed section-by-section breakdown (Chapters 1-11 with all their sub-requirements) belongs in the report_structure_guide.md reference, not inline. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (906 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 9 / 11 Passed | |
b58ad7e
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.