trend-researcher
Expert market intelligence analyst specializing in identifying emerging trends, competitive analysis, and opportunity assessment. Focused on providing actionable insights that drive product strategy and innovation decisions.
25
7%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./market_researcher/skills/SKILL.mdQuality
Discovery
14%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 description reads like a professional bio or LinkedIn headline rather than a functional skill description. It relies heavily on buzzwords and abstract language without specifying concrete actions or when the skill should be triggered. It would be very difficult for Claude to reliably select this skill over others in a multi-skill environment.
Suggestions
Replace abstract language with concrete actions, e.g., 'Researches market size, analyzes competitor products, identifies industry trends, and generates SWOT analyses.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about market research, competitor analysis, industry trends, market sizing, or product opportunity assessment.'
Remove first-person-adjacent framing ('Expert... specializing in') and use third-person action verbs (e.g., 'Conducts market research, compares competitors, assesses market opportunities').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, buzzword-heavy language like 'emerging trends', 'competitive analysis', 'opportunity assessment', and 'actionable insights' without listing concrete actions. It reads more like a resume summary than a skill description with specific capabilities. | 1 / 3 |
Completeness | The 'what' is vague (no concrete actions listed) and there is no 'when' clause or explicit trigger guidance at all. The absence of a 'Use when...' clause caps this at 2 per the rubric, but the weak 'what' brings it down to 1. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'market intelligence', 'competitive analysis', 'emerging trends', and 'product strategy' that users might mention, but lacks common variations and natural phrasing users would actually say (e.g., 'market research', 'competitor comparison', 'industry analysis', 'SWOT'). | 2 / 3 |
Distinctiveness Conflict Risk | Terms like 'actionable insights', 'product strategy', and 'innovation decisions' are extremely generic and could overlap with many other skills related to strategy, research, business analysis, or product management. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a marketing brochure or role description rather than an actionable skill file. It extensively lists capabilities, methodologies, and frameworks that Claude already understands, without providing any concrete instructions, executable examples, templates, or specific workflows. The entire document could be replaced with a few focused, actionable sections that tell Claude exactly what to do when performing market research tasks.
Suggestions
Replace abstract capability lists with concrete, executable workflows—e.g., provide a specific template for a competitive analysis report with example output structure and actual steps to follow.
Add actionable examples: show a sample trend brief with real structure, a competitive landscape template, or a specific market sizing calculation with step-by-step instructions.
Remove explanations of well-known concepts (TAM/SAM/SOM definitions, adoption curves, SWOT analysis) that Claude already knows, and focus only on project-specific conventions or preferences.
Add validation checkpoints to workflows—e.g., 'After collecting signals, verify at least 3 independent sources confirm the trend before proceeding to impact assessment.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and padded with high-level descriptions of concepts Claude already knows (market sizing, SWOT analysis, TAM/SAM/SOM, adoption curves, etc.). The entire document reads like a consultant's capability brochure rather than actionable instructions. Nearly every bullet point explains well-known business concepts that add no value to Claude's context window. | 1 / 3 |
Actionability | The content is entirely abstract and descriptive—there are no concrete commands, executable code, specific prompts, templates, or copy-paste-ready outputs. It lists capabilities and frameworks at a high level ('Pattern Recognition: Statistical analysis and anomaly detection with machine learning') without ever showing Claude how to actually perform any of these tasks. | 1 / 3 |
Workflow Clarity | While there is a numbered 'Trend Identification Process' (7 steps), the steps are vague and lack any validation checkpoints, concrete tools/commands, or feedback loops. Steps like 'Automated monitoring across 50+ sources with real-time aggregation' provide no actionable guidance on what to actually do. No error handling or verification is present. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files, no clear navigation structure, and no progressive disclosure. All content is inline at the same level of detail (which is uniformly shallow), with no links to deeper resources or separation of overview from detailed guidance. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- OpenRoster-ai/awesome-openroster
- Commit
09aef5d
- 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.