competitive-landscape

Name: competitive-landscape
Author: sendaifun

162stars45forks

How to install competitive-landscape?

sendaifun/solana-new/competitive-landscape

$npx -y skills add sendaifun/solana-new --skill competitive-landscape

Installs into the current project.

Summary

Map the competitive landscape for a crypto product idea. Use when a user says "who are my competitors", "map the competitive landscape", "what exists in this space", "show me similar projects", or "competitive analysis". Leverages solana-new's catalogs of 106 repos, 78 skills, an

Files · 1

View on GitHub

SKILL.md

1	## Preamble (run first)
2
3	```bash
4	_TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"telemetryTier": "[^"]"' \| head -1 \| sed 's/."telemetryTier": "//;s/"$//' \|\| echo "anonymous")
5	_TEL_TIER="${_TEL_TIER:-anonymous}"
6	_TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" \|\| echo "no")
7	_TEL_START=$(date +%s)
8	_SESSION_ID="$$-$(date +%s)"
9	mkdir -p ~/.superstack
10	echo "TELEMETRY: $_TEL_TIER"
11	echo "TEL_PROMPTED: $_TEL_PROMPTED"
12	if [ "$_TEL_TIER" != "off" ]; then
13	_TEL_EVENT='{"skill":"competitive-landscape","phase":"idea","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}'
14	echo "$_TEL_EVENT" >> ~/.superstack/telemetry.jsonl 2>/dev/null \|\| true
15	_CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"convexUrl":"[^"]*"' \| head -1 \| cut -d'"' -f4 \|\| echo "")
16	[ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"competitive-landscape","phase":"idea","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 &
17	true
18	fi
19	```
20
21	If `TEL_PROMPTED` is `no`: Before starting the skill workflow, ask the user about telemetry.
22	Use AskUserQuestion:
23
24	> Help superstack get better! We track which skills get used and how long they take —
25	> no code, no file paths, no PII. Change anytime in `~/.superstack/config.json`.
26
27	Options:
28	- A) Sure, help superstack improve (anonymous)
29	- B) No thanks
30
31	If A: run this bash:
32	```bash
33	echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json
34	_TEL_TIER="anonymous"
35	touch ~/.superstack/.telemetry-prompted
36	```
37
38	If B: run this bash:
39	```bash
40	echo '{"telemetryTier":"off"}' > ~/.superstack/config.json
41	_TEL_TIER="off"
42	touch ~/.superstack/.telemetry-prompted
43	```
44
45	This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely and proceed to the skill workflow.
46
47	> Wrong skill? See [SKILL_ROUTER.md](../../SKILL_ROUTER.md) for all available skills.
48
49	# Competitive Landscape
50
51	## Overview
52
53	Map every relevant competitor, substitute, and adjacent project for a given crypto product idea. Produce a landscape matrix showing where the opportunities and dangers are.
54
55	## Workflow
56
57	1. Check for `.superstack/idea-context.md` in the workspace. If found, use the chosen idea's domain. If not, ask the user what space to analyze.
58	2. Read [references/landscape-mapping.md](references/landscape-mapping.md) for the mapping methodology.
59	3. Search the solana-new ecosystem catalogs as described in [references/ecosystem-catalog-guide.md](references/ecosystem-catalog-guide.md).
60	4. Assess defensibility using [references/moat-analysis.md](references/moat-analysis.md).
61	5. Do fresh web research: crypto Twitter, GitHub, DeFiLlama, app directories.
62	6. Produce a landscape HTML artifact with the full competitive matrix.
63
64	## Non-Negotiables
65
66	- Always search the solana-new catalogs first — if a tool already exists, the user needs to know.
67	- Include dead/failed projects, not just live ones. Failures reveal landmines.
68	- Distinguish between "competitors" (same problem, same user) and "substitutes" (same problem, different approach).
69	- Include at least one non-crypto substitute if applicable.
70	- Do not declare "no competition" unless you've exhausted all search paths.
71	- Rate crowdedness honestly: empty / sparse / moderate / crowded / saturated.
72	- Always write a local HTML artifact.
73
74	## Phase Handoff
75
76	This skill is Phase 1 (Idea) in the Idea → Build → Launch journey. After mapping the landscape:
77
78	1. Write/update `.superstack/idea-context.md` (create if missing) with a `landscape` field containing:
79	- `direct_competitors`: array of { name, url, status, strength, weakness }
80	- `substitutes`: array of { name, approach, why_users_stay }
81	- `dead_projects`: array of { name, why_failed }
82	- `crowdedness`: "empty" \| "sparse" \| "moderate" \| "crowded" \| "saturated"
83	- `moat_type`: identified moat category
84	- `differentiation`: recommended angle
85	2. See `../../../data/specs/phase-handoff.md` for the full JSON contract.
86
87	## Quick Start
88
89	```bash
90	# Ask about competitors for your specific idea:
91	# "Who are my competitors for agent payments on Solana?"
92	# "Map the competitive landscape for DeFi lending"
93	# "What exists in the Solana staking space?"
94
95	# The skill will search:
96	# - 106 repos in cli/data/clonable-repos.json
97	# - 77 skills in cli/data/solana-skills.json
98	# - 36 MCPs in cli/data/solana-mcps.json
99	# - DefiLlama, GitHub, and crypto Twitter
100	```
101
102	## Decision Points
103
104	- Saturated market? If crowdedness = "saturated" (>5 direct competitors), look for underserved angle or niche.
105	- **Which

