[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77KDMMP6AC0X35E4149NXAA":3,"skill-same:01M77KDMMP6AC0X35E4149NXAA":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M77KDMMP6AC0X35E4149NXAA","scf-round-watcher",null,"Surface current and recent Stellar Community Fund (SCF) round activity. Use when a user says \"current SCF round\", \"what's happening with SCF\", \"active SCF submissions\", \"should I apply to SCF this round\", \"SCF deadline\", \"who is applying to SCF right now\", \"SCF round status\", or \"show me this round's submissions\". Fetches live data from communityfund.stellar.org and cross-references with the LumenLoop ecosystem DB to flag repeat builders and category trends.","WritzProtocol\u002Fwritz","WritzProtocol","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F296057967?v=4","01M77K5N0T3073T814APZTAXM4","Writz Protocol","01M77K5N1WQ551ZKCCK9MR379A",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FWritzProtocol\u002Fwritz\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fscf-round-watcher\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: scf-round-watcher\ndescription: Surface current and recent Stellar Community Fund (SCF) round activity. Use when a user says \"current SCF round\", \"what's happening with SCF\", \"active SCF submissions\", \"should I apply to SCF this round\", \"SCF deadline\", \"who is applying to SCF right now\", \"SCF round status\", or \"show me this round's submissions\". Fetches live data from communityfund.stellar.org and cross-references with the LumenLoop ecosystem DB to flag repeat builders and category trends.\n---\n\n## What this skill does\n\n### 1. Find the active round\n\nFetch `https:\u002F\u002Fcommunityfund.stellar.org\u002Fawards`. The currently open round has status \"Submission\". Extract its rec ID from the round's link (`\u002Fawards\u002F\u003Crec-id>`).\n\nThe site is a client-rendered React app - plain `curl` returns mostly empty HTML. Use the **WebFetch tool** (Claude Code built-in) which handles client-rendered pages via its parsing layer:\n\n```\nWebFetch(\n  url=\"https:\u002F\u002Fcommunityfund.stellar.org\u002Fawards\",\n  prompt=\"Find the round with status 'Submission' (currently open). Return its name (e.g., 'SCF #44'), its rec-id from the link (\u002Fawards\u002F\u003Crec-id>), the deadline date, and the maximum award amount.\"\n)\n```\n\nIf WebFetch isn't available in the runtime, fall back to a headless-browser fetch (e.g., `playwright` or `puppeteer` via `uvx`) - `curl` alone won't get rendered content for this site.\n\n### 2. Get the round's submissions\n\nFetch `https:\u002F\u002Fcommunityfund.stellar.org\u002Fawards\u002F\u003Cround-rec-id>`. Parse the submissions list - each entry has: project name, requested amount, status.\n\nIf a \"See All\" link is present, follow it for the full list (not just the first 11 visible on the round page).\n\n### 3. Enrich each submission with project detail\n\nFor each submission, follow its \"view\" link → `\u002Fproject\u002F\u003Csubmission-rec-id>`. Fetch in parallel (5 at a time, polite to the server). Extract: project description, category, team members + GitHub links, Stellar integration summary, requested amount.\n\n### 4. Cross-reference repeat builders\n\nLoad `~\u002F.claude\u002Fskills\u002Fdata\u002Flumenloop\u002Fprojects.json` (or fetch from `https:\u002F\u002Fraw.githubusercontent.com\u002Flumenloop\u002Fstellar-ecosystem-db\u002Fmain\u002F...` if missing).\n\nFor each submission team, check if any team's project is already in the LumenLoop DB. If yes, flag them as **repeat builder** with their past SCF rounds and total prior funding.\n\n### 4.5 Cross-reference Stellar dev history (Electric Capital)\n\nLoad `~\u002F.claude\u002Fskills\u002Fdata\u002Felectric-capital\u002Fstellar-repos.json` (~9000 repos). For each submission's GitHub org\u002Fuser (extracted from team links on `\u002Fproject\u002F\u003Crec-id>`), count how many Stellar-tagged repos that org has.\n\nBucket:\n- **Stellar veteran**: org has 5+ Stellar repos in Electric Capital → likely a serious builder\n- **First Stellar project**: 0-1 Stellar repos → fresh to the ecosystem (positive: new blood; risk: less Stellar-native context)\n- **Bootcamp graduate**: repos are mostly `whitebelt`\u002F`orangebelt`\u002Fetc → graduated Stellar's training program, applying directly after\n\nThis often reveals more than the LumenLoop check alone, because LumenLoop only catalogs projects with SCF history; many serious builders have GitHub activity but no funded project yet.\n\n### 5. Summarize for the user\n\nFormat as:\n\n```\n## SCF Round #\u003CN> - \u003CSTATUS>\nDeadline: \u003CDATE> (\u003CX days remaining>)\n\n### Top facts\n- \u003CN> submissions visible\n- Total requested: $\u003Csum>K\n- Top 3 categories: \u003Ccategory 1> (N), \u003Ccategory 2> (N), \u003Ccategory 3> (N)\n- Repeat builders: \u003CN> teams previously funded by SCF\n- First-timers: \u003CN>\n\n### Notable submissions\n\n| Project | Asks | Category | Builder status | What they do |\n|---------|------|----------|----------------|--------------|\n| ... | $X K | ... | repeat \u002F first-time | one-line description |\n\n### Patterns this round\n\u003C2-3 sentences on what categories or themes are dominant>\n```\n\n### 5.5 Optional: thesis-alignment flagging\n\nFor each active submission, optionally cross-reference with:\n- `~\u002F.claude\u002Fskills\u002Fdata\u002Fideas\u002Fa16z-big-ideas-2025.json` - does this submission ride an a16z 2025 thesis (RWA, agentic payments, prediction markets, etc.)?\n- `~\u002F.claude\u002Fskills\u002Fdata\u002Fideas\u002Fyc-requests-for-startups.json` - does YC explicitly want something in this category?\n\nSubmissions that hit BOTH Stellar ecosystem-fit AND broader investor thesis are 2x more likely to win the round. Flag them as \"thesis-aligned\" in the summary table.\n\n### 6. Close with next-step suggestions\n\nIf user is considering applying:\n- Route to `scf-prescreen-checker` to test their idea against the prescreen filter\n- Route to `scf-competitor-analyst` if they're worried about overlap with other submissions\n- Route to `scf-submission-drafter` if ready to draft\n\nIf user is researching:\n- Offer to deep-dive any specific submission\n- Offer to compare against the last 3 rounds (grep historical `scf.awarded_round` patterns in `projects.json`)\n\n## Constraints\n\n- Be polite to communityfund.stellar.org - sequential fetches or low concurrency (5 max)\n- Cache fetched data in `~\u002F.stellar\u002Fcache\u002Fscf-round\u002F\u003Crec-id>.json` for the session\n- If the site is down or returns non-200, report cleanly and suggest the user visit communityfund.stellar.org directly. Do not fabricate data.\n- If dates aren't visible on the page, say \"deadline not extractable from page\" - don't speculate\n- The active-round detection assumes exactly one round has status \"Submission\" at a time. If multiple or none, surface that as a finding\n","## What this skill does\n\n### 1. Find the active round\n\nFetch `https:\u002F\u002Fcommunityfund.stellar.org\u002Fawards`. The currently open round has status \"Submission\". Extract its rec ID from the round's link (`\u002Fawards\u002F\u003Crec-id>`).\n\nThe site is a client-rendered React app - plain `curl` returns mostly empty HTML. Use the **WebFetch tool** (Claude Code built-in) which handles client-rendered pages via its parsing layer:\n\n```\nWebFetch(\n  url=\"https:\u002F\u002Fcommunityfund.stellar.org\u002Fawards\",\n  prompt=\"Find the round with status 'Submission' (currently open). Return its name (e.g., 'SCF #44'), its rec-id from the link (\u002Fawards\u002F\u003Crec-id>), the deadline date, and the maximum award amount.\"\n)\n```\n\nIf WebFetch isn't available in the runtime, fall back to a headless-browser fetch (e.g., `playwright` or `puppeteer` via `uvx`) - `curl` alone won't get rendered content for this site.\n\n### 2. Get the round's submissions\n\nFetch `https:\u002F\u002Fcommunityfund.stellar.org\u002Fawards\u002F\u003Cround-rec-id>`. Parse the submissions list - each entry has: project name, requested amount, status.\n\nIf a \"See All\" link is present, follow it for the full list (not just the first 11 visible on the round page).\n\n### 3. Enrich each submission with project detail\n\nFor each submission, follow its \"view\" link → `\u002Fproject\u002F\u003Csubmission-rec-id>`. Fetch in parallel (5 at a time, polite to the server). Extract: project description, category, team members + GitHub links, Stellar integration summary, requested amount.\n\n### 4. Cross-reference repeat builders\n\nLoad `~\u002F.claude\u002Fskills\u002Fdata\u002Flumenloop\u002Fprojects.json` (or fetch from `https:\u002F\u002Fraw.githubusercontent.com\u002Flumenloop\u002Fstellar-ecosystem-db\u002Fmain\u002F...` if missing).\n\nFor each submission team, check if any team's project is already in the LumenLoop DB. If yes, flag them as **repeat builder** with their past SCF rounds and total prior funding.\n\n### 4.5 Cross-reference Stellar dev history (Electric Capital)\n\nLoad `~\u002F.claude\u002Fskills\u002Fdata\u002Felectric-capital\u002Fstellar-repos.json` (~9000 repos). For each submission's GitHub org\u002Fuser (extracted from team links on `\u002Fproject\u002F\u003Crec-id>`), count how many Stellar-tagged repos that org has.\n\nBucket:\n- **Stellar veteran**: org has 5+ Stellar repos in Electric Capital → likely a serious builder\n- **First Stellar project**: 0-1 Stellar repos → fresh to the ecosystem (positive: new blood; risk: less Stellar-native context)\n- **Bootcamp graduate**: repos are mostly `whitebelt`\u002F`orangebelt`\u002Fetc → graduated Stellar's training program, applying directly after\n\nThis often reveals more than the LumenLoop check alone, because LumenLoop only catalogs projects with SCF history; many serious builders have GitHub activity but no funded project yet.\n\n### 5. Summarize for the user\n\nFormat as:\n\n```\n## SCF Round #\u003CN> - \u003CSTATUS>\nDeadline: \u003CDATE> (\u003CX days remaining>)\n\n### Top facts\n- \u003CN> submissions visible\n- Total requested: $\u003Csum>K\n- Top 3 categories: \u003Ccategory 1> (N), \u003Ccategory 2> (N), \u003Ccategory 3> (N)\n- Repeat builders: \u003CN> teams previously funded by SCF\n- First-timers: \u003CN>\n\n### Notable submissions\n\n| Project | Asks | Category | Builder status | What they do |\n|---------|------|----------|----------------|--------------|\n| ... | $X K | ... | repeat \u002F first-time | one-line description |\n\n### Patterns this round\n\u003C2-3 sentences on what categories or themes are dominant>\n```\n\n### 5.5 Optional: thesis-alignment flagging\n\nFor each active submission, optionally cross-reference with:\n- `~\u002F.claude\u002Fskills\u002Fdata\u002Fideas\u002Fa16z-big-ideas-2025.json` - does this submission ride an a16z 2025 thesis (RWA, agentic payments, prediction markets, etc.)?\n- `~\u002F.claude\u002Fskills\u002Fdata\u002Fideas\u002Fyc-requests-for-startups.json` - does YC explicitly want something in this category?\n\nSubmissions that hit BOTH Stellar ecosystem-fit AND broader investor thesis are 2x more likely to win the round. Flag them as \"thesis-aligned\" in the summary table.\n\n### 6. Close with next-step suggestions\n\nIf user is considering applying:\n- Route to `scf-prescreen-checker` to test their idea against the prescreen filter\n- Route to `scf-competitor-analyst` if they're worried about overlap with other submissions\n- Route to `scf-submission-drafter` if ready to draft\n\nIf user is researching:\n- Offer to deep-dive any specific submission\n- Offer to compare against the last 3 rounds (grep historical `scf.awarded_round` patterns in `projects.json`)\n\n## Constraints\n\n- Be polite to communityfund.stellar.org - sequential fetches or low concurrency (5 max)\n- Cache fetched data in `~\u002F.stellar\u002Fcache\u002Fscf-round\u002F\u003Crec-id>.json` for the session\n- If the site is down or returns non-200, report cleanly and suggest the user visit communityfund.stellar.org directly. Do not fabricate data.\n- If dates aren't visible on the page, say \"deadline not extractable from page\" - don't speculate\n- The active-round detection assumes exactly one round has status \"Submission\" at a time. If multiple or none, surface that as a finding\n",{"name":5,"description":7},"main","db2f47e2b79822ad3d8dd0f17489d5d15bcba96d",".claude\u002Fskills\u002Fscf-round-watcher",3,"https:\u002F\u002Fgithub.com\u002FWritzProtocol\u002Fwritz","https:\u002F\u002Fwritz.xyz","https:\u002F\u002Fgithub.com\u002FWritzProtocol","https:\u002F\u002Fwritz.xyz\u002F","Native Bitcoin lending on Stellar. No bridge, no custodian.","2026-11-14 18:13:11",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add WritzProtocol\u002Fwritz --skill scf-round-watcher",{"tool":40,"command":41},"bunx","bunx skills add WritzProtocol\u002Fwritz --skill scf-round-watcher",{"tool":43,"command":44},"pnpm","pnpm dlx skills add WritzProtocol\u002Fwritz --skill scf-round-watcher","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FWritzProtocol\u002Fwritz\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fscf-round-watcher\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M77KKJ6DYZP10BJ74CW4H0AE","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\u002FWritzProtocol\u002Fwritz\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fzk-proofs\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M77KKF3SK8JVBGRY4A89HYQC","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\u002FWritzProtocol\u002Fwritz\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftyler-architect\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M77KKCD584VQA1TM1F9Q8JBH","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\u002FWritzProtocol\u002Fwritz\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fstellar-help\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M77KK7W2HKQ3QMAG0KJY1BHH","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\", or \"map the Stellar landscape for X\". 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\u002FWritzProtocol\u002Fwritz\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fstellar-competitive-landscape\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M77KK1ACXYN5AZTWR8B5CKTX","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\u002FWritzProtocol\u002Fwritz\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fstandards\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M77KJV8VW46WC58DHJR2296C","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\u002FWritzProtocol\u002Fwritz\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsmart-contracts\u002FSKILL.md",[],[]]