[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HA74F7A17KCJCYBTHCZND":3,"skill-same:01M71HA74F7A17KCJCYBTHCZND":70},{"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":23,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M71HA74F7A17KCJCYBTHCZND","craft-skill",null,"Create new bigpowers skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill for the bigpowers lifecycle.","danielvm-git\u002Fbigpowers","danielvm-git","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1020864?v=4","01M71H1N1CTQ529S0KN7KETVG6","Daniel V M","01M71H1N218Y3S8WHCJ58NPRSW",289,"MIT","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.codebuddy\u002Fskills\u002Fcraft-skill\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"craft","craft skill","user","build","with","progressive disclosure","use","progressive","lifecycle","for","sonnet","new skill","write","structure","create","when","new","resources","2026-11-10 10:12:30",false,"---\nname: craft-skill\nmodel: sonnet\ndescription: \"Create new bigpowers skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill for the bigpowers lifecycle.\"\n---\n\n# Craft Skill\n\n> **HARD GATE** — Do NOT name a skill without a two-word verb-noun pair. Do NOT merge a new skill without running `sync-skills.sh`. Generated `.cursor\u002Frules\u002F` and `.gemini\u002F` artifacts MUST match the source SKILL.md.\n\n## CSO Description Discipline (e45s02)\n\nThe YAML `description` is the **Catalog Selection Object** — the only field agents see when picking a skill.\n\n| Rule | Limit |\n|------|-------|\n| Max length | 1024 characters |\n| Voice | Third person |\n| Content | Capability + `Use when …` triggers only |\n| Forbidden | Workflow steps, phase chains, numbered lists, `→ verify:`, HARD GATE prose |\n\nMove process detail into the SKILL.md body or REFERENCE.md — never into `description`.\n\n## Agentic STE body discipline (e79s02)\n\nSkill-body instructional prose MUST follow [AGENTIC-STE.md](..\u002F..\u002Fdocs\u002FAGENTIC-STE.md).\n\n| Rule | Limit |\n|------|-------|\n| Sentence length | ≤20 words per instruction sentence |\n| Voice | Imperative, active |\n| Directive terms | MUST, MUST NOT, NEVER, ALWAYS, DO, DO NOT |\n| Banned modals | should, might, could, may, consider, try, generally, typically |\n| Scope | SKILL.md body only — not YAML `description`, not `terse-mode` output |\n\n> **HARD GATE** — Do NOT merge a new or edited skill until `bash scripts\u002Fvalidate-agentic-ste.sh --strict skills\u002F\u003Cname>\u002FSKILL.md` exits 0. Fix violations before `sync-skills.sh`.\n\n## Process\n\n1. **Gather requirements** — ask user about:\n   - What task\u002Fdomain does the skill cover?\n   - Which use cases must the skill handle?\n   - Does it need executable scripts or just instructions?\n   - Any reference materials to include?\n   - What specs\u002F output does it produce (if any)?\n\n2. **Verify Principles** — Ensure the skill aligns with [PRINCIPLES.md](..\u002F..\u002Fdocs\u002FPRINCIPLES.md):\n   - Is it atomic (verb-noun)?\n   - Is it \"deep\" (simple interface, complex internal logic)?\n   - Does it include Hard Gates?\n   - Is it verifiable with a `.feature` file?\n\n3. **Draft the skill** — create:\n   - SKILL.md with concise instructions (see [REFERENCE.md](REFERENCE.md) for template)\n   - Additional reference files if content exceeds 100 lines\n   - Utility scripts if deterministic operations needed\n\n   **Auto-skill from library README:** When user provides a library README or API docs URL, extract triggers and HARD GATEs.\n   Draft verify commands and specs\u002F output into SKILL.md. Do NOT invent APIs not in the source.\n\n4. Add `model:` frontmatter (`haiku` | `sonnet` | `opus`) per [model-profiles.md](..\u002F..\u002Fdocs\u002Freferences\u002Fmodel-profiles.md).\n\n> **STREAM CONTINUITY** — When writing file content, output in continuous chunks of ~200 lines. Do not pause. Continue immediately until complete. If you need time, emit a placeholder comment rather than going silent.\n\n5. **Review with user** — present draft and ask:\n   - Does this cover your use cases?\n   - Anything missing or unclear?\n   - Does any section need more or less detail?\n\n6. **Completion-honesty gate (HARD GATE — e45s02)** — Before declaring done:\n   - Run `bash scripts\u002Fvalidate-skill-description.sh skills\u002F\u003Cname>\u002FSKILL.md` — must exit 0\n   - Run `bash scripts\u002Fvalidate-agentic-ste.sh --strict skills\u002F\u003Cname>\u002FSKILL.md` — must exit 0 (e79s02)\n   - Run `bash scripts\u002Fsync-skills.sh` — must complete without error\n   - Run `bash scripts\u002Frun-skill-verify.sh \u003Cname>` if the skill defines a verify command\n   - Show terminal output for each — narration without evidence is rejected\n\n## Naming Rules\n\nEvery skill name must be a **two-word verb-noun pair**. See [REFERENCE.md](REFERENCE.md) for full rules, examples, and documented exceptions.\n\n## specs\u002F Output\n\nIf the skill produces written output, it goes in `specs\u002F` at the project root. Document the output file path in the skill body and in CONVENTIONS.md's output files table.\n\n## Review Checklist\n\nAfter drafting, verify:\n\n- [ ] Name is a two-word verb-noun pair (or follows grill-me exception)\n- [ ] Description \u003C 1024 chars, triggers only, no workflow-summary leakage\n- [ ] Description includes triggers (\"Use when...\")\n- [ ] SKILL.md under 100 lines\n- [ ] No time-sensitive info\n- [ ] Consistent terminology with CONVENTIONS.md\n- [ ] specs\u002F output documented if applicable\n- [ ] `validate-skill-description.sh` exits 0\n- [ ] `validate-agentic-ste.sh --strict` exits 0 (e79s02)\n- [ ] `sync-skills.sh` run to propagate to Cursor\u002FGemini\n- [ ] `bash scripts\u002Fvalidate-skill-catalog.sh` passes for the new skill (HARD GATE — completion honesty)\n\n> **HARD GATE** — Do NOT declare the skill done until `bash scripts\u002Fvalidate-skill-catalog.sh --strict --skill \u003Cname>` exits 0. Validator enforces verb-noun name, HARD GATE block, description ≤1024 chars, and `→ verify:` command.\n\n## Verify\n\n→ verify: `bash scripts\u002Fvalidate-skill-catalog.sh --strict --skill craft-skill && bash scripts\u002Fvalidate-skill-description.sh skills\u002Fcraft-skill\u002FSKILL.md`\n\n---\n\n# Craft Skill — Reference\n\n## Naming Rules (full)\n\nEvery skill name must be a **two-word verb-noun pair**:\n- First word: a verb (survey, model, define, develop, audit…)\n- Second word: a noun from PMBOK 6 \u002F Agile vocabulary (context, domain, language, tdd, code…)\n- Pronounceable in any language, searchable, no noise words, no encodings\n- Exception precedent: `grill-me` — kept for recognizability\n\nGood: `survey-context`, `audit-code`, `validate-fix`\nBad: `context-surveyor`, `code-auditing-skill`, `fix-validator`\n\nAny new naming exception requires an entry in CONVENTIONS.md before the skill is published.\n\n## Skill Structure\n\n```\nskill-name\u002F\n├── SKILL.md           # Main instructions (required)\n├── REFERENCE.md       # Detailed docs (if needed)\n├── EXAMPLES.md        # Usage examples (if needed)\n└── scripts\u002F           # Utility scripts (if needed)\n    └── helper.sh\n```\n\n## SKILL.md Template\n\n```md\n---\nname: skill-name\ndescription: Brief description of capability. Use when [specific triggers].\n---\n\n# Skill Name\n\n## Quick start\n\n[Minimal working example]\n\n## Workflows\n\n[Step-by-step processes with checklists for complex tasks]\n\n## Advanced features\n\n[Link to separate files: See [REFERENCE.md](REFERENCE.md)]\n```\n\n## Description Requirements\n\nThe description is **the only thing your agent sees** when deciding which skill to load.\n\n**Format**:\n- Max 1024 chars\n- Write in third person\n- First sentence: what it does\n- Second sentence: \"Use when [specific triggers]\"\n\n**Good example**:\n```\nInvestigate a bug by exploring the codebase to find root cause, then write a TDD-based fix plan to specs\u002Fbugs\u002FBUG-*.md. Use when user reports a bug, wants to investigate a problem, or mentions \"triage\".\n```\n\n## When to Add Scripts\n\nAdd utility scripts when:\n- Operation is deterministic (validation, formatting)\n- Same code would be generated repeatedly\n- Errors need explicit handling\n\n## When to Split Files\n\nSplit into separate files when:\n- SKILL.md exceeds 100 lines\n- Content has distinct domains\n- Advanced features are rarely needed\n\n## sync-skills.sh Propagation\n\nAfter adding a new skill directory with SKILL.md, run `scripts\u002Fsync-skills.sh` from the bigpowers repo root. This automatically generates:\n- `.cursor\u002Frules\u002F\u003Cname>.mdc` — for Cursor\n- `.gemini\u002Fextensions\u002Fbigpowers\u002Fskills\u002F\u003Cname>\u002FSKILL.md` — Agent Skill\n- `.gemini\u002Fextensions\u002Fbigpowers\u002Fcommands\u002F\u003Cname>.toml` — Slash Command\n- `.gemini\u002Fextensions\u002Fbigpowers\u002Fcommands\u002Fprompts\u002F\u003Cname>.md` — Command Prompt\n- Updated `gemini-extension.json`\n\nverify: `bash scripts\u002Fsync-skills.sh 2>&1 | grep \"skills synced\"`\n","# Craft Skill\n\n> **HARD GATE** — Do NOT name a skill without a two-word verb-noun pair. Do NOT merge a new skill without running `sync-skills.sh`. Generated `.cursor\u002Frules\u002F` and `.gemini\u002F` artifacts MUST match the source SKILL.md.\n\n## CSO Description Discipline (e45s02)\n\nThe YAML `description` is the **Catalog Selection Object** — the only field agents see when picking a skill.\n\n| Rule | Limit |\n|------|-------|\n| Max length | 1024 characters |\n| Voice | Third person |\n| Content | Capability + `Use when …` triggers only |\n| Forbidden | Workflow steps, phase chains, numbered lists, `→ verify:`, HARD GATE prose |\n\nMove process detail into the SKILL.md body or REFERENCE.md — never into `description`.\n\n## Agentic STE body discipline (e79s02)\n\nSkill-body instructional prose MUST follow [AGENTIC-STE.md](..\u002F..\u002Fdocs\u002FAGENTIC-STE.md).\n\n| Rule | Limit |\n|------|-------|\n| Sentence length | ≤20 words per instruction sentence |\n| Voice | Imperative, active |\n| Directive terms | MUST, MUST NOT, NEVER, ALWAYS, DO, DO NOT |\n| Banned modals | should, might, could, may, consider, try, generally, typically |\n| Scope | SKILL.md body only — not YAML `description`, not `terse-mode` output |\n\n> **HARD GATE** — Do NOT merge a new or edited skill until `bash scripts\u002Fvalidate-agentic-ste.sh --strict skills\u002F\u003Cname>\u002FSKILL.md` exits 0. Fix violations before `sync-skills.sh`.\n\n## Process\n\n1. **Gather requirements** — ask user about:\n   - What task\u002Fdomain does the skill cover?\n   - Which use cases must the skill handle?\n   - Does it need executable scripts or just instructions?\n   - Any reference materials to include?\n   - What specs\u002F output does it produce (if any)?\n\n2. **Verify Principles** — Ensure the skill aligns with [PRINCIPLES.md](..\u002F..\u002Fdocs\u002FPRINCIPLES.md):\n   - Is it atomic (verb-noun)?\n   - Is it \"deep\" (simple interface, complex internal logic)?\n   - Does it include Hard Gates?\n   - Is it verifiable with a `.feature` file?\n\n3. **Draft the skill** — create:\n   - SKILL.md with concise instructions (see [REFERENCE.md](REFERENCE.md) for template)\n   - Additional reference files if content exceeds 100 lines\n   - Utility scripts if deterministic operations needed\n\n   **Auto-skill from library README:** When user provides a library README or API docs URL, extract triggers and HARD GATEs.\n   Draft verify commands and specs\u002F output into SKILL.md. Do NOT invent APIs not in the source.\n\n4. Add `model:` frontmatter (`haiku` | `sonnet` | `opus`) per [model-profiles.md](..\u002F..\u002Fdocs\u002Freferences\u002Fmodel-profiles.md).\n\n> **STREAM CONTINUITY** — When writing file content, output in continuous chunks of ~200 lines. Do not pause. Continue immediately until complete. If you need time, emit a placeholder comment rather than going silent.\n\n5. **Review with user** — present draft and ask:\n   - Does this cover your use cases?\n   - Anything missing or unclear?\n   - Does any section need more or less detail?\n\n6. **Completion-honesty gate (HARD GATE — e45s02)** — Before declaring done:\n   - Run `bash scripts\u002Fvalidate-skill-description.sh skills\u002F\u003Cname>\u002FSKILL.md` — must exit 0\n   - Run `bash scripts\u002Fvalidate-agentic-ste.sh --strict skills\u002F\u003Cname>\u002FSKILL.md` — must exit 0 (e79s02)\n   - Run `bash scripts\u002Fsync-skills.sh` — must complete without error\n   - Run `bash scripts\u002Frun-skill-verify.sh \u003Cname>` if the skill defines a verify command\n   - Show terminal output for each — narration without evidence is rejected\n\n## Naming Rules\n\nEvery skill name must be a **two-word verb-noun pair**. See [REFERENCE.md](REFERENCE.md) for full rules, examples, and documented exceptions.\n\n## specs\u002F Output\n\nIf the skill produces written output, it goes in `specs\u002F` at the project root. Document the output file path in the skill body and in CONVENTIONS.md's output files table.\n\n## Review Checklist\n\nAfter drafting, verify:\n\n- [ ] Name is a two-word verb-noun pair (or follows grill-me exception)\n- [ ] Description \u003C 1024 chars, triggers only, no workflow-summary leakage\n- [ ] Description includes triggers (\"Use when...\")\n- [ ] SKILL.md under 100 lines\n- [ ] No time-sensitive info\n- [ ] Consistent terminology with CONVENTIONS.md\n- [ ] specs\u002F output documented if applicable\n- [ ] `validate-skill-description.sh` exits 0\n- [ ] `validate-agentic-ste.sh --strict` exits 0 (e79s02)\n- [ ] `sync-skills.sh` run to propagate to Cursor\u002FGemini\n- [ ] `bash scripts\u002Fvalidate-skill-catalog.sh` passes for the new skill (HARD GATE — completion honesty)\n\n> **HARD GATE** — Do NOT declare the skill done until `bash scripts\u002Fvalidate-skill-catalog.sh --strict --skill \u003Cname>` exits 0. Validator enforces verb-noun name, HARD GATE block, description ≤1024 chars, and `→ verify:` command.\n\n## Verify\n\n→ verify: `bash scripts\u002Fvalidate-skill-catalog.sh --strict --skill craft-skill && bash scripts\u002Fvalidate-skill-description.sh skills\u002Fcraft-skill\u002FSKILL.md`\n\n---\n\n# Craft Skill — Reference\n\n## Naming Rules (full)\n\nEvery skill name must be a **two-word verb-noun pair**:\n- First word: a verb (survey, model, define, develop, audit…)\n- Second word: a noun from PMBOK 6 \u002F Agile vocabulary (context, domain, language, tdd, code…)\n- Pronounceable in any language, searchable, no noise words, no encodings\n- Exception precedent: `grill-me` — kept for recognizability\n\nGood: `survey-context`, `audit-code`, `validate-fix`\nBad: `context-surveyor`, `code-auditing-skill`, `fix-validator`\n\nAny new naming exception requires an entry in CONVENTIONS.md before the skill is published.\n\n## Skill Structure\n\n```\nskill-name\u002F\n├── SKILL.md           # Main instructions (required)\n├── REFERENCE.md       # Detailed docs (if needed)\n├── EXAMPLES.md        # Usage examples (if needed)\n└── scripts\u002F           # Utility scripts (if needed)\n    └── helper.sh\n```\n\n## SKILL.md Template\n\n```md\n---\nname: skill-name\ndescription: Brief description of capability. Use when [specific triggers].\n---\n\n# Skill Name\n\n## Quick start\n\n[Minimal working example]\n\n## Workflows\n\n[Step-by-step processes with checklists for complex tasks]\n\n## Advanced features\n\n[Link to separate files: See [REFERENCE.md](REFERENCE.md)]\n```\n\n## Description Requirements\n\nThe description is **the only thing your agent sees** when deciding which skill to load.\n\n**Format**:\n- Max 1024 chars\n- Write in third person\n- First sentence: what it does\n- Second sentence: \"Use when [specific triggers]\"\n\n**Good example**:\n```\nInvestigate a bug by exploring the codebase to find root cause, then write a TDD-based fix plan to specs\u002Fbugs\u002FBUG-*.md. Use when user reports a bug, wants to investigate a problem, or mentions \"triage\".\n```\n\n## When to Add Scripts\n\nAdd utility scripts when:\n- Operation is deterministic (validation, formatting)\n- Same code would be generated repeatedly\n- Errors need explicit handling\n\n## When to Split Files\n\nSplit into separate files when:\n- SKILL.md exceeds 100 lines\n- Content has distinct domains\n- Advanced features are rarely needed\n\n## sync-skills.sh Propagation\n\nAfter adding a new skill directory with SKILL.md, run `scripts\u002Fsync-skills.sh` from the bigpowers repo root. This automatically generates:\n- `.cursor\u002Frules\u002F\u003Cname>.mdc` — for Cursor\n- `.gemini\u002Fextensions\u002Fbigpowers\u002Fskills\u002F\u003Cname>\u002FSKILL.md` — Agent Skill\n- `.gemini\u002Fextensions\u002Fbigpowers\u002Fcommands\u002F\u003Cname>.toml` — Slash Command\n- `.gemini\u002Fextensions\u002Fbigpowers\u002Fcommands\u002Fprompts\u002F\u003Cname>.md` — Command Prompt\n- Updated `gemini-extension.json`\n\nverify: `bash scripts\u002Fsync-skills.sh 2>&1 | grep \"skills synced\"`\n",{"name":5,"model":34,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa",".codebuddy\u002Fskills\u002Fcraft-skill",24,"https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers","https:\u002F\u002Fdanielvm-git.github.io\u002Fbigpowers\u002F","https:\u002F\u002Fgithub.com\u002Fdanielvm-git","danielvm.net","2026-11-10 01:18:54",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add danielvm-git\u002Fbigpowers --skill craft-skill",{"tool":62,"command":63},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill craft-skill",{"tool":65,"command":66},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill craft-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.codebuddy\u002Fskills\u002Fcraft-skill\u002FSKILL.md",true,[],[71,87,94,120,143,163],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":78,"publishedAt":42},"01M71KBG9F8X644MJB16H4V8M7","skill-verify-fail-open-fixture","Negative-path fixture for run-skill-verify.sh — must never PASS.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fskill-verify-fail-open\u002FSKILL.md",[77],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[79,80,81,82,83,84,85,33,86],"fixture","open","verify","skill verify fail open fixture","skill verify","path","run","never",{"skillNo":88,"name":89,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":42},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[93,84],"negative path",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":103,"publishedAt":42},"01M71KBBGF7Y4EB4AMHBZ8CJFC","write-document","Write, organize, and sync high-integrity technical documents using the BMAD methodology. Ensures every document is Bold, Minimal, Actionable, and Durable. Use when creating architectural docs, technical guides, or organizing the specs\u002F directory.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-document\u002FSKILL.md",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",[36,104,105,106,107,108,109,110,111,112,30,39,113,114,34,115,116,117,118,119],"write document","document","documents","actionable","technical","methodology","high","bmad","standard","minimal","bold","integrity","organize","sync","directory","guides",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":42},"01M71KB8TM089JJD5AY5KAFSDM","wire-observability","Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwire-observability\u002FSKILL.md",[],[127,128,129,112,130,30,131,132,133,134,34,135,136,137,138,139,140,39,141,142],"observability","wire observability","readiness","commands","development","as","logging","add","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":42},"01M71KB6CNRANP449DQA3NJZ96","wire-ci","CI pipeline setup with bundled, forge-neutral templates and local validation. Detects the forge from the git remote, generates workflows for supported forges, and skips honestly for the rest. The CI equivalent of wire-observability.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwire-ci\u002FSKILL.md",[],[150,151,152,153,154,155,156,157,158,159,28,112,160,33,127,34,161,162],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","ci pipeline setup","git","workflows",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":180,"publishedAt":42},"01M71KB2ZV98P03X88QR8MT9F1","visual-dashboard","Start a browser-based dashboard that visualizes architecture, implementation plans, and project status. Persists artifacts in .bigpowers\u002Fdashboard\u002F. Reads specs\u002Fstate.yaml, release-plan.yaml, epics, and planning-status via HTTP API or opencode panel.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-dashboard\u002FSKILL.md",[169,172,177],{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":173,"categoryName":174,"taxonomyType":175,"taxonomyTypeDesc":176},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":178,"categoryName":179,"taxonomyType":175,"taxonomyTypeDesc":176},"01JBSEEDCAT000000000000033","数据分析师",[181,182,183,184,185,186,187,188,189,34,190,191,192,193,194,195,196,141,197,198],"dashboard","visual","visual dashboard","status","artifacts","http","plans","planning","panel","start","release","opencode","plan","browser","api","architecture","project status","http api"]