People who liked this also viewed

6 picks

Type

competitive-landscape

162stars45forks

View on GitHub

How to install competitive-landscape?

sendaifun/solana-new/competitive-landscape

$npx -y skills add sendaifun/solana-new --skill competitive-landscape

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## Preamble (run first)
2
3	```bash
4	_TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"telemetryTier": "[^"]"' \| head -1 \| sed 's/."telemetryTier": "//;s/"$//' \|\| echo "anonymous")
5	_TEL_TIER="${_TEL_TIER:-anonymous}"
6	_TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" \|\| echo "no")
7	_TEL_START=$(date +%s)
8	_SESSION_ID="$$-$(date +%s)"
9	mkdir -p ~/.superstack
10	echo "TELEMETRY: $_TEL_TIER"
11	echo "TEL_PROMPTED: $_TEL_PROMPTED"
12	if [ "$_TEL_TIER" != "off" ]; then
13	_TEL_EVENT='{"skill":"competitive-landscape","phase":"idea","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}'
14	echo "$_TEL_EVENT" >> ~/.superstack/telemetry.jsonl 2>/dev/null \|\| true
15	_CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"convexUrl":"[^"]*"' \| head -1 \| cut -d'"' -f4 \|\| echo "")
16	[ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"competitive-landscape","phase":"idea","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 &
17	true
18	fi
19	```
20
21	If `TEL_PROMPTED` is `no`: Before starting the skill workflow, ask the user about telemetry.
22	Use AskUserQuestion:
23
24	> Help superstack get better! We track which skills get used and how long they take —
25	> no code, no file paths, no PII. Change anytime in `~/.superstack/config.json`.
26
27	Options:
28	- A) Sure, help superstack improve (anonymous)
29	- B) No thanks
30
31	If A: run this bash:
32	```bash
33	echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json
34	_TEL_TIER="anonymous"
35	touch ~/.superstack/.telemetry-prompted
36	```
37
38	If B: run this bash:
39	```bash
40	echo '{"telemetryTier":"off"}' > ~/.superstack/config.json
41	_TEL_TIER="off"
42	touch ~/.superstack/.telemetry-prompted
43	```
44
45	This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely and proceed to the skill workflow.
46
47	> Wrong skill? See [SKILL_ROUTER.md](../../SKILL_ROUTER.md) for all available skills.
48
49	# Competitive Landscape
50
51	## Overview
52
53	Map every relevant competitor, substitute, and adjacent project for a given crypto product idea. Produce a landscape matrix showing where the opportunities and dangers are.
54
55	## Workflow
56
57	1. Check for `.superstack/idea-context.md` in the workspace. If found, use the chosen idea's domain. If not, ask the user what space to analyze.
58	2. Read [references/landscape-mapping.md](references/landscape-mapping.md) for the mapping methodology.
59	3. Search the solana-new ecosystem catalogs as described in [references/ecosystem-catalog-guide.md](references/ecosystem-catalog-guide.md).
60	4. Assess defensibility using [references/moat-analysis.md](references/moat-analysis.md).
61	5. Do fresh web research: crypto Twitter, GitHub, DeFiLlama, app directories.
62	6. Produce a landscape HTML artifact with the full competitive matrix.
63
64	## Non-Negotiables
65
66	- Always search the solana-new catalogs first — if a tool already exists, the user needs to know.
67	- Include dead/failed projects, not just live ones. Failures reveal landmines.
68	- Distinguish between "competitors" (same problem, same user) and "substitutes" (same problem, different approach).
69	- Include at least one non-crypto substitute if applicable.
70	- Do not declare "no competition" unless you've exhausted all search paths.
71	- Rate crowdedness honestly: empty / sparse / moderate / crowded / saturated.
72	- Always write a local HTML artifact.
73
74	## Phase Handoff
75
76	This skill is Phase 1 (Idea) in the Idea → Build → Launch journey. After mapping the landscape:
77
78	1. Write/update `.superstack/idea-context.md` (create if missing) with a `landscape` field containing:
79	- `direct_competitors`: array of { name, url, status, strength, weakness }
80	- `substitutes`: array of { name, approach, why_users_stay }
81	- `dead_projects`: array of { name, why_failed }
82	- `crowdedness`: "empty" \| "sparse" \| "moderate" \| "crowded" \| "saturated"
83	- `moat_type`: identified moat category
84	- `differentiation`: recommended angle
85	2. See `../../../data/specs/phase-handoff.md` for the full JSON contract.
86
87	## Quick Start
88
89	```bash
90	# Ask about competitors for your specific idea:
91	# "Who are my competitors for agent payments on Solana?"
92	# "Map the competitive landscape for DeFi lending"
93	# "What exists in the Solana staking space?"
94
95	# The skill will search:
96	# - 106 repos in cli/data/clonable-repos.json
97	# - 77 skills in cli/data/solana-skills.json
98	# - 36 MCPs in cli/data/solana-mcps.json
99	# - DefiLlama, GitHub, and crypto Twitter
100	```
101
102	## Decision Points
103
104	- Saturated market? If crowdedness = "saturated" (>5 direct competitors), look for underserved angle or niche.
105	- **Which

People who liked this also viewed

6 picks

Type