本文へ移動
cccskills
無料GitHub で公開

competitive-cartographer

Strategic analyst that maps competitive landscapes, identifies white space opportunities, and provides positioning recommendations. Use when users need competitive analysis, market positioning strategy, differentiation tactics, or "how do I stand out?" guidance across any domain (portfolios, products, services). NOT for market size estimation or financial forecasting.

インストール方法を見る

含まれるファイル(6)

  • SKILL.md5.1 KB
  • CHANGELOG.md862 B
  • references/domain-positioning.md3.0 KB
  • references/mapping-process.md4.7 KB
  • references/troubleshooting.md3.5 KB
  • scripts/validate_map.sh2.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Competitive Cartographer

A strategic analyst who maps competitive spaces to reveal positioning opportunities, white space, and differentiation strategies. Creates "you are here" maps in crowded markets.

Quick Start

User: "How do I stand out as a senior frontend engineer?"

Cartographer:
1. Define space: "Professional portfolios for senior frontend engineers"
2. Identify players:
   - Direct: Other senior frontend engineers in similar tech stacks
   - Adjacent: Full-stack engineers, design engineers
   - Aspirational: Apple's minimal aesthetic
3. Map on axes: Technical Depth (x) vs Design Polish (y)
4. Find white space: High tech + high design (rare combination)
5. Recommend positioning: "Engineer who thinks like a designer"

Key principle: Don't just list competitors - map them spatially to reveal positioning opportunities.

When to Use

Use when:

  • User asks "how do I stand out?" or "what makes me different?"
  • Launching product/service and need positioning strategy
  • Feeling lost in crowded market
  • Considering pivot or repositioning

Do NOT use when:

  • User needs market size or TAM estimates
  • Financial projections or fundraising strategy
  • Specific feature-by-feature comparison
  • User already has clear positioning

The 6-Step Process

StepAction
1. Define SpaceDomain, user's offer, background, goals
2. Identify PlayersDirect, adjacent, aspirational competitors
3. Analyze PositioningExtract taglines, visual strategy, content strategy
4. Create MapPlot on 2D axes, identify clusters
5. Find White SpaceViable, defensible, sustainable, aligned gaps
6. Recommend StrategyHeadline, differentiators, visual/content direction

Common Anti-Patterns

Me-Too Positioning

What it looks likeWhy it's wrong
"We're like Airbnb but for X"Invites comparison where you'll lose
Instead: Find unique angle that makes comparison irrelevant

Swiss Army Knife Syndrome

What it looks likeWhy it's wrong
"We do everything for everyone"In crowded markets, specialists beat generalists
Instead: Pick one thing you'll be known for

Feature Parity Race

What it looks likeWhy it's wrong
"All competitor features plus one more"Mature competitors will always out-feature you
Instead: Different approach/philosophy, not more features

Ignoring Your Constraints

What it looks likeWhy it's wrong
Positioning as enterprise when solo founderCan't deliver on promise, credibility destroyed
Instead: Position where constraints become advantages ("boutique", "founder-led")

Types of White Space

TypeExample
Intersection"Technical depth + warm personality" (most pick one)
Under-served Audience"Mid-market companies" (everyone targets enterprise or startups)
Contrarian"Slow and thoughtful" (when everyone races to launch fast)

Best Practices

Start with User, Not Market

  1. What's genuinely unique about user?
  2. What do they do better than anyone?
  3. What do they want to be known for?
  4. Then find where that fits in competitive landscape

Be Ruthlessly Honest

  • Point out crowded positioning
  • Identify genuine weaknesses
  • Recommend against poor strategic fit

Provide Evidence

  • "Here are 15 portfolios using exact same layout"
  • "Here are 8 products with nearly identical taglines"
  • "Here's how competitors cluster around this position"

Reference Files

FileContents
references/mapping-process.mdDetailed 6-step methodology, TypeScript interfaces, axis pairs
references/domain-positioning.mdPortfolio, SaaS, consulting-specific positioning + examples
references/troubleshooting.mdCommon issues, validation methods, best practices checklist

Integration with Other Skills

SkillIntegration
design-archivistVisual pattern database informs differentiation strategy
vibe-matcherTranslate positioning into emotional/visual direction
career-biographerCompetitive context informs personal brand positioning

Transform competitive chaos into strategic clarity.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Expert in 2000s-era music visualization (Milkdrop, AVS, Geiss) and modern WebGL implementations. Specializes in Butterchurn integration, Web Audio API AnalyserNode FFT data, GLSL shaders for audio-reactive visuals, and psychedelic generative art. Activate on "Milkdrop", "music visualization", "WebGL visualizer", "Butterchurn", "audio reactive", "FFT visualization", "spectrum analyzer". NOT for simple bar charts/waveforms (use basic canvas), video editing, or non-audio visuals.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/windags-skills132026年10月12日 更新

Expert legal research agent for finding and scraping expungement data state by state. Knows authoritative sources, URL patterns, Firecrawl configuration, and 2026 legal landscape.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/windags-skills132026年10月12日 更新

Expert in 3D computer vision labeling tools, workflows, and AI-assisted annotation for LiDAR, point clouds, and sensor fusion. Covers SAM4D/Point-SAM, human-in-the-loop architectures, and vertical-specific training strategies. Activate on '3D labeling', 'point cloud annotation', 'LiDAR labeling', 'SAM 3D', 'SAM4D', 'sensor fusion annotation', '3D bounding box', 'semantic segmentation point cloud'. NOT for 2D image labeling (use clip-aware-embeddings), general ML training (use ml-engineer), video annotation without 3D (use computer-vision-pipeline), or VLM prompt engineering (use prompt-engineer).

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/windags-skills132026年10月12日 更新

Apply crisis decision-making research to agent routing, uncertainty triage, and coordination failure analysis in time-pressured systems. Use when diagnosing handoff failures, analytical paralysis, or expert judgment under incomplete information. NOT for routine coding, simple CRUD design, or static single-agent tasks with complete information.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/windags-skills132026年10月12日 更新

Use for insight, reframing, contradiction, impasse, and anomaly-driven problem solving when execution effort no longer helps. NOT for routine optimization, error correction, or well-specified tasks with known solution paths.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/windags-skills132026年10月12日 更新

Apply normative BDI reasoning to agents that must detect norms, choose which commitments to internalize, and resolve conflicts by comparing consequences. Use when obligations, prohibitions, or policies collide in autonomous systems. NOT for simple fixed-priority rules, pure constraint satisfaction, or domains where no real normative conflict exists.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/windags-skills132026年10月12日 更新

curiositech のスキルをすべて見る

このスキルの問題を報告する