[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HMC5W0B7EQFAM70S8AMJS":3,"skill-same:01M71HMC5W0B7EQFAM70S8AMJS":67},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M71HMC5W0B7EQFAM70S8AMJS","organize-workspace",null,"Scans the active workspace for disposable artifacts—logs, caches, stale build output, and stray draft markdown—and proposes consolidation of scattered assets. Produces a reviewable list, asks for explicit confirmation before any delete or move, and optionally revises .gitignore. Use when the user says \"clean my room\", \"organize workspace\", \"workspace cleanup\", \"remove temp files\", \"organize assets\", \"gitignore\", or wants a safe tidy pass.","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.codex\u002Fskills\u002Forganize-workspace\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"organize","workspace","organize workspace","my","list","safe","active","markdown","delete","haiku","logs","when","confirmation","cleanup","files","tidy","clean","move","remove","consolidation","2026-11-10 10:12:30",false,"---\nname: organize-workspace\nmodel: haiku\ndescription: \"Scans the active workspace for disposable artifacts—logs, caches, stale build output, and stray draft markdown—and proposes consolidation of scattered assets. Produces a reviewable list, asks for explicit confirmation before any delete or move, and optionally revises .gitignore. Use when the user says \\\"clean my room\\\", \\\"organize workspace\\\", \\\"workspace cleanup\\\", \\\"remove temp files\\\", \\\"organize assets\\\", \\\"gitignore\\\", or wants a safe tidy pass.\"\n---\n\n# Organize Workspace\n> **HARD GATE** — **HARD GATE** — Workspace structure must reflect domain structure. If the codebase feels disorganized, flag it. Disorganization != 'just a style thing;' it is a signal of domain misalignment.\n\n\n## Principles\n\n- **Read-only first**: inventory and size (`du`, `ls -la`) before any change.\n- **Never delete or move** without a numbered list and **explicit user approval** (item-level or \"approve all\").\n- **Prefer `fd` \u002F `ripgrep` \u002F `find`** in that order; avoid blind `rm -rf` on vague globs.\n- **Do not** touch `.git\u002F`, `node_modules\u002F`, `venv\u002F`, `.env*`, or SSH keys; flag them only if the user asked about them.\n- Confirm prompts in the **user's language** if they are not writing in English.\n\n## 1. Establish scope\n\n- Default: **current project root** (where the user is working) or the path they name.\n- Record OS (macOS vs Linux) for ignore patterns (e.g. `.DS_Store`).\n\n## 2. Classify candidates (scan)\n\nGroup findings under these **buckets**:\n\n| Bucket | Examples | Typical action |\n|--------|----------|----------------|\n| **Logs & temp** | `*.log`, `logs\u002F`, `tmp\u002F`, `temp\u002F`, `*.pid` | Delete after confirm |\n| **Build \u002F cache** | `dist\u002F`, `build\u002F`, `.next\u002F`, `coverage\u002F`, `.turbo\u002F` | Delete if rebuildable |\n| **Package caches** | root `.cache\u002F`, `__pycache__\u002F` | Offer delete |\n| **Stray drafts** | root-level `*.md` named `draft`, `scratch`, `temp` | User picks: delete, move to `specs\u002F`, or keep |\n| **Duplicate \u002F dump dirs** | `old\u002F`, `backup\u002F`, `copy\u002F`, `*_backup` | List + ask |\n\nUse quick size hints: `du -sh` per top-level dir; sort large items first.\n\n## 3. Assets & data (organize, not only delete)\n\nIf the user wants **organization**:\n\n1. Propose a **single convention**, e.g.:\n   - `assets\u002F` — images, fonts, static media\n   - `data\u002F` — JSON, CSV, fixtures, samples\n   - `specs\u002F` — all planning and domain documents\n2. For each cluster of loose files, suggest **one target path** and a short rationale.\n3. Use **git-aware moves** when in a repo: `git mv` if tracked; otherwise `mv` and report.\n4. Never move secrets or production DB dumps into `docs\u002F` or public `assets\u002F`.\n\n## 4. Present the plan\n\nOutput a table or numbered list:\n\n- Path\n- Kind (log \u002F build \u002F draft \u002F asset \u002F other)\n- Approx size\n- Proposed action: **delete** | **move to …** | **keep**\n\nAsk: *\"Delete items 1–3? Move 4–5? Skip 6?\"*\n\n## 5. Execute after approval\n\n- Deletes: on macOS, prefer a Trash-capable tool (e.g. `trash` from Homebrew) if installed; else `rm` with paths echoed back.\n- Moves: create dirs with `mkdir -p` first; one batch at a time.\n- **Verify**: re-run listing on affected parents; if anything failed, report stderr.\n\n## 6. Post-cleanup and `.gitignore` revision\n\nDo this when the repo is under Git and the cleanup surfaced **untracked** noise:\n\n1. **Inventory ignore sources**: root `.gitignore`, `.git\u002Finfo\u002Fexclude`, any subpackage `.gitignore` files.\n2. **Map findings to rules**: for each deleted or recurring artifact class, check whether a pattern already exists; note gaps.\n3. **Propose a patch**: list only **concrete** changes — `+` add \u002F `-` remove \u002F `~` reword — with one-line why.\n4. **User must approve** the exact diff before editing the file.\n5. **Verify**: run `git check-ignore -v \u003Cpath>` on 2–3 representative paths.\n\nSee [REFERENCE.md](REFERENCE.md) for shell patterns, `.gitignore` mechanics, and safety checks.\n\n\n\n\u003C!-- story: e04s03 -->\n\n---\n\n# clean-my-room — reference patterns\n\nOptional commands for the agent. Adapt paths; **dry-run** before bulk delete.\n\n## Discover large top-level entries\n\n```sh\ndu -sh .\u002F* .[!.]* 2>\u002Fdev\u002Fnull | sort -hr | head -30\n```\n\n## Find common logs (respect `.gitignore` when using fd)\n\n```sh\nfd -t f '\\.log$' . 2>\u002Fdev\u002Fnull\nfd 'npm-debug' . 2>\u002Fdev\u002Fnull\n```\n\n## Find build-like dirs (review list before `rm -rf`)\n\n```sh\nfd -t d '^(dist|build|out|target|\\.next|coverage)$' . --max-depth 3 2>\u002Fdev\u002Fnull\n```\n\n## Stray markdown at repo root (heuristic)\n\n```sh\nls -1 .\u002F*.md 2>\u002Fdev\u002Fnull\nfd -t f '^(draft|scratch|untitled|TODO|notes)' . --max-depth 1 2>\u002Fdev\u002Fnull\n```\n\n## Git-safe moves\n\n```sh\ngit status -sb\ngit check-ignore -v \u003Cpath>   # was ignored?\n# Tracked: git mv old new\n# Untracked: mkdir -p … && mv old new\n```\n\n## `.gitignore` revision (after cleanup)\n\n**Goal:** stop regenerated junk from polluting `git status`, without hiding real source.\n\n1. **Read** root `.gitignore` and, in monorepos, `apps\u002F*\u002F.gitignore` \u002F `packages\u002F*\u002F.gitignore` as needed. Check **`.git\u002Finfo\u002Fexclude`** for machine-only rules that should *not* be committed (keep personal noise there; don’t copy into shared `.gitignore` unless the team agrees).\n2. **Per-path checks** (last match wins; shows which file defined the rule):\n\n   ```sh\n   git check-ignore -v path\u002Fto\u002Fartifact\n   git status -u --ignored    # optional: see ignored names (noisy)\n   ```\n\n3. **Pattern style**\n   - Leading `\u002F` = relative to the `.gitignore`’s directory (e.g. `\u002Fdist\u002F` = only that folder at that level, not all nested `dist` unless intended).\n   - `**` for deep trees, e.g. `**\u002F*.log`, when noise appears at many depths.\n   - **Negation** (`!`) is tricky: later rules, parent dirs, and `git add -f` interact—prefer narrow positive ignores over `!` unless you already use negation in that file.\n4. **Do not** add rules that would ignore: application source, small JSON\u002FYAML config the repo tracks, or `!important` assets. When unsure, run `git check-ignore -v` on a *known good* file that must stay tracked.\n5. **Tracked but should be ignored** (user already committed `build\u002F` once): this skill does not silently fix history; flag `git rm -r --cached \u003Cpath>` + `.gitignore` as a **separate** explicit step the user must approve.\n6. **Global excludes** (optional heads-up for “why is this still ignored?”):\n\n   ```sh\n   git config --get core.excludesfile\n   ```\n\n## Safety: never pass through these in automated deletes\n\n- `.git\u002F`, `.svn\u002F`, `.hg\u002F`\n- `node_modules\u002F`, `vendor\u002F`, `venv\u002F`, `.venv\u002F`, `__pypackages__\u002F`\n- Files matching `.env`, `.env.*` (except `.env.example` if intentional)\n- `~\u002F.ssh`, `id_rsa*`, `*.pem` inside project trees\n\n## Post-deploy \u002F server-ish extras (name buckets to stack)\n\n- Docker: dangling images\u002Fvolumes (only if user asked for Docker cleanup; requires `docker` context).\n- CI: `*.log` under `build\u002F`, artifact dirs from previous runs.\n- K8s: local `*.kube`, tmp kubeconfigs—list only; do not delete without confirmation.\n\n## Inspiration\n\n- Same **inventory → plan → confirm → act** flow as [post-deploy environment cleanup](https:\u002F\u002Fmcpmarket.com\u002Ftools\u002Fskills\u002Fpost-deploy-environment-cleanup) style workflows.\n- [Agent template public](https:\u002F\u002Fgithub.com\u002Fmatsuni-kk\u002Fagent_template_public): honor **Flow** (draft) vs **Stock** (stable); do not “clean” user drafts from Flow without explicit approval.\n","# Organize Workspace\n> **HARD GATE** — **HARD GATE** — Workspace structure must reflect domain structure. If the codebase feels disorganized, flag it. Disorganization != 'just a style thing;' it is a signal of domain misalignment.\n\n\n## Principles\n\n- **Read-only first**: inventory and size (`du`, `ls -la`) before any change.\n- **Never delete or move** without a numbered list and **explicit user approval** (item-level or \"approve all\").\n- **Prefer `fd` \u002F `ripgrep` \u002F `find`** in that order; avoid blind `rm -rf` on vague globs.\n- **Do not** touch `.git\u002F`, `node_modules\u002F`, `venv\u002F`, `.env*`, or SSH keys; flag them only if the user asked about them.\n- Confirm prompts in the **user's language** if they are not writing in English.\n\n## 1. Establish scope\n\n- Default: **current project root** (where the user is working) or the path they name.\n- Record OS (macOS vs Linux) for ignore patterns (e.g. `.DS_Store`).\n\n## 2. Classify candidates (scan)\n\nGroup findings under these **buckets**:\n\n| Bucket | Examples | Typical action |\n|--------|----------|----------------|\n| **Logs & temp** | `*.log`, `logs\u002F`, `tmp\u002F`, `temp\u002F`, `*.pid` | Delete after confirm |\n| **Build \u002F cache** | `dist\u002F`, `build\u002F`, `.next\u002F`, `coverage\u002F`, `.turbo\u002F` | Delete if rebuildable |\n| **Package caches** | root `.cache\u002F`, `__pycache__\u002F` | Offer delete |\n| **Stray drafts** | root-level `*.md` named `draft`, `scratch`, `temp` | User picks: delete, move to `specs\u002F`, or keep |\n| **Duplicate \u002F dump dirs** | `old\u002F`, `backup\u002F`, `copy\u002F`, `*_backup` | List + ask |\n\nUse quick size hints: `du -sh` per top-level dir; sort large items first.\n\n## 3. Assets & data (organize, not only delete)\n\nIf the user wants **organization**:\n\n1. Propose a **single convention**, e.g.:\n   - `assets\u002F` — images, fonts, static media\n   - `data\u002F` — JSON, CSV, fixtures, samples\n   - `specs\u002F` — all planning and domain documents\n2. For each cluster of loose files, suggest **one target path** and a short rationale.\n3. Use **git-aware moves** when in a repo: `git mv` if tracked; otherwise `mv` and report.\n4. Never move secrets or production DB dumps into `docs\u002F` or public `assets\u002F`.\n\n## 4. Present the plan\n\nOutput a table or numbered list:\n\n- Path\n- Kind (log \u002F build \u002F draft \u002F asset \u002F other)\n- Approx size\n- Proposed action: **delete** | **move to …** | **keep**\n\nAsk: *\"Delete items 1–3? Move 4–5? Skip 6?\"*\n\n## 5. Execute after approval\n\n- Deletes: on macOS, prefer a Trash-capable tool (e.g. `trash` from Homebrew) if installed; else `rm` with paths echoed back.\n- Moves: create dirs with `mkdir -p` first; one batch at a time.\n- **Verify**: re-run listing on affected parents; if anything failed, report stderr.\n\n## 6. Post-cleanup and `.gitignore` revision\n\nDo this when the repo is under Git and the cleanup surfaced **untracked** noise:\n\n1. **Inventory ignore sources**: root `.gitignore`, `.git\u002Finfo\u002Fexclude`, any subpackage `.gitignore` files.\n2. **Map findings to rules**: for each deleted or recurring artifact class, check whether a pattern already exists; note gaps.\n3. **Propose a patch**: list only **concrete** changes — `+` add \u002F `-` remove \u002F `~` reword — with one-line why.\n4. **User must approve** the exact diff before editing the file.\n5. **Verify**: run `git check-ignore -v \u003Cpath>` on 2–3 representative paths.\n\nSee [REFERENCE.md](REFERENCE.md) for shell patterns, `.gitignore` mechanics, and safety checks.\n\n\n\n\u003C!-- story: e04s03 -->\n\n---\n\n# clean-my-room — reference patterns\n\nOptional commands for the agent. Adapt paths; **dry-run** before bulk delete.\n\n## Discover large top-level entries\n\n```sh\ndu -sh .\u002F* .[!.]* 2>\u002Fdev\u002Fnull | sort -hr | head -30\n```\n\n## Find common logs (respect `.gitignore` when using fd)\n\n```sh\nfd -t f '\\.log$' . 2>\u002Fdev\u002Fnull\nfd 'npm-debug' . 2>\u002Fdev\u002Fnull\n```\n\n## Find build-like dirs (review list before `rm -rf`)\n\n```sh\nfd -t d '^(dist|build|out|target|\\.next|coverage)$' . --max-depth 3 2>\u002Fdev\u002Fnull\n```\n\n## Stray markdown at repo root (heuristic)\n\n```sh\nls -1 .\u002F*.md 2>\u002Fdev\u002Fnull\nfd -t f '^(draft|scratch|untitled|TODO|notes)' . --max-depth 1 2>\u002Fdev\u002Fnull\n```\n\n## Git-safe moves\n\n```sh\ngit status -sb\ngit check-ignore -v \u003Cpath>   # was ignored?\n# Tracked: git mv old new\n# Untracked: mkdir -p … && mv old new\n```\n\n## `.gitignore` revision (after cleanup)\n\n**Goal:** stop regenerated junk from polluting `git status`, without hiding real source.\n\n1. **Read** root `.gitignore` and, in monorepos, `apps\u002F*\u002F.gitignore` \u002F `packages\u002F*\u002F.gitignore` as needed. Check **`.git\u002Finfo\u002Fexclude`** for machine-only rules that should *not* be committed (keep personal noise there; don’t copy into shared `.gitignore` unless the team agrees).\n2. **Per-path checks** (last match wins; shows which file defined the rule):\n\n   ```sh\n   git check-ignore -v path\u002Fto\u002Fartifact\n   git status -u --ignored    # optional: see ignored names (noisy)\n   ```\n\n3. **Pattern style**\n   - Leading `\u002F` = relative to the `.gitignore`’s directory (e.g. `\u002Fdist\u002F` = only that folder at that level, not all nested `dist` unless intended).\n   - `**` for deep trees, e.g. `**\u002F*.log`, when noise appears at many depths.\n   - **Negation** (`!`) is tricky: later rules, parent dirs, and `git add -f` interact—prefer narrow positive ignores over `!` unless you already use negation in that file.\n4. **Do not** add rules that would ignore: application source, small JSON\u002FYAML config the repo tracks, or `!important` assets. When unsure, run `git check-ignore -v` on a *known good* file that must stay tracked.\n5. **Tracked but should be ignored** (user already committed `build\u002F` once): this skill does not silently fix history; flag `git rm -r --cached \u003Cpath>` + `.gitignore` as a **separate** explicit step the user must approve.\n6. **Global excludes** (optional heads-up for “why is this still ignored?”):\n\n   ```sh\n   git config --get core.excludesfile\n   ```\n\n## Safety: never pass through these in automated deletes\n\n- `.git\u002F`, `.svn\u002F`, `.hg\u002F`\n- `node_modules\u002F`, `vendor\u002F`, `venv\u002F`, `.venv\u002F`, `__pypackages__\u002F`\n- Files matching `.env`, `.env.*` (except `.env.example` if intentional)\n- `~\u002F.ssh`, `id_rsa*`, `*.pem` inside project trees\n\n## Post-deploy \u002F server-ish extras (name buckets to stack)\n\n- Docker: dangling images\u002Fvolumes (only if user asked for Docker cleanup; requires `docker` context).\n- CI: `*.log` under `build\u002F`, artifact dirs from previous runs.\n- K8s: local `*.kube`, tmp kubeconfigs—list only; do not delete without confirmation.\n\n## Inspiration\n\n- Same **inventory → plan → confirm → act** flow as [post-deploy environment cleanup](https:\u002F\u002Fmcpmarket.com\u002Ftools\u002Fskills\u002Fpost-deploy-environment-cleanup) style workflows.\n- [Agent template public](https:\u002F\u002Fgithub.com\u002Fmatsuni-kk\u002Fagent_template_public): honor **Flow** (draft) vs **Stock** (stable); do not “clean” user drafts from Flow without explicit approval.\n",{"name":5,"model":28,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa",".codex\u002Fskills\u002Forganize-workspace",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add danielvm-git\u002Fbigpowers --skill organize-workspace",{"tool":59,"command":60},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill organize-workspace",{"tool":62,"command":63},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill organize-workspace","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Forganize-workspace\u002FSKILL.md",true,[],[68,89,96,124,147,168],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":79,"publishedAt":39},"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",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[80,81,82,83,84,85,86,87,88],"fixture","open","verify","skill verify fail open fixture","skill verify","path","run","for","never",{"skillNo":90,"name":91,"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":92,"categories":93,"keywords":94,"publishedAt":39},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[95,85],"negative path",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":105,"publishedAt":39},"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",[102],{"categoryNo":103,"categoryName":104,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000002","文档处理",[106,107,108,109,110,111,112,113,114,115,116,30,117,118,119,120,19,121,122,123],"write","write document","document","documents","actionable","technical","methodology","high","bmad","standard","use","minimal","bold","sonnet","integrity","sync","directory","guides",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":39},"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",[],[131,132,133,115,134,116,135,136,137,138,119,139,140,141,142,143,144,30,145,146],"observability","wire observability","readiness","commands","development","as","logging","add","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":39},"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",[],[154,155,156,157,158,159,160,161,162,163,164,115,165,87,131,119,166,167],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","with","ci pipeline setup","git","workflows",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":185,"publishedAt":39},"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",[174,177,182],{"categoryNo":175,"categoryName":176,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":178,"categoryName":179,"taxonomyType":180,"taxonomyTypeDesc":181},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":183,"categoryName":184,"taxonomyType":180,"taxonomyTypeDesc":181},"01JBSEEDCAT000000000000033","数据分析师",[186,187,188,189,190,191,192,193,194,119,195,196,197,198,199,200,201,145,202,203],"dashboard","visual","visual dashboard","status","artifacts","http","plans","planning","panel","start","release","opencode","plan","browser","api","architecture","project status","http api"]