[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DPYW8C2S0MEWTYJFRMMA87":3,"skill-same:01M7DPYW8C2S0MEWTYJFRMMA87":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7DPYW8C2S0MEWTYJFRMMA87","navigate-skills",null,"Meta-skill — browse and discover all installed stellar.new skills. Use when a user says \"what skills do I have\", \"show me available skills\", \"what can I do\", \"find a skill for X\", \"which skill should I use\", \"help me navigate\", \"what does stellar.new do\", or \"where do I start\". Lists skills by journey phase, surfaces the SKILL_ROUTER trigger phrases, and recommends the next skill given current context.","ozioziel\u002FWorkville","ozioziel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F201685456?v=4","01M7DPQ6XNF4MK3SRN0ADFTNHT","01M7DPQ6YAMRZ4S2NQPN9VQPH3",3,"MIT","https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fnavigate-skills\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: navigate-skills\ndescription: Meta-skill — browse and discover all installed stellar.new skills. Use when a user says \"what skills do I have\", \"show me available skills\", \"what can I do\", \"find a skill for X\", \"which skill should I use\", \"help me navigate\", \"what does stellar.new do\", or \"where do I start\". Lists skills by journey phase, surfaces the SKILL_ROUTER trigger phrases, and recommends the next skill given current context.\n---\n\n## What this skill does\n\n### 1. Survey installed skills\n\nScan `~\u002F.claude\u002Fskills\u002F` for: (a) skill folders with `SKILL.md`, (b) flat `.md` skill files (the SCF skills ship as flat files). Group them into journey phases:\n\n- **Idea** — `find-stellar-idea`, `brainstorming`, `advanced-elicitation`, `stellar-competitive-landscape`, `scf-round-watcher`, `justin-analyst`\n- **Planning** — `prfaq`, `product-brief`, `prd`, `nicole-pm`, `kaan-ux-designer`, `create-ux-design`\n- **Solutioning** — `tyler-architect`, `create-architecture`, `create-epics-and-stories`, `soroban`, `dapp`, `assets`, `data`, `agentic-payments`, `zk-proofs`, `standards`\n- **Implementation** — `elliot-dev`, `dev-story`, `investigate`, `party-mode`\n- **Review** — `code-review`, `review-edge-case-hunter`\n- **Launch** — `deploy-stellar-mainnet`, `scf-prescreen-checker`, `scf-interest-form-drafter`, `scf-submission-drafter`, `scf-budget-builder`, `scf-competitor-analyst`, `scf-referral-preparer`, `scf-reviewer`, `scf-round-reviewer`, `scf-tranche-reporter`, `fetch-external-doc`\n- **Meta** — `navigate-skills`, `stellar-help`, `bri-tech-writer`\n\n### 2. Read the SKILL_ROUTER\n\nLoad `~\u002F.claude\u002Fskills\u002FSKILL_ROUTER.md` if present — that's the canonical trigger-phrase → skill mapping.\n\n### 3. Respond based on user intent\n\n**If user is exploring** (\"what skills do I have\", \"show me everything\"):\n- Print the journey map above\n- Mention there are 42 total skills\n- Suggest starting with `find-stellar-idea` for early-stage builders\n\n**If user has a specific task** (\"I need to write a PRD\", \"I want to deploy to mainnet\"):\n- Match against trigger phrases in `SKILL_ROUTER.md`\n- Surface the matching skill name + how to invoke it\n- Mention 1-2 related skills they might want next\n\n**If user is stuck** (\"I'm lost\", \"which one do I use\", \"where do I start\"):\n- Ask: \"Where are you in the journey — figuring out what to build, planning, implementing, or shipping?\"\n- Based on the answer, suggest the 2-3 most relevant skills for that phase\n\n### 4. Always offer a concrete next step\n\nEvery response ends with one specific next-skill suggestion, not a list.\n\n## Constraints\n\n- Don't list skills that aren't actually installed — verify against the filesystem\n- Don't invent skill names — only use what's in `~\u002F.claude\u002Fskills\u002F`\n- If installed skill count doesn't match expected (42), suggest the user run `--update` to refresh\n- For the 6 personas (justin-analyst, bri-tech-writer, nicole-pm, kaan-ux-designer, tyler-architect, elliot-dev), explain they're invokable by name (\"talk to Nicole\") — these are role-based agents, not phase-bound skills\n","## What this skill does\n\n### 1. Survey installed skills\n\nScan `~\u002F.claude\u002Fskills\u002F` for: (a) skill folders with `SKILL.md`, (b) flat `.md` skill files (the SCF skills ship as flat files). Group them into journey phases:\n\n- **Idea** — `find-stellar-idea`, `brainstorming`, `advanced-elicitation`, `stellar-competitive-landscape`, `scf-round-watcher`, `justin-analyst`\n- **Planning** — `prfaq`, `product-brief`, `prd`, `nicole-pm`, `kaan-ux-designer`, `create-ux-design`\n- **Solutioning** — `tyler-architect`, `create-architecture`, `create-epics-and-stories`, `soroban`, `dapp`, `assets`, `data`, `agentic-payments`, `zk-proofs`, `standards`\n- **Implementation** — `elliot-dev`, `dev-story`, `investigate`, `party-mode`\n- **Review** — `code-review`, `review-edge-case-hunter`\n- **Launch** — `deploy-stellar-mainnet`, `scf-prescreen-checker`, `scf-interest-form-drafter`, `scf-submission-drafter`, `scf-budget-builder`, `scf-competitor-analyst`, `scf-referral-preparer`, `scf-reviewer`, `scf-round-reviewer`, `scf-tranche-reporter`, `fetch-external-doc`\n- **Meta** — `navigate-skills`, `stellar-help`, `bri-tech-writer`\n\n### 2. Read the SKILL_ROUTER\n\nLoad `~\u002F.claude\u002Fskills\u002FSKILL_ROUTER.md` if present — that's the canonical trigger-phrase → skill mapping.\n\n### 3. Respond based on user intent\n\n**If user is exploring** (\"what skills do I have\", \"show me everything\"):\n- Print the journey map above\n- Mention there are 42 total skills\n- Suggest starting with `find-stellar-idea` for early-stage builders\n\n**If user has a specific task** (\"I need to write a PRD\", \"I want to deploy to mainnet\"):\n- Match against trigger phrases in `SKILL_ROUTER.md`\n- Surface the matching skill name + how to invoke it\n- Mention 1-2 related skills they might want next\n\n**If user is stuck** (\"I'm lost\", \"which one do I use\", \"where do I start\"):\n- Ask: \"Where are you in the journey — figuring out what to build, planning, implementing, or shipping?\"\n- Based on the answer, suggest the 2-3 most relevant skills for that phase\n\n### 4. Always offer a concrete next step\n\nEvery response ends with one specific next-skill suggestion, not a list.\n\n## Constraints\n\n- Don't list skills that aren't actually installed — verify against the filesystem\n- Don't invent skill names — only use what's in `~\u002F.claude\u002Fskills\u002F`\n- If installed skill count doesn't match expected (42), suggest the user run `--update` to refresh\n- For the 6 personas (justin-analyst, bri-tech-writer, nicole-pm, kaan-ux-designer, tyler-architect, elliot-dev), explain they're invokable by name (\"talk to Nicole\") — these are role-based agents, not phase-bound skills\n",{"name":5,"description":7},"main","217c58ef684b467a1122bd3bac74141a90f974cd",".codex\u002Fskills\u002Fnavigate-skills",0,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville","https:\u002F\u002Fmyworkville.com","https:\u002F\u002Fgithub.com\u002Fozioziel","Full Stack Developer | React · NestJS · Flutter · Python | AI & Cloud | Penguins 🐧\r\n","2026-11-11 03:39:50",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add ozioziel\u002FWorkville --skill navigate-skills",{"tool":38,"command":39},"bunx","bunx skills add ozioziel\u002FWorkville --skill navigate-skills",{"tool":41,"command":42},"pnpm","pnpm dlx skills add ozioziel\u002FWorkville --skill navigate-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fnavigate-skills\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M7DQ1A5WKJHC1DSAAK9SJ5W8","zk-proofs","Zero-knowledge proofs and privacy patterns on Stellar. Covers Groth16 verification in smart contracts via BLS12-381 host functions (CAP-0059, available), the BN254 + Poseidon proposals (CAP-0074\u002F0075, status-sensitive), and concrete toolchain walkthroughs for Circom (on-chain verifiable today), Noir, and RISC Zero (attestation pattern until BN254 lands). Use when building privacy-preserving applications, ZK-verifier contracts, or wiring a proving toolchain to Stellar.","https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fzk-proofs\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7DQ171146QGP8BTPA4AQZX7","tyler-architect","System architect and technical design leader. Use when the user asks to talk to Tyler or requests the architect.","https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftyler-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7DQ120EG4KCSXJ8SBH7P7A8","stellar-help","Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.","https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fstellar-help\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7DQ0P859R7J75ZC9G93YHF2","stellar-competitive-landscape","Map the competitive landscape for a Stellar project idea. Use when a user says \"who are my competitors on Stellar\", \"competitive analysis Stellar\", \"what already exists in this space on Stellar\", \"show me similar Stellar projects\", \"is anyone else building this on Stellar\", \"map the Stellar landscape for X\" — or the Spanish\u002Fmixed-language equivalents, e.g. \"cual es la competencia de X\", \"que tan saturado está este espacio\", \"que aspectos están menos explorados y la SDF\u002FSCF están dispuestos a fondear\", or \"analiza la competencia de estos bounties\". Also fires when a user (directly, or via a BMAD persona like justin-analyst) names a specific protocol\u002Fidea inline and asks about its competition, viability, or market whitespace — including \"should we integrate [external protocol]\" or \"does anything like this already exist on Stellar\" research, where the deliverable is the same landscape map applied to a build-vs-integrate decision. Queries the 728-project LumenLoop ecosystem database and Electric Capital developer activity to rank competitors by SCF funding history and repo activity.","https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fstellar-competitive-landscape\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7DQ0DJ62TJJV7Z6N3149ZWJ","standards","Stellar standards, ecosystem, and reference. Covers SEPs (Stellar Ecosystem Proposals), CAPs (Core Advancement Proposals), and a quick map for picking the right standard for wallets, anchors, payments, deposits\u002Fwithdrawals, federation, deep links, and KYC. Also bundles ecosystem references (DeFi protocols, dev tools, wallets, infra, community projects), curated documentation links, and MCP servers (live tools such as Raven). Use when you need to know which SEP applies, or want a starting point for ecosystem integrations, official docs, or live MCP tooling.","https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fstandards\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7DQ0697WA5NA7C4XHCVK193","smart-contracts","Stellar smart contract development (Rust, soroban-sdk). Entry point with project setup, contract anatomy, and build\u002Fdeploy workflow, routing to three companion files in this directory — development.md (storage\u002FTTL, authorization, cross-contract calls, tokens, events, errors, upgrades, fees, troubleshooting), testing.md (unit, fuzz, property, fork, mutation, integration), and security.md (vulnerability classes, checklists, tooling, audits). Use when writing, testing, reviewing, securing, debugging, or shipping Stellar smart contracts, including anything the user calls \"Soroban\" — Soroban contracts, soroban-sdk, Soroban auth\u002Fstorage\u002FTTL errors, SEP-41 tokens, or SAC integration from contract code.","https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsmart-contracts\u002FSKILL.md",[],[]]