competlab

competlab-agent-adoption

Wraps CompetLab's existing 25-check Agent-Adoption Scan (open Agent-Adoption Specification) for each monitored competitor + adds on-demand JSON-RPC POST verification for any MCP-server URLs detected by the scan. The platform scan covers discoverability, access control, content readability, and agent endpoints. This skill's value-add: PROTOCOL-LEVEL verification of MCP claims (browser GET 200 ≠ MCP exists), cross-competitor synthesis, strategic interpretation. Use when the user asks "does competitor X have a real MCP server", "agent-adoption posture in [category]", "AI-agent-readiness comparison", "is competitor's MCP claim real". Requires CompetLab MCP (start_agent_adoption_scan + get_agent_adoption_scan + list_competitors) + Bash for JSON-RPC POST verification.

competlab-ai-ecosystem

Measures EXTERNAL developer-ecosystem signals around each competitor — GitHub organization meta, top-starred repos, npm/PyPI download volumes, community-built MCP servers (not first-party), integration marketplace presence, Claude Skills directories, agent-toolkit repos. Complements competlab-agent-adoption (which measures FIRST-PARTY signals). Use when the user asks "developer adoption", "GitHub presence", "npm downloads", "marketplace presence", "agent-ecosystem strength", "community signals around [competitor]". Requires CompetLab MCP + Bash (GitHub + npm + PyPI API, mostly unauth) + WebSearch + Perplexity with URL verification.

competlab-ai-visibility

Analyzes how AI models (ChatGPT, Claude, Gemini) mention, rank, and recommend your brand vs competitors using CompetLab monitoring data. Use this skill when the user asks "how do LLMs see my brand", "AI visibility report", "AI brand check", "what does ChatGPT say about us", "GEO analysis", "AI SEO report", "LLM rankings", "AI mentions", "AI perception", or "who do AI models recommend in my space". NOT for traditional SEO, Google rankings, or web traffic analysis. Requires CompetLab MCP server (competlab.com) with an active project.

competlab-battlecard

Generates sales-ready competitive battlecards using CompetLab monitoring data and live web research — quick-reference cards for sales calls, demos, and competitive objection handling. Use this skill when the user asks to "create a battlecard", "sales battlecard for [competitor]", "competitive comparison card", "why us vs [competitor]", "win against [competitor]", "how to beat [competitor]", "objection handling for [competitor]", "sales cheat sheet", or "competitive one-pager". NOT for deep strategic analysis (use competlab-competitor-dive), weekly updates (use competlab-weekly-briefing), or full market landscape analysis (use competlab-landscape). Requires CompetLab MCP server (competlab.com) with competitors being monitored.

competlab-cmo-report

Orchestrator skill. Generates a complete CMO-grade strategic briefing for a CompetLab project by sequencing all dimension dashboards + on-demand research skills (status-watch, funding-watch, ai-ecosystem, hiring-signals, agent-adoption, product-watch, customer-voice-snapshot) + URL Verification middleware + the layered backing-docs synthesis. Output: 1 main briefing (L3) + 12 per-dimension docs (L2 — 4 dashboard-derived + 8 sub-skill-derived) + per-Tier-1-competitor deep dives (L2) + per-Tier-2-light-recon for monitoring-suggestions, with two-axis cross-references between docs. Use when the user asks for "CMO report", "strategic briefing", "Itrinity briefing", "full competitive analysis for [project]", "cold-start briefing". Replaces manual sequencing of individual skills with a single one-command run.

competlab-competitor-dive

Generates a comprehensive competitor dossier combining CompetLab monitoring data with live web research — tech stack, pricing, positioning, content strategy, AI visibility, public sentiment, SWOT analysis, and recommended responses. Use this skill when the user asks to "analyze [competitor]", "deep dive on [competitor]", "competitor dossier", "competitor profile", "research [competitor]", "what is [competitor] doing", "SWOT analysis for [competitor]", "competitor SWOT", or "tell me everything about [competitor]". NOT for multi-competitor landscape analysis (use competlab-landscape) or weekly updates (use competlab-weekly-briefing). Requires CompetLab MCP server (competlab.com) with the target competitor being monitored.

competlab-customer-voice-snapshot

Snapshots competitor presence on review platforms (G2 + Capterra + Trustpilot) and recent complaint themes. **Snapshot-only — limited coverage by design** because review-platform bot-blocking is universal (G2 + Trustpilot return 403 to all WebFetch attempts). Uses Perplexity-grounded answers as primary source, with URL verification for citations. Use when the user asks "what do customers say about competitor X", "G2 reviews for [competitor]", "complaint themes for [competitor]". For trend / velocity / sentiment-delta — requires dimension promotion (not this skill). Requires CompetLab MCP + Perplexity MCP + URL verification.

competlab-funding-watch

Surfaces recent funding events, ownership changes, ARR estimates, M&A activity, executive transitions, and category-adjacent capital pressure for each monitored competitor. Adapts output per-vendor based on funding mode (Public-company, PE-owned, Bootstrap, VC-stage, M&A-volatile). Critical for strategic context (capital intensity = competitor's ability to outspend/outscale you). Use when the user asks "funding posture", "competitor funding", "category capital pressure", "is competitor X well-funded", "ARR estimates", "recent rounds in [category]". Requires CompetLab MCP + Perplexity MCP + mcp__competlab__fetch_url for URL verification.

competlab-hiring-signals

Probes hiring + GTM-motion signals for each monitored competitor via public ATS APIs (Ashby, Greenhouse, Lever, Workable) + LinkedIn unauth fallback + Perplexity for exec transitions. Three-condition feasibility: (1) LinkedIn employer-brand presence, (2) ATS adoption (Ashby/Greenhouse/Lever), (3) vendor-name uniqueness. Use when the user asks "competitor hiring", "is X expanding sales motion", "competitor headcount trend", "GTM motion shift signals", "exec transitions". Most reliable for Series-B+ private + public vendors; less for bootstrapped operators without public ATS. Requires CompetLab MCP + Bash + Perplexity + URL verification.

competlab-landscape

Generates a comprehensive competitive landscape analysis combining all 5 CompetLab monitoring dimensions with deep web research — market dynamics, competitive matrices, cross-dimensional patterns, market macro trends, positioning opportunities, and strategic recommendations. Use this skill when the user asks for "competitive landscape", "full CI analysis", "landscape scan", "quarterly competitive review", "market analysis", "market overview", "competitive overview", "competitor matrix", "board-level CI", "market trends in [category]", or "where is the market heading". NOT for single-competitor analysis (use competlab-competitor-dive) or quick weekly updates (use competlab-weekly-briefing). Requires CompetLab MCP server (competlab.com) with an active project.

competlab-product-watch

Snapshots each monitored competitor's product surface beyond the homepage — structured changelogs, GitHub Releases, named-asset directories (MCP marketplaces, Claude Skills directories), API documentation versions, deprecation patterns. **Snapshot-only — does NOT produce velocity, diff, or alerts** (those are dimension-level features). Use when the user asks "what did competitor X ship recently", "product launches in [category]", "named recent product features", "changelog summary". Requires CompetLab MCP + Bash + mcp__competlab__fetch_url.

competlab-status-watch

Probes each monitored competitor's public status page and recent incident history. Detects ongoing outages, recent incident frequency, post-mortem quality, and status-page-broken-or-missing as itself a signal. Critical for sales conversations (concrete reliability ammunition — specific incident with date + duration + customer-impact), competitive trust assessment, and operational-maturity reads. Use when the user asks "competitor reliability", "competitor incidents", "status page check", "operational maturity", "sales reliability ammunition vs [competitor]". Requires CompetLab MCP + Bash + `mcp__competlab__fetch_url`.

competlab-weekly-briefing

Generates a weekly competitive intelligence briefing from CompetLab monitoring data — what changed, what it means, and what to do about it. Use this skill when the user asks for "weekly briefing", "CI update", "competitive update", "what changed with competitors", "Monday briefing", "competitive summary", "competitive news", "CI digest", or "catch me up on competitors". NOT for deep single-competitor analysis (use competlab-competitor-dive) or full landscape reviews (use competlab-landscape). Requires CompetLab MCP server (competlab.com) with an active project.