find-next-crypto-idea

Name: find-next-crypto-idea
Author: sendaifun

162stars45forks

How to install find-next-crypto-idea?

sendaifun/solana-new/find-next-crypto-idea

$npx -y skills add sendaifun/solana-new --skill find-next-crypto-idea

Installs into the current project.

Summary

Interview users sharply to discover, rank, or validate what they should build in crypto. Use when a user asks what to build in crypto, wants startup ideas in a crypto niche such as DeFi or AI x crypto, wants blunt feedback on an existing crypto idea, or wants a concrete artifact

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":"find-next-crypto-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":"find-next-crypto-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	# Find Next Crypto Idea
50
51	## Overview
52
53	Interview the user until there is real clarity, not just enthusiasm. Generate three serious idea candidates, force a winner, explain why crypto is necessary, and write a local HTML artifact that the user can review outside the chat.
54
55	## Workflow
56
57	1. Infer whether the user needs fresh ideas, a narrowed idea search in a known domain, or validation of an existing thesis.
58	2. Ask the user to pick a report theme. Read [references/report-themes.md](references/report-themes.md) and present the 12-theme table. Store their choice as the `theme` field in the JSON payload. If they say "surprise me", pick one that matches their vibe.
59	3. Read [references/source-map.md](references/source-map.md) first to understand the local datasets available to this skill.
60	4. Read [references/interview-framework.md](references/interview-framework.md) before asking substantive questions.
61	5. Gate every candidate through [references/crypto-necessity-test.md](references/crypto-necessity-test.md) before scoring it.
62	6. Score surviving candidates with [references/scoring-rubric.md](references/scoring-rubric.md).
63	7. Run fresh research with [references/research-playbook.md](references/research-playbook.md). When you already have candidate ideas, use `scripts/live_research.py` to generate browser-first X queries, GitHub queries, a normalized research pack, and a worksheet HTML.
64	8. Produce the shortlist artifact first. Let the user pick one. Then deepen the chosen idea and write a second artifact.
65
66	## Non-Negotiables
67
68	- Stay blunt. Challenge weak assumptions before elaborating them.
69	- Keep interviewing until you can clearly state:
70	- the user's unfair edge
71	- the real shipping constraint
72	- the first plausible wedge
73	- why crypto is required
74	- Reject ornamental crypto. Redirect to a stronger crypto angle instead of dressing up a weak one.
75	- Do not praise a bad idea because the user is attached to it.
76	- Do not produce three near-identical ideas. Force diversity across the shortlist when possible.
77	- Always do fresh research for competitors, substitutes, and active OSS before committing to the final ranking.
78	- Always write a local HTML file. Do not leave the result only in chat.
79
80	## Interview Rules
81
82	- Start with anchor questions, not a giant questionnaire.
83	- Pull constraints only when they would change the recommendation.
84	- Prefer questions that reveal:
85	- edge
86	- urgency
87	- customer access
88	- shipping ability
89	- tolerance for infra, regulation, and sales friction
90	-

People who liked this also viewed

6 picks

Type

find-next-crypto-idea

162stars45forks

View on GitHub

How to install find-next-crypto-idea?

sendaifun/solana-new/find-next-crypto-idea

$npx -y skills add sendaifun/solana-new --skill find-next-crypto-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":"find-next-crypto-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":"find-next-crypto-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	# Find Next Crypto Idea
50
51	## Overview
52
53	Interview the user until there is real clarity, not just enthusiasm. Generate three serious idea candidates, force a winner, explain why crypto is necessary, and write a local HTML artifact that the user can review outside the chat.
54
55	## Workflow
56
57	1. Infer whether the user needs fresh ideas, a narrowed idea search in a known domain, or validation of an existing thesis.
58	2. Ask the user to pick a report theme. Read [references/report-themes.md](references/report-themes.md) and present the 12-theme table. Store their choice as the `theme` field in the JSON payload. If they say "surprise me", pick one that matches their vibe.
59	3. Read [references/source-map.md](references/source-map.md) first to understand the local datasets available to this skill.
60	4. Read [references/interview-framework.md](references/interview-framework.md) before asking substantive questions.
61	5. Gate every candidate through [references/crypto-necessity-test.md](references/crypto-necessity-test.md) before scoring it.
62	6. Score surviving candidates with [references/scoring-rubric.md](references/scoring-rubric.md).
63	7. Run fresh research with [references/research-playbook.md](references/research-playbook.md). When you already have candidate ideas, use `scripts/live_research.py` to generate browser-first X queries, GitHub queries, a normalized research pack, and a worksheet HTML.
64	8. Produce the shortlist artifact first. Let the user pick one. Then deepen the chosen idea and write a second artifact.
65
66	## Non-Negotiables
67
68	- Stay blunt. Challenge weak assumptions before elaborating them.
69	- Keep interviewing until you can clearly state:
70	- the user's unfair edge
71	- the real shipping constraint
72	- the first plausible wedge
73	- why crypto is required
74	- Reject ornamental crypto. Redirect to a stronger crypto angle instead of dressing up a weak one.
75	- Do not praise a bad idea because the user is attached to it.
76	- Do not produce three near-identical ideas. Force diversity across the shortlist when possible.
77	- Always do fresh research for competitors, substitutes, and active OSS before committing to the final ranking.
78	- Always write a local HTML file. Do not leave the result only in chat.
79
80	## Interview Rules
81
82	- Start with anchor questions, not a giant questionnaire.
83	- Pull constraints only when they would change the recommendation.
84	- Prefer questions that reveal:
85	- edge
86	- urgency
87	- customer access
88	- shipping ability
89	- tolerance for infra, regulation, and sales friction
90	-

People who liked this also viewed

6 picks

Type