CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

market-research-report-generator

Generates professional market research reports by analyzing business intent, decision levels, and conducting multi-source data retrieval (Web, PubMed, Clinical Trials).

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/market-research-report-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The core Workflow section is strong: a clearly sequenced, actionable five-step process with real reference files and an executable script. The body is dragged down by substantial generic template boilerplate (When to Use, Key Features, Dependencies, Implementation Details, Output Contract, Failure Handling) that adds tokens without skill-specific value, plus a fabricated Quick Validation expected-output.

Suggestions

Remove or collapse the generic template sections (When to Use, Key Features, Dependencies, Implementation Details, Required Inputs, Output Contract, Validation and Safety Rules, Failure Handling) that restate the Workflow or say nothing skill-specific; keep only the Input/Output/Workflow/Quality Rules core.

Fix the Quick Validation section: either describe the actual `--help` output or replace it with a real verification (e.g., a dry-run command against a sample query) whose expected output matches reality.

Use a portable example path instead of "20260316/scientific-skills/Others/market-research-report-generator" so the Example Usage commands are copy-paste runnable from the skill directory.

DimensionReasoningScore

Conciseness

Roughly half the body is generic template filler: "Use this skill when the request matches its documented task boundary", a Key Features section repeating the frontmatter description verbatim, "See `## Workflow` above for related details", and boilerplate Dependencies/Required Inputs/Output Contract sections. Several padded sections add no skill-specific value, matching anchor 2 rather than the mostly-efficient anchor 3; it is above anchor 1 because the Workflow core is genuinely useful.

2 / 5

Actionability

The workflow gives mostly executable guidance: a concrete command "python scripts/research_orchestrator.py '[\"query1\", \"query2\"]'", "generate 5-7 core questions", "Generate 3-5 distinct search queries", a named 5-part report structure, and citation examples ("According to Gartner..."). Minor gaps remain (the non-portable example path "20260316/scientific-skills/Others/..." and a Quick Validation expected-output that --help would not actually print), keeping it below anchor 5.

4 / 5

Workflow Clarity

A clear five-step sequence (Intent Analysis -> Decision Level -> Question Generation -> Data Collection -> Synthesis -> Report) with most checkpoints present: the "Do NOT make up data" rule, cross-referencing conflicts, a Quick Validation pre-run, and a Failure Handling section. Not anchor 5 because the Quick Validation checkpoint's "Expected output format" does not match what `--help` actually produces, weakening the validation loop.

4 / 5

Progressive Disclosure

References to `references/intent_classification.md` and `references/decision_level.md` (and the script) are real files, clearly signaled in context, and one level deep. Structure is good with descriptive section headers; minor gaps come from inline boilerplate sections that dilute the overview role rather than content misplacement, so anchor 4 rather than the well-split anchor 5.

4 / 5

Total

14

/

20

Passed

Description

58%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description gives a clear, fairly specific picture of what the skill does, with distinctive source names (PubMed, Clinical Trials). Its main weaknesses are the complete absence of a "Use when..." trigger clause and thin coverage of natural synonyms users would actually say.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for market research, industry analysis, a competitive landscape review, or due-diligence research on a market or product area."

Include natural synonyms and variations users would say ("market analysis", "industry report", "competitive landscape", "market size", "CAGR") to improve trigger-term coverage.

Briefly hint at the deliverable shape (e.g., structured Markdown report with executive summary and strategic recommendations) to sharpen the "what" without adding length.

DimensionReasoningScore

Specificity

"Generates professional market research reports by analyzing business intent, decision levels, and conducting multi-source data retrieval (Web, PubMed, Clinical Trials)" lists several concrete actions with named data sources. Coverage has minor gaps (e.g., no hint of the report structure or analysis types), so it sits at anchor 4 rather than 5, and clearly above the 1-2-action anchor 3.

4 / 5

Completeness

The "what" is clear (generate market research reports via intent/decision-level analysis and multi-source retrieval), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"market research reports" is a natural phrase users would say, but common variations and synonyms are missing ("market analysis", "industry analysis", "competitive landscape", "due diligence", "market size"). Some relevant keywords exist, matching anchor 3 rather than the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

The market-research-report niche combined with PubMed and Clinical Trials retrieval is mostly distinct with only minor overlap risk against generic research or report-writing skills. It is not a fully clear niche with distinct triggers (anchor 5) because triggering rests on a single phrase with no "when" guidance.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/market-research-report-generator/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.