$npx -y skills add sendaifun/solana-new --skill navigate-skillsMeta skill — browse all installed solana-new skills, repos, and MCPs to find the right tool for any task
| 1 | ## Preamble (run first) |
| 2 | |
| 3 | ```bash |
| 4 | mkdir -p ~/.superstack |
| 5 | _TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null | grep -o '"telemetryTier":"[^"]*"' | head -1 | cut -d'"' -f4 || echo "anonymous") |
| 6 | _CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null | grep -o '"convexUrl":"[^"]*"' | head -1 | cut -d'"' -f4 || echo "") |
| 7 | _TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" || echo "no") |
| 8 | _TEL_START=$(date +%s) |
| 9 | _SESSION_ID="$$-$(date +%s)" |
| 10 | echo '{"skill":"navigate-skills","phase":"build","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' >> ~/.superstack/telemetry.jsonl 2>/dev/null || true |
| 11 | [ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"navigate-skills","phase":"build","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 || true |
| 12 | echo "TELEMETRY: $_TEL_TIER" |
| 13 | echo "TEL_PROMPTED: $_TEL_PROMPTED" |
| 14 | ``` |
| 15 | |
| 16 | If `TEL_PROMPTED` is `no`: Before starting the skill workflow, ask the user about telemetry. |
| 17 | Use AskUserQuestion: |
| 18 | |
| 19 | > Help superstack get better! We track which skills get used and how long they take — |
| 20 | > no code, no file paths, no PII. Change anytime in `~/.superstack/config.json`. |
| 21 | |
| 22 | Options: |
| 23 | - A) Sure, help superstack improve (anonymous) |
| 24 | - B) No thanks |
| 25 | |
| 26 | If A: run this bash: |
| 27 | ```bash |
| 28 | echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json |
| 29 | _TEL_TIER="anonymous" |
| 30 | touch ~/.superstack/.telemetry-prompted |
| 31 | ``` |
| 32 | |
| 33 | If B: run this bash: |
| 34 | ```bash |
| 35 | echo '{"telemetryTier":"off"}' > ~/.superstack/config.json |
| 36 | _TEL_TIER="off" |
| 37 | touch ~/.superstack/.telemetry-prompted |
| 38 | ``` |
| 39 | |
| 40 | This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely and proceed to the skill workflow. |
| 41 | |
| 42 | > **Wrong skill?** See [SKILL_ROUTER.md](../../SKILL_ROUTER.md) for all available skills. |
| 43 | |
| 44 | # Navigate Skills — Solana Ecosystem Skill Router |
| 45 | |
| 46 | You are a skill navigator. Help the user discover the right skill, repo, or MCP server for their task. You have access to the full solana-new catalog data. |
| 47 | |
| 48 | ## Your Catalog Data |
| 49 | |
| 50 | Catalog data may be in either location: |
| 51 | |
| 52 | - `~/.codex/skills/data/catalogs/` |
| 53 | - `~/.claude/skills/data/catalogs/` |
| 54 | |
| 55 | | File | What it contains | |
| 56 | |------|-----------------| |
| 57 | | `clonable-repos.json` | 88 cloneable Solana repos with categories, keywords, and clone URLs | |
| 58 | | `solana-skills.json` | 77 skills (15 official + 62 community) with install commands | |
| 59 | | `solana-mcps.json` | 36 MCP servers with setup instructions | |
| 60 | |
| 61 | Read these files to answer the user's questions accurately. |
| 62 | |
| 63 | ## Installed Journey Skills (16) |
| 64 | |
| 65 | These are the installed skills. The user can trigger them by asking naturally: |
| 66 | |
| 67 | ### Phase 1: Idea |
| 68 | | Skill | Trigger | |
| 69 | |-------|---------| |
| 70 | | `find-next-crypto-idea` | "What should I build in crypto?" | |
| 71 | | `validate-idea` | "Validate this idea" | |
| 72 | | `competitive-landscape` | "Who are my competitors?" | |
| 73 | | `defillama-research` | "Show me DeFi opportunities" | |
| 74 | |
| 75 | ### Phase 2: Build |
| 76 | | Skill | Trigger | |
| 77 | |-------|---------| |
| 78 | | `scaffold-project` | "Scaffold my project" | |
| 79 | | `build-with-claude` | "Help me build the MVP" | |
| 80 | | `build-defi-protocol` | "Build a DeFi protocol" | |
| 81 | | `launch-token` | "Launch an SPL token" | |
| 82 | | `build-data-pipeline` | "Build an indexer / data pipeline" | |
| 83 | | `build-mobile` | "Build a Solana mobile app" | |
| 84 | | `debug-program` | "Debug my program" | |
| 85 | | `review-and-iterate` | "Review my code for security" | |
| 86 | | `navigate-skills` | "What skills do I have?" (this skill) | |
| 87 | |
| 88 | ### Phase 3: Launch |
| 89 | | Skill | Trigger | |
| 90 | |-------|---------| |
| 91 | | `deploy-to-mainnet` | "Deploy to mainnet" | |
| 92 | | `create-pitch-deck` | "Create a pitch deck" | |
| 93 | | `submit-to-hackathon` | "Prepare my hackathon submission" | |
| 94 | |
| 95 | ## Dependency Routing (Required) |
| 96 | |
| 97 | When a user invokes a downstream skill directly, route them to the required predecessor skill(s) first. |
| 98 | |
| 99 | Use this exact order: |
| 100 | |
| 101 | 1. `/find-next-crypto-idea` (or prompt: "What should I build in crypto?") |
| 102 | 2. `scaffold-project` |
| 103 | 3. `build-with-claude` |
| 104 | 4. `review-and-iterate` |
| 105 | 5. Launch skills: |
| 106 | - `deploy-to-mainnet` |
| 107 | - `create-pitch-deck` |
| 108 | - `submit-to-hackathon` |
| 109 | |
| 110 | Context dependencies: |
| 111 | |
| 112 | - `scaffold-project` expects `.superstack/idea-context.md` (or will create it from user interview). |
| 113 | - `build-with-claude` expects `.superstack/build-context.md` from scaffold. |
| 114 | - `review-and-iterate` expects `.superstack/build-context.md`. |
| 115 | - Launch skills expect build context, and `deploy-to-mainnet` also expects devnet-tested status. |
| 116 | |
| 117 | If dependency context is missing, do not pretend it exists. Tell the user the exact next skill to run and why. |
| 118 | |
| 119 | ## Installing Community Skills |
| 120 | |
| 121 | Skills from the catalog can be installed locally using `npx skills add` |