validate-idea

Name: validate-idea
Author: sendaifun

162stars45forks

How to install validate-idea?

sendaifun/solana-new/validate-idea

$npx -y skills add sendaifun/solana-new --skill validate-idea

Installs into the current project.

Summary

Run a structured validation sprint on a crypto startup idea. Use when a user says "validate this idea", "is this worth building", "run a validation sprint", "help me test demand", or "should I build this". Reads idea-context.md from a prior idea phase if available.

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":"validate-idea","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":"validate-idea","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	# Validate Idea
50
51	## Overview
52
53	Take an idea (from a prior find-next-crypto-idea session or fresh from the user) and stress-test it with a structured validation sprint. Produce a go/no-go recommendation backed by demand signals, risk analysis, and a concrete next-steps plan.
54
55	## Workflow
56
57	1. Check for `.superstack/idea-context.md` in the workspace. If found, load the chosen idea. If not, ask the user to describe their idea.
58	2. Read [references/validation-framework.md](references/validation-framework.md) for the sprint structure.
59	3. Evaluate demand signals using [references/customer-signal-rubric.md](references/customer-signal-rubric.md).
60	4. Run the crypto necessity gut-check: "What breaks if you remove the blockchain?"
61	5. Map risks: technical, market, regulatory, team.
62	6. Apply [references/pivot-or-persist.md](references/pivot-or-persist.md) to reach a go/no-go decision.
63	7. Write a local HTML artifact with the validation report.
64
65	## Non-Negotiables
66
67	- Do not rubber-stamp. If the idea is weak, say so with specifics.
68	- Every "go" recommendation must cite at least 2 concrete demand signals (not vibes).
69	- Every "no-go" must include a pivot suggestion, not just rejection.
70	- If the user has no evidence of demand, the answer is "go validate" with a specific sprint plan, not "go build".
71	- Always check if there is already a live product doing the same thing on Solana.
72	- Always write a local HTML artifact. Do not leave results only in chat.
73	- Integration-first assessment: As part of validation, identify whether the idea can be built by integrating existing Solana protocols rather than writing a custom program. If integration is viable, note it as an advantage (faster to ship, lower audit costs). If the idea requires novel on-chain logic or the user is building the protocol layer itself, custom development is the right call — don't penalize it. Include the integration-vs-build assessment in next_steps. See `data/solana-knowledge/04-protocols-and-sdks.md` → "Integrate First, Build Second".
74
75	## Phase Handoff
76
77	This skill is Phase 1 (Idea) in the Idea → Build → Launch journey. After completing validation:
78
79	1. Write/update `.superstack/idea-context.md` (create if missing) with a `validation` field containing:
80	- `demand_signals`: array of evidence items
81	- `risks`: array of { category, description, severity }
82	- `go_no_go`: "go" \| "no-go" \| "pivot"
83	- `confidence`: 0.0 - 1.0
84	- `next_steps`: array of concrete actions
85	2. Tell the user they can proceed to the Build phase if the verdict is "go".
86	3. See `../../../data/specs/phase-handoff.md` for the full JSON contract.
87
88	## Quick Start
89
90	```bash
91	# Just describe your idea and ask for validation:
92	# "Validat

People who liked this also viewed

6 picks

Type

validate-idea

162stars45forks

View on GitHub

How to install validate-idea?

sendaifun/solana-new/validate-idea

$npx -y skills add sendaifun/solana-new --skill validate-idea

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":"validate-idea","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":"validate-idea","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	# Validate Idea
50
51	## Overview
52
53	Take an idea (from a prior find-next-crypto-idea session or fresh from the user) and stress-test it with a structured validation sprint. Produce a go/no-go recommendation backed by demand signals, risk analysis, and a concrete next-steps plan.
54
55	## Workflow
56
57	1. Check for `.superstack/idea-context.md` in the workspace. If found, load the chosen idea. If not, ask the user to describe their idea.
58	2. Read [references/validation-framework.md](references/validation-framework.md) for the sprint structure.
59	3. Evaluate demand signals using [references/customer-signal-rubric.md](references/customer-signal-rubric.md).
60	4. Run the crypto necessity gut-check: "What breaks if you remove the blockchain?"
61	5. Map risks: technical, market, regulatory, team.
62	6. Apply [references/pivot-or-persist.md](references/pivot-or-persist.md) to reach a go/no-go decision.
63	7. Write a local HTML artifact with the validation report.
64
65	## Non-Negotiables
66
67	- Do not rubber-stamp. If the idea is weak, say so with specifics.
68	- Every "go" recommendation must cite at least 2 concrete demand signals (not vibes).
69	- Every "no-go" must include a pivot suggestion, not just rejection.
70	- If the user has no evidence of demand, the answer is "go validate" with a specific sprint plan, not "go build".
71	- Always check if there is already a live product doing the same thing on Solana.
72	- Always write a local HTML artifact. Do not leave results only in chat.
73	- Integration-first assessment: As part of validation, identify whether the idea can be built by integrating existing Solana protocols rather than writing a custom program. If integration is viable, note it as an advantage (faster to ship, lower audit costs). If the idea requires novel on-chain logic or the user is building the protocol layer itself, custom development is the right call — don't penalize it. Include the integration-vs-build assessment in next_steps. See `data/solana-knowledge/04-protocols-and-sdks.md` → "Integrate First, Build Second".
74
75	## Phase Handoff
76
77	This skill is Phase 1 (Idea) in the Idea → Build → Launch journey. After completing validation:
78
79	1. Write/update `.superstack/idea-context.md` (create if missing) with a `validation` field containing:
80	- `demand_signals`: array of evidence items
81	- `risks`: array of { category, description, severity }
82	- `go_no_go`: "go" \| "no-go" \| "pivot"
83	- `confidence`: 0.0 - 1.0
84	- `next_steps`: array of concrete actions
85	2. Tell the user they can proceed to the Build phase if the verdict is "go".
86	3. See `../../../data/specs/phase-handoff.md` for the full JSON contract.
87
88	## Quick Start
89
90	```bash
91	# Just describe your idea and ask for validation:
92	# "Validat

People who liked this also viewed

6 picks

Type