[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CTGTQH2551Y1MNCVGC2DDP":3,"skill-same:01M6CTGTQH2551Y1MNCVGC2DDP":72},{"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":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":43,"updatedAt":44,"install":45,"resources":57},"01M6CTGTQH2551Y1MNCVGC2DDP","upgrade-company-os",null,"Checks for, previews, applies or rolls back Company OS updates. Use when you want the latest version or need to undo an upgrade.","vibbs\u002Fcompany-os","vibbs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7379149?v=4","01M6CT6M03CAS1H7RA89F3965B","Vibbs Dod","01M6CT6M4MY60C9FFQ3AAR2RSK",6,"MIT","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fupgrade-company-os\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"company os","upgrade","upgrade company os","rollback","check","use","version","back","preview","2026-11-10 10:12:30",false,"---\nname: upgrade-company-os\ndescription: Checks for, previews, applies or rolls back Company OS updates. Use when you want the latest version or need to undo an upgrade.\nruntimes:\n  claude:\n    user-invocable: true\n    argument-hint: \"[check | preview | apply | rollback]\"\n---\n\n# Upgrade Company OS\n\nChecks for updates, previews changes, upgrades, or rolls back Company OS to a previous version.\n\n## When to Use\n\n- You want to know whether a newer Company OS release exists.\n- You want to see what an upgrade would change before it touches any file.\n- You want to apply an upgrade, or undo one that went wrong.\n\n## Subcommands\n\n### `\u002Fupgrade-company-os` or `\u002Fupgrade-company-os check`\n\nCheck if an update is available:\n\n1. Read `.company-os\u002Fversion` for the currently installed version\n2. If checking against remote, advise the user to run:\n   ```bash\n   curl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fvibbs\u002Fcompany-os\u002Fmain\u002Finstall.sh | bash -s -- --check\n   ```\n   To read the script first, download it to a temporary folder, review it, then run it:\n   ```bash\n   tmp=$(mktemp -d) && curl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fvibbs\u002Fcompany-os\u002Fmain\u002Finstall.sh -o \"$tmp\u002Finstall.sh\"\n   less \"$tmp\u002Finstall.sh\"\n   bash \"$tmp\u002Finstall.sh\" --check\n   ```\n   Inside an AI tool `less` is not interactive. Show the user only the header and version lines (`head -n 20 \"$tmp\u002Finstall.sh\"`) and the path, and ask them to review the whole file in their own terminal.\n3. If `.company-os\u002Fversion` doesn't exist, inform the user this is a pre-versioning install (1.11 or earlier). The installer backs up first. A run without `--force` only previews. With no manifest, the installer compares each file with every version Company OS has shipped (`.company-os\u002Fknown-hashes.txt` in the release): a file that matches one is an unedited copy and is updated. `--force` saves each file that matches no shipped version (the user's edits) as `.company-os\u002Fconflicts\u002F\u003Cpath>.user`, then replaces it\n\nWhat you will see:\n\n```text\n  Installed:  1.11.0\n  Available:  1.12.0 (minor)\n  Update available - 1.11.0 -> 1.12.0\n```\n\nOr, when nothing is newer: `Up to date - Company OS 1.11.0`.\n\n### `\u002Fupgrade-company-os preview`\n\nPreview what would change without applying:\n\n1. Get the installer. Never run an `install.sh` that sits in the project root: it may be the user's own script or a stale download. Download the current one to a temporary folder (`curl` is denied for the agent, so the user runs this in their terminal):\n   ```bash\n   tmp=$(mktemp -d) && curl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fvibbs\u002Fcompany-os\u002Fmain\u002Finstall.sh -o \"$tmp\u002Finstall.sh\"\n   ```\n2. Check that the file is the Company OS installer before running it: `head -n 5 \"$tmp\u002Finstall.sh\"` must contain `Company OS`. If it does not, stop and tell the user. Then run it in dry-run mode:\n   ```bash\n   bash \"$tmp\u002Finstall.sh\" --dry-run --force\n   ```\n   (Downloading to a file first lets the user read the script before it runs. Piping the script straight into `bash` works too, but nothing is reviewed.)\n3. Parse and display the output — highlight new files, updated files, conflicts, and migration notes\n\nWhat you will see:\n\n```text\n  Preview  .claude\u002Fsettings.json (would merge permissions)\n  Preview: Would create 2, add 5, merge 1, update 12, skip 40.\n  Warning: 1 file(s) modified by you AND changed in template.\n  These will be saved to .company-os\u002Fconflicts\u002F on upgrade.\n  Run without --dry-run to apply these changes.\n```\n\nNothing on disk changes during a preview.\n\n### `\u002Fupgrade-company-os apply`\n\nPerform the upgrade:\n\n1. Show current version from `.company-os\u002Fversion`\n2. For MAJOR upgrades: display migration notes from `.company-os\u002Fdocs\u002FCHANGELOG.md` and ask for confirmation before proceeding\n3. Run the upgrade:\n   ```bash\n   bash \"$tmp\u002Finstall.sh\" --force\n   ```\n   Use the same verified download as in preview. If the shell has no `$tmp`, download again to a new temporary folder and run the same header check. The user can also run these steps in their own terminal after reading the file with `less \"$tmp\u002Finstall.sh\"`.\n   To upgrade to a specific release instead of the latest, pin it with `--version`, for example `bash \"$tmp\u002Finstall.sh\" --force --version 1.12.0`. Pinning also works for a downgrade or when a team wants everyone on the same version.\n4. After upgrade, verify with:\n   ```bash\n   .\u002Ftools\u002Fregistry\u002Fhealth-check.sh\n   ```\n5. Display post-upgrade summary including new version from `.company-os\u002Fversion`\n6. If conflicts were detected (`.company-os\u002Fconflicts\u002F` exists and is non-empty), list the conflicted files and advise manual resolution\n\nWhat you will see:\n\n```text\n  Backup   Created at .company-os\u002Fbackup\u002F20261013-101500-v1.11.0\n  ...file-by-file results...\n  1 conflict(s) detected - your modified versions saved to .company-os\u002Fconflicts\u002F\n  Review the conflicts and merge manually.\n```\n\nEach conflict keeps the folder path of the original file, so same-named files never collide. A file the user edited that the template did not change is left alone and is not a conflict. A plain upgrade (no `--force`) keeps the user's version of a conflicting file and lists it; `--force` saves both and installs the template copy. A saved copy is never overwritten: a later one gets a timestamp suffix. Upgrades keep the adapters the project already has. For example, a changed `tools\u002Fqa\u002Frun.sh` is saved as `.company-os\u002Fconflicts\u002Ftools\u002Fqa\u002Frun.sh.user` (your version) and `run.sh.new` (the template version). Merge what you want to keep, then delete the conflict files. If you see `Up to date`, there was nothing to apply. The guides in `.company-os\u002Fdocs\u002F` are template-owned and always refreshed on upgrade; a guide the user edited is kept next to the new copy as `\u003Cname>.user` (for example `.company-os\u002Fdocs\u002FSETUP.md.user`).\n\n### `\u002Fupgrade-company-os rollback`\n\nRestore from a previous backup:\n\n1. List available backups:\n   ```bash\n   ls -d .company-os\u002Fbackup\u002F*\u002F 2>\u002Fdev\u002Fnull\n   ```\n2. If no backups exist, inform the user that backups are created automatically during major upgrades or with the `--backup` flag\n3. If backups exist, present them to the user with timestamps and versions\n4. After user selects a backup, restore by copying the backup files over current template files. The backup holds exactly these paths, so restore all of them that are present:\n   - `os\u002Fagents\u002F`, `os\u002Fskills\u002F`, `os\u002Fplaybooks\u002F`, `os\u002Fhooks\u002F` (the source of truth)\n   - `.claude\u002Fagents\u002F`, `.claude\u002Fskills\u002F`, `.claude\u002Fhooks\u002F`\n   - `tools\u002F`\n   - `CLAUDE.md`\n\n   Copying over does not remove skills or agents that the newer version added. List the directories in `os\u002Fskills\u002F` and `os\u002Fagents\u002F` that are not in the backup, show them to the user, and delete them only if the user agrees (they may be the user's own).\n5. The other runtime adapters (`AGENTS.md`, `GEMINI.md`, `.cursor\u002F`, `.codex\u002F`) are not in the backup because they are generated from `os\u002F`. Rebuild only the adapters this project already has, so the rollback does not add runtimes the user never installed:\n   ```bash\n   [ -d .claude ] && bash tools\u002Fbuild\u002Fbuild.sh --runtime=claude\n   [ -f AGENTS.md ] && bash tools\u002Fbuild\u002Fbuild.sh --runtime=agents\n   [ -f GEMINI.md ] && bash tools\u002Fbuild\u002Fbuild.sh --runtime=gemini\n   { [ -d .cursor ] || [ -f .cursorrules ]; } && bash tools\u002Fbuild\u002Fbuild.sh --runtime=cursor\n   [ -d .codex ] && bash tools\u002Fbuild\u002Fbuild.sh --runtime=codex\n   ```\n   Do not run `build.sh` with no arguments: it builds every adapter.\n6. Update `.company-os\u002Fversion` to the backup's version (parse from the backup directory name)\n7. Rebuild the manifest so the next upgrade compares against the restored version. Re-install that same version, passing only the runtimes the project already has (for example `claude,cursor`):\n   ```bash\n   bash \"$tmp\u002Finstall.sh\" --force --version \u003Cbackup-version> --runtime \u003Cinstalled runtimes>\n   ```\n   (Use the verified download from the apply step. Or the user runs the `curl ... | bash -s -- --force --version \u003Cbackup-version> --runtime \u003C...>` form in their terminal.) This re-applies the same files, so content does not change; any `.user`\u002F`.new` pairs it reports for restored files are identical and can be deleted. Never run the installer with `--force` and no `--version` here: it downloads and applies the latest release, which undoes the rollback.\n\nWhat you will see:\n\n```text\nAvailable backups:\n  .company-os\u002Fbackup\u002F20261013-101500-v1.11.0\u002F   (version 1.11.0)\nWhich one should I restore?\n```\n\nAfter you choose, the skill restores the template files and reports the restored version. With no backups it says so and explains how backups are created. Your own files (`artifacts\u002F`, `tasks\u002F`, `company.config.yaml`) are never touched by a rollback.\n\n## Version File Locations\n\n| File | Purpose |\n|------|---------|\n| `.company-os\u002Fversion` | Template version — single source of truth |\n| `.company-os\u002Fmanifest` | SHA256 hashes of installed template files |\n| `.company-os\u002Fbackup\u002F` | Timestamped backups (auto for major upgrades) |\n| `.company-os\u002Fconflicts\u002F` | Conflicting file versions during upgrade |\n| `.company-os\u002Fdocs\u002FCHANGELOG.md` | Human-readable changelog (Keep a Changelog format) |\n\n## Reference\n\n- **ID**: S-ORG-10\n- **Category**: Orchestration\n- **Inputs**: `.company-os\u002Fversion`, `.company-os\u002Fmanifest`, remote release metadata\n- **Outputs**: upgraded system files, backup in `.company-os\u002Fbackup\u002F`\n- **Used by**: User (directly), Orchestrator Agent\n\n## Notes\n\n- The `curl` command is denied in `.claude\u002Fsettings.json`. For remote operations (check against latest, download updates), advise the user to run the command in their terminal directly.\n- For local operations (reading version files, listing backups), use Bash tool directly. Never run an `install.sh` found in the project root; use the verified download in a temporary folder.\n- Always show the user what will change before applying upgrades.\n- For major version upgrades, always recommend `--dry-run` first.\n","# Upgrade Company OS\n\nChecks for updates, previews changes, upgrades, or rolls back Company OS to a previous version.\n\n## When to Use\n\n- You want to know whether a newer Company OS release exists.\n- You want to see what an upgrade would change before it touches any file.\n- You want to apply an upgrade, or undo one that went wrong.\n\n## Subcommands\n\n### `\u002Fupgrade-company-os` or `\u002Fupgrade-company-os check`\n\nCheck if an update is available:\n\n1. Read `.company-os\u002Fversion` for the currently installed version\n2. If checking against remote, advise the user to run:\n   ```bash\n   curl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fvibbs\u002Fcompany-os\u002Fmain\u002Finstall.sh | bash -s -- --check\n   ```\n   To read the script first, download it to a temporary folder, review it, then run it:\n   ```bash\n   tmp=$(mktemp -d) && curl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fvibbs\u002Fcompany-os\u002Fmain\u002Finstall.sh -o \"$tmp\u002Finstall.sh\"\n   less \"$tmp\u002Finstall.sh\"\n   bash \"$tmp\u002Finstall.sh\" --check\n   ```\n   Inside an AI tool `less` is not interactive. Show the user only the header and version lines (`head -n 20 \"$tmp\u002Finstall.sh\"`) and the path, and ask them to review the whole file in their own terminal.\n3. If `.company-os\u002Fversion` doesn't exist, inform the user this is a pre-versioning install (1.11 or earlier). The installer backs up first. A run without `--force` only previews. With no manifest, the installer compares each file with every version Company OS has shipped (`.company-os\u002Fknown-hashes.txt` in the release): a file that matches one is an unedited copy and is updated. `--force` saves each file that matches no shipped version (the user's edits) as `.company-os\u002Fconflicts\u002F\u003Cpath>.user`, then replaces it\n\nWhat you will see:\n\n```text\n  Installed:  1.11.0\n  Available:  1.12.0 (minor)\n  Update available - 1.11.0 -> 1.12.0\n```\n\nOr, when nothing is newer: `Up to date - Company OS 1.11.0`.\n\n### `\u002Fupgrade-company-os preview`\n\nPreview what would change without applying:\n\n1. Get the installer. Never run an `install.sh` that sits in the project root: it may be the user's own script or a stale download. Download the current one to a temporary folder (`curl` is denied for the agent, so the user runs this in their terminal):\n   ```bash\n   tmp=$(mktemp -d) && curl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fvibbs\u002Fcompany-os\u002Fmain\u002Finstall.sh -o \"$tmp\u002Finstall.sh\"\n   ```\n2. Check that the file is the Company OS installer before running it: `head -n 5 \"$tmp\u002Finstall.sh\"` must contain `Company OS`. If it does not, stop and tell the user. Then run it in dry-run mode:\n   ```bash\n   bash \"$tmp\u002Finstall.sh\" --dry-run --force\n   ```\n   (Downloading to a file first lets the user read the script before it runs. Piping the script straight into `bash` works too, but nothing is reviewed.)\n3. Parse and display the output — highlight new files, updated files, conflicts, and migration notes\n\nWhat you will see:\n\n```text\n  Preview  .claude\u002Fsettings.json (would merge permissions)\n  Preview: Would create 2, add 5, merge 1, update 12, skip 40.\n  Warning: 1 file(s) modified by you AND changed in template.\n  These will be saved to .company-os\u002Fconflicts\u002F on upgrade.\n  Run without --dry-run to apply these changes.\n```\n\nNothing on disk changes during a preview.\n\n### `\u002Fupgrade-company-os apply`\n\nPerform the upgrade:\n\n1. Show current version from `.company-os\u002Fversion`\n2. For MAJOR upgrades: display migration notes from `.company-os\u002Fdocs\u002FCHANGELOG.md` and ask for confirmation before proceeding\n3. Run the upgrade:\n   ```bash\n   bash \"$tmp\u002Finstall.sh\" --force\n   ```\n   Use the same verified download as in preview. If the shell has no `$tmp`, download again to a new temporary folder and run the same header check. The user can also run these steps in their own terminal after reading the file with `less \"$tmp\u002Finstall.sh\"`.\n   To upgrade to a specific release instead of the latest, pin it with `--version`, for example `bash \"$tmp\u002Finstall.sh\" --force --version 1.12.0`. Pinning also works for a downgrade or when a team wants everyone on the same version.\n4. After upgrade, verify with:\n   ```bash\n   .\u002Ftools\u002Fregistry\u002Fhealth-check.sh\n   ```\n5. Display post-upgrade summary including new version from `.company-os\u002Fversion`\n6. If conflicts were detected (`.company-os\u002Fconflicts\u002F` exists and is non-empty), list the conflicted files and advise manual resolution\n\nWhat you will see:\n\n```text\n  Backup   Created at .company-os\u002Fbackup\u002F20261013-101500-v1.11.0\n  ...file-by-file results...\n  1 conflict(s) detected - your modified versions saved to .company-os\u002Fconflicts\u002F\n  Review the conflicts and merge manually.\n```\n\nEach conflict keeps the folder path of the original file, so same-named files never collide. A file the user edited that the template did not change is left alone and is not a conflict. A plain upgrade (no `--force`) keeps the user's version of a conflicting file and lists it; `--force` saves both and installs the template copy. A saved copy is never overwritten: a later one gets a timestamp suffix. Upgrades keep the adapters the project already has. For example, a changed `tools\u002Fqa\u002Frun.sh` is saved as `.company-os\u002Fconflicts\u002Ftools\u002Fqa\u002Frun.sh.user` (your version) and `run.sh.new` (the template version). Merge what you want to keep, then delete the conflict files. If you see `Up to date`, there was nothing to apply. The guides in `.company-os\u002Fdocs\u002F` are template-owned and always refreshed on upgrade; a guide the user edited is kept next to the new copy as `\u003Cname>.user` (for example `.company-os\u002Fdocs\u002FSETUP.md.user`).\n\n### `\u002Fupgrade-company-os rollback`\n\nRestore from a previous backup:\n\n1. List available backups:\n   ```bash\n   ls -d .company-os\u002Fbackup\u002F*\u002F 2>\u002Fdev\u002Fnull\n   ```\n2. If no backups exist, inform the user that backups are created automatically during major upgrades or with the `--backup` flag\n3. If backups exist, present them to the user with timestamps and versions\n4. After user selects a backup, restore by copying the backup files over current template files. The backup holds exactly these paths, so restore all of them that are present:\n   - `os\u002Fagents\u002F`, `os\u002Fskills\u002F`, `os\u002Fplaybooks\u002F`, `os\u002Fhooks\u002F` (the source of truth)\n   - `.claude\u002Fagents\u002F`, `.claude\u002Fskills\u002F`, `.claude\u002Fhooks\u002F`\n   - `tools\u002F`\n   - `CLAUDE.md`\n\n   Copying over does not remove skills or agents that the newer version added. List the directories in `os\u002Fskills\u002F` and `os\u002Fagents\u002F` that are not in the backup, show them to the user, and delete them only if the user agrees (they may be the user's own).\n5. The other runtime adapters (`AGENTS.md`, `GEMINI.md`, `.cursor\u002F`, `.codex\u002F`) are not in the backup because they are generated from `os\u002F`. Rebuild only the adapters this project already has, so the rollback does not add runtimes the user never installed:\n   ```bash\n   [ -d .claude ] && bash tools\u002Fbuild\u002Fbuild.sh --runtime=claude\n   [ -f AGENTS.md ] && bash tools\u002Fbuild\u002Fbuild.sh --runtime=agents\n   [ -f GEMINI.md ] && bash tools\u002Fbuild\u002Fbuild.sh --runtime=gemini\n   { [ -d .cursor ] || [ -f .cursorrules ]; } && bash tools\u002Fbuild\u002Fbuild.sh --runtime=cursor\n   [ -d .codex ] && bash tools\u002Fbuild\u002Fbuild.sh --runtime=codex\n   ```\n   Do not run `build.sh` with no arguments: it builds every adapter.\n6. Update `.company-os\u002Fversion` to the backup's version (parse from the backup directory name)\n7. Rebuild the manifest so the next upgrade compares against the restored version. Re-install that same version, passing only the runtimes the project already has (for example `claude,cursor`):\n   ```bash\n   bash \"$tmp\u002Finstall.sh\" --force --version \u003Cbackup-version> --runtime \u003Cinstalled runtimes>\n   ```\n   (Use the verified download from the apply step. Or the user runs the `curl ... | bash -s -- --force --version \u003Cbackup-version> --runtime \u003C...>` form in their terminal.) This re-applies the same files, so content does not change; any `.user`\u002F`.new` pairs it reports for restored files are identical and can be deleted. Never run the installer with `--force` and no `--version` here: it downloads and applies the latest release, which undoes the rollback.\n\nWhat you will see:\n\n```text\nAvailable backups:\n  .company-os\u002Fbackup\u002F20261013-101500-v1.11.0\u002F   (version 1.11.0)\nWhich one should I restore?\n```\n\nAfter you choose, the skill restores the template files and reports the restored version. With no backups it says so and explains how backups are created. Your own files (`artifacts\u002F`, `tasks\u002F`, `company.config.yaml`) are never touched by a rollback.\n\n## Version File Locations\n\n| File | Purpose |\n|------|---------|\n| `.company-os\u002Fversion` | Template version — single source of truth |\n| `.company-os\u002Fmanifest` | SHA256 hashes of installed template files |\n| `.company-os\u002Fbackup\u002F` | Timestamped backups (auto for major upgrades) |\n| `.company-os\u002Fconflicts\u002F` | Conflicting file versions during upgrade |\n| `.company-os\u002Fdocs\u002FCHANGELOG.md` | Human-readable changelog (Keep a Changelog format) |\n\n## Reference\n\n- **ID**: S-ORG-10\n- **Category**: Orchestration\n- **Inputs**: `.company-os\u002Fversion`, `.company-os\u002Fmanifest`, remote release metadata\n- **Outputs**: upgraded system files, backup in `.company-os\u002Fbackup\u002F`\n- **Used by**: User (directly), Orchestrator Agent\n\n## Notes\n\n- The `curl` command is denied in `.claude\u002Fsettings.json`. For remote operations (check against latest, download updates), advise the user to run the command in their terminal directly.\n- For local operations (reading version files, listing backups), use Bash tool directly. Never run an `install.sh` found in the project root; use the verified download in a temporary folder.\n- Always show the user what will change before applying upgrades.\n- For major version upgrades, always recommend `--dry-run` first.\n",{"name":5,"runtimes":33,"description":7},{"claude":34},{"argument-hint":35,"user-invocable":36},"[check | preview | apply | rollback]",true,"main","e842fb6d0e04360c47db78bc2e2e2987314d64d4","os\u002Fskills\u002Fupgrade-company-os",2,"https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os","https:\u002F\u002Fgithub.com\u002Fvibbs","Principal Engineer · Applied AI · building ArcAI @ GrowthArc","2026-10-21 02:08:08",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":36},[47,50,53],{"tool":48,"command":49},"npx","npx skills add vibbs\u002Fcompany-os --skill upgrade-company-os",{"tool":51,"command":52},"bunx","bunx skills add vibbs\u002Fcompany-os --skill upgrade-company-os",{"tool":54,"command":55},"pnpm","pnpm dlx skills add vibbs\u002Fcompany-os --skill upgrade-company-os","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fupgrade-company-os\u002FSKILL.md",[58,64,68],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"bmad-skill-manifest.yaml","REFERENCE","参考文档",12,"https:\u002F\u002Fgithub.com\u002Fcodeasice\u002Fagentcore-presentation\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fgds-dev-story\u002Fbmad-skill-manifest.yaml",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"checklist.md",4389,"https:\u002F\u002Fgithub.com\u002Fcodeasice\u002Fagentcore-presentation\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fgds-dev-story\u002Fchecklist.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"workflow.md",23385,"https:\u002F\u002Fgithub.com\u002Fcodeasice\u002Fagentcore-presentation\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fgds-dev-story\u002Fworkflow.md",[73,82,90,100,116,134],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":28},"01M6CTHBW1E64ECYGD105N4S5E","typo-field","Fixture skill with a misspelled top-level field.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Ftypo-field\u002FSKILL.md",[],[80,81],"typo field","fixture skill",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":28},"01M6CTHABTV8FKVDHFMMKPAV51","spaced-comments","Fixture skill with comments and spaces after block keys.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fspaced-comments\u002FSKILL.md",[],[89,81],"spaced comments",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":28},"01M6CTH8MHC14KB65ZDHYBJW1N","crlf-comments","Fixture skill with Windows line endings.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fcrlf-comments\u002FSKILL.md",[],[97,98,99,81],"crlf comments","CRLF","windows",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":28},"01M6CTH6TBKTDP9G8QB1Z2K0TY","claude-fields","Fixture skill using top-level fields Claude Code documents.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fclaude-fields\u002FSKILL.md",[],[107,108,109,110,111,112,81,113,114,115],"claude fields","explore","documents","src","grep","read","Bash","code","testing",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":127,"publishedAt":28},"01M6CTH46BGKXH80RWS876Y2CW","workflow-router","Maps an objective to the artifacts, stages and agents it needs. Use when deciding what happens next or which agents to involve.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fworkflow-router\u002FSKILL.md",[122],{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[128,129,130,131,132,24,133],"workflow","router","workflow router","next","maps","artifacts",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":28},"01M6CTH27653SRVP2FMEQN3J5B","weekly-review","Summarizes your week: what shipped, AI spend, support themes, security health and next priorities. Use at the end of each week.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[141,142,143,131,24,144,145,146,147],"weekly review","review","priorities","health","save","support","security"]