Feature Research Skill
Use this skill to perform competitive feature analysis. You will research specific functionality across competitor products and compare them to [YOUR PRODUCT].
Inputs
The user will provide:
- Message: A description of what features or functionality to analyze
- URLs: One or more competitor URLs to research (documentation, product pages, changelogs, etc.)
Research Workflow
Step 1: Analyze Competitor URLs
For each URL provided:
- Use web search and fetch_web_pages to gather information about the specified features
- Extract: feature capabilities, limitations, pricing implications, and user experience details
- Note the source URL for every claim
Step 2: Research Your Product's Equivalent Functionality
- Search your product's documentation at
YOUR_PRODUCT_DOCS_URL for equivalent or related features
- Look for: feature parity, unique differentiators, gaps, and areas where your product exceeds competitors
- Be thorough — check multiple relevant doc pages based on your product's structure
Step 3: Compare (if multiple URLs provided)
- Identify common capabilities across competitors
- Note differentiating features unique to each product
- Highlight where your product leads, matches, or trails
Output Format
Return your analysis in this structured format:
---BEGIN FORMAT---
Feature Analysis: [Topic from user's message]
Date: [Current date]
TL;DR: [1-2 sentence summary of key findings]
[COMPETITOR NAME] (source: [URL])
- [Feature 1]: [description, capabilities, limitations]
- [Feature 2]: [description, capabilities, limitations]
- [Notable absence]: [features they don't have that are relevant]
[COMPETITOR NAME 2] (source: [URL]) — if multiple URLs provided
- [Feature 1]: [description, capabilities, limitations]
- [Feature 2]: [description, capabilities, limitations]
[YOUR PRODUCT] (source: YOUR_PRODUCT_DOCS_URL)
- [Feature 1]: [description, capabilities, limitations]
- [Feature 2]: [description, capabilities, limitations]
- [Unique capabilities]: [things your product has that competitors don't]
COMPARISON SUMMARY
- [Feature] — Competitor 1: [status] | Competitor 2: [status] | [YOUR PRODUCT]: [status]
- [Feature] — Competitor 1: [status] | Competitor 2: [status] | [YOUR PRODUCT]: [status]
(Use ✅ has feature, ⚠️ partial/limited, ❌ missing, ❓ unclear)
KEY INSIGHTS
- [insight 1 — what this means for product decisions]
- [insight 2]
- [insight 3]
GAPS & OPPORTUNITIES
- [gap 1 — where your product could improve or differentiate]
- [gap 2]
RISKS
- [risk 1 — competitive threats or market shifts to watch]
- [risk 2]
---END FORMAT---
Guidelines
- Be evidence-driven: cite the source (URL/section) for every important claim
- Separate facts from assumptions from opinions
- If information is unclear or unavailable, say so rather than guessing
- Focus on the specific features/functionality the user asked about
- Keep the analysis actionable and decision-ready
After Completing Analysis
create a markdown file in reports/feature_research with your findings, and create a PR.
1---2name: feature-research3description: Does research on competitive features and creates a report.4---56# Feature Research Skill78Use this skill to perform competitive feature analysis. You will research specific functionality across competitor products and compare them to [YOUR PRODUCT].910## Inputs1112The user will provide:131. **Message**: A description of what features or functionality to analyze142. **URLs**: One or more competitor URLs to research (documentation, product pages, changelogs, etc.)1516## Research Workflow1718### Step 1: Analyze Competitor URLs19For each URL provided:20- Use web search and fetch_web_pages to gather information about the specified features21- Extract: feature capabilities, limitations, pricing implications, and user experience details22- Note the source URL for every claim2324### Step 2: Research Your Product's Equivalent Functionality25- Search your product's documentation at `YOUR_PRODUCT_DOCS_URL` for equivalent or related features26- Look for: feature parity, unique differentiators, gaps, and areas where your product exceeds competitors27- Be thorough — check multiple relevant doc pages based on your product's structure2829### Step 3: Compare (if multiple URLs provided)30- Identify common capabilities across competitors31- Note differentiating features unique to each product32- Highlight where your product leads, matches, or trails3334## Output Format3536Return your analysis in this structured format:3738---BEGIN FORMAT---3940Feature Analysis: [Topic from user's message]41Date: [Current date]4243TL;DR: [1-2 sentence summary of key findings]4445---4647[COMPETITOR NAME] (source: [URL])48- [Feature 1]: [description, capabilities, limitations]49- [Feature 2]: [description, capabilities, limitations]50- [Notable absence]: [features they don't have that are relevant]5152[COMPETITOR NAME 2] (source: [URL]) — if multiple URLs provided53- [Feature 1]: [description, capabilities, limitations]54- [Feature 2]: [description, capabilities, limitations]5556---5758[YOUR PRODUCT] (source: YOUR_PRODUCT_DOCS_URL)59- [Feature 1]: [description, capabilities, limitations]60- [Feature 2]: [description, capabilities, limitations]61- [Unique capabilities]: [things your product has that competitors don't]6263---6465COMPARISON SUMMARY66- [Feature] — Competitor 1: [status] | Competitor 2: [status] | [YOUR PRODUCT]: [status]67- [Feature] — Competitor 1: [status] | Competitor 2: [status] | [YOUR PRODUCT]: [status]6869(Use ✅ has feature, ⚠️ partial/limited, ❌ missing, ❓ unclear)7071---7273KEY INSIGHTS74- [insight 1 — what this means for product decisions]75- [insight 2]76- [insight 3]7778GAPS & OPPORTUNITIES79- [gap 1 — where your product could improve or differentiate]80- [gap 2]8182RISKS83- [risk 1 — competitive threats or market shifts to watch]84- [risk 2]8586---END FORMAT---8788## Guidelines8990- Be evidence-driven: cite the source (URL/section) for every important claim91- Separate facts from assumptions from opinions92- If information is unclear or unavailable, say so rather than guessing93- Focus on the specific features/functionality the user asked about94- Keep the analysis actionable and decision-ready9596## After Completing Analysis9798create a markdown file in reports/feature_research with your findings, and create a PR.