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 exactly when to select this skill over others. Adding trigger guidance would elevate this from a good to an excellent description.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user requests 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 specific 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'. These cover a wide range of terms a user requesting market research would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: consulting-style market research reports with specific frameworks, LaTeX formatting, and 50+ page scope. Unlikely to conflict with general document or analysis skills due to the very specific domain and output format. | 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 workflow clarity, providing executable commands, complete code examples, and thorough validation checklists. However, it is extremely verbose—much of the content describes what Claude already knows about market research, consulting frameworks, and report writing. The detailed chapter-by-chapter content requirements and quality standards could be dramatically condensed or moved to reference files, as the inline content bloats the skill far beyond what's needed.
Suggestions
Drastically reduce the chapter-by-chapter content requirements to brief bullet points or move them entirely to the referenced `report_structure_guide.md`—Claude knows what goes in a competitive landscape or risk analysis section.
Remove the 'When to Use This Skill' section entirely; Claude can determine applicability from the overview.
Move the detailed LaTeX formatting examples (box environments, table formatting, figure formatting) to the referenced `FORMATTING_GUIDE.md` and keep only a brief pointer in the main skill.
Consolidate the 'Quality Standards' section into the existing checklist rather than having both a standards section and a separate validation checklist covering overlapping concerns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 500+ lines. Extensively explains what market research reports are, when to use them, and lists obvious content requirements (e.g., 'Market definition and scope', 'Key stakeholders and their roles') that Claude already knows. The 'When to Use This Skill' section lists 10 obvious use cases. Page count targets, quality standards for writing, and detailed chapter-by-chapter content requirements are largely things Claude can infer from the task description. | 1 / 3 |
Actionability | Provides fully executable bash commands for visual generation, complete LaTeX code examples for box environments/figures/tables, specific file paths and project structure, and concrete compilation commands. The workflow steps include copy-paste ready commands for research-lookup and scientific-schematics integration. | 3 / 3 |
Workflow Clarity | Clear 5-phase workflow with 11 numbered steps, explicit sequencing (research before analysis, visuals before writing, compile then review). Includes validation checklists at the end covering structure, visuals, content quality, and technical quality. The LaTeX compilation sequence is correctly ordered with bibtex pass. Quality review has explicit checkboxes. | 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 a monolithic wall of content that should have much of its detail pushed to those reference files. The detailed chapter-by-chapter content requirements, visual specifications per section, and LaTeX formatting examples could all live in referenced files rather than 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 | |
25e1c0f
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.