[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DPTP6MTB614MZYR44CKQ55":3,"skill-same:01M7DPTP6MTB614MZYR44CKQ55":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},"01M7DPTP6MTB614MZYR44CKQ55","reprompt",null,"Rewrite a rough request into a sharp, structured prompt before acting on it. Use when the user says \"reprompt this\", \"reprompt\", \"improve this prompt\", \"make this prompt better\", \"structure this request\", or hands you a vague\u002Funderspecified ask you should sharpen first. Complements the automatic per-turn sharpener (the UserPromptSubmit hook) for explicit, heavier rewrites. Personalizes from ~\u002F.stellar\u002Fprofile.md when present.","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.claude\u002Fskills\u002Freprompt\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: reprompt\ndescription: Rewrite a rough request into a sharp, structured prompt before acting on it. Use when the user says \"reprompt this\", \"reprompt\", \"improve this prompt\", \"make this prompt better\", \"structure this request\", or hands you a vague\u002Funderspecified ask you should sharpen first. Complements the automatic per-turn sharpener (the UserPromptSubmit hook) for explicit, heavier rewrites. Personalizes from ~\u002F.stellar\u002Fprofile.md when present.\n---\n\n## What this skill does\n\nTurns a rough ask into a tight working spec, then acts on it — the explicit,\non-demand counterpart to the loop's automatic per-turn sharpener. Use it when a\nrequest is vague enough to be worth structuring out loud, or when the user\nliterally asks you to \"reprompt this\".\n\n## How to run it\n\n### 1. Capture the raw request\n\nTake the text the user wants sharpened (everything after \"reprompt this:\", or\nthe preceding message if they just say \"reprompt that\").\n\n### 2. Load any learned profile\n\nIf `~\u002F.stellar\u002Fprofile.md` exists (the optimizer distills it from real usage),\nread it and treat it as defaults — domain, typical scope, preferred stack,\ntone — unless the request contradicts them. Honor `STELLAR_HOME` if set.\n\n### 3. Produce the sharpened spec\n\nRewrite the request into this structure. Keep it tight; don't pad.\n\n```\nGoal:        the outcome actually wanted (not the literal words)\nContext:     relevant assumptions, environment, prior decisions\nTask:        the smallest precise action(s) that achieve the goal\nConstraints: scope limits, must-nots, non-negotiables\nSuccess:     how we'll know it's done right\n```\n\n### 4. Gate on ambiguity\n\nIf a genuine ambiguity would change the result, ask 1–3 sharp questions first\n(one at a time) and fill the spec from the answers. If it's clear enough,\nproceed directly.\n\n### 5. Act\n\nShow the sharpened spec briefly, then execute on it (or hand off to the right\nstellar-build skill — e.g. `find-stellar-idea`, `nicole-pm`, `tyler-architect`).\nDon't make the user re-approve unless a clarifying answer is still pending.\n\n## Notes\n\n- This is the manual lever. The automatic version runs every turn via the\n  `UserPromptSubmit` hook and needs no invocation; turn it off with\n  `STELLAR_BUILD_NO_REPROMPT=1`.\n- The more you use stellar-build, the better both get: `\u002Foptimize-skills`\n  refreshes `~\u002F.stellar\u002Fprofile.md` from your traces, which feeds these rewrites.\n","## What this skill does\n\nTurns a rough ask into a tight working spec, then acts on it — the explicit,\non-demand counterpart to the loop's automatic per-turn sharpener. Use it when a\nrequest is vague enough to be worth structuring out loud, or when the user\nliterally asks you to \"reprompt this\".\n\n## How to run it\n\n### 1. Capture the raw request\n\nTake the text the user wants sharpened (everything after \"reprompt this:\", or\nthe preceding message if they just say \"reprompt that\").\n\n### 2. Load any learned profile\n\nIf `~\u002F.stellar\u002Fprofile.md` exists (the optimizer distills it from real usage),\nread it and treat it as defaults — domain, typical scope, preferred stack,\ntone — unless the request contradicts them. Honor `STELLAR_HOME` if set.\n\n### 3. Produce the sharpened spec\n\nRewrite the request into this structure. Keep it tight; don't pad.\n\n```\nGoal:        the outcome actually wanted (not the literal words)\nContext:     relevant assumptions, environment, prior decisions\nTask:        the smallest precise action(s) that achieve the goal\nConstraints: scope limits, must-nots, non-negotiables\nSuccess:     how we'll know it's done right\n```\n\n### 4. Gate on ambiguity\n\nIf a genuine ambiguity would change the result, ask 1–3 sharp questions first\n(one at a time) and fill the spec from the answers. If it's clear enough,\nproceed directly.\n\n### 5. Act\n\nShow the sharpened spec briefly, then execute on it (or hand off to the right\nstellar-build skill — e.g. `find-stellar-idea`, `nicole-pm`, `tyler-architect`).\nDon't make the user re-approve unless a clarifying answer is still pending.\n\n## Notes\n\n- This is the manual lever. The automatic version runs every turn via the\n  `UserPromptSubmit` hook and needs no invocation; turn it off with\n  `STELLAR_BUILD_NO_REPROMPT=1`.\n- The more you use stellar-build, the better both get: `\u002Foptimize-skills`\n  refreshes `~\u002F.stellar\u002Fprofile.md` from your traces, which feeds these rewrites.\n",{"name":5,"description":7},"main","217c58ef684b467a1122bd3bac74141a90f974cd",".claude\u002Fskills\u002Freprompt",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 reprompt",{"tool":38,"command":39},"bunx","bunx skills add ozioziel\u002FWorkville --skill reprompt",{"tool":41,"command":42},"pnpm","pnpm dlx skills add ozioziel\u002FWorkville --skill reprompt","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Freprompt\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",[],[]]