skills/cleanexpo/competitor-analysis/SKILL.md
Analyze competitor website structures, messaging patterns, and unique features. Use when researching competition, identifying gaps, or informing content strategy.
npx skillsauth add aiskillstore/marketplace competitor-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Analyze top competitors page-by-page to understand their structure, messaging, and features for gap analysis.
For each page, extract:
Order of sections from top to bottom:
Capture the exact wording used:
What builds credibility:
Call-to-action patterns:
What they have that others don't:
After analyzing competitors, identify:
src/lib/agents/competitor-analyzer.ts - Main agentcompetitor_analysis table - Storage{
"competitor": "Competitor Name",
"url": "https://competitor.com",
"rank": "national_leader",
"page_structures": {
"homepage": {
"sections": [...],
"headlines": [...],
"ctas": [...]
}
},
"unique_features": [...],
"trust_signals": [...],
"messaging_patterns": {...}
}
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.