[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AV30550XWK8QH4P39VRME2":3,"skill-same:01M7AV30550XWK8QH4P39VRME2":52},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7AV30550XWK8QH4P39VRME2","specrew-update",null,"Refresh Specrew-managed assets and supported platform baselines in the current project.","alonf\u002FKeyContextAI","alonf","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F554150?v=4","01M7ATEPSCNKG13BVTKA74VG59","Alon Fliess","01M7ATEPSZ4YMBM9W25SKM3GES",0,"MIT","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fspecrew-update\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: specrew-update\ndescription: Refresh Specrew-managed assets and supported platform baselines in the current project.\n---\n\n# specrew-update\n\n**Type**: Operational Skill\n**Schema**: v1\n**Status**: Active\n**Namespace**: `\u002Fspecrew`\n**Canonical command**: `\u002Fspecrew-update`\n\n## Purpose\n\nRefresh Specrew-managed assets and supported platform baselines (Spec Kit, Squad) in the current project.\n\n## When to Use\n\n- When a contributor wants to update Specrew assets in an existing project.\n- When refreshing the slash-command surface after a new Specrew release.\n- When synchronizing Spec Kit or Squad extensions to a newer version.\n- Invoke this skill when the user says: \"Update Specrew\", \"Refresh Specrew assets\", \"Update Spec Kit\", \"Update Squad\".\n\n## Boundary Safety\n\nThis skill updates **distribution-managed assets only**. It does **not** authorize or imply approval to advance any lifecycle boundary. The scope of updates is bounded by the documented argument whitelist — no undocumented expansion occurs.\n\n## Coexistence Contract\n\nThis skill is additive. Refreshing Specrew assets does not remove or shadow `\u002Fspeckit.*` command surfaces.\n\n## Invocation\n\n```text\n\u002Fspecrew-update [--project-path \u003Cpath>] [--info] [--all]\n                 [--specrew] [--squad] [--spec-kit] [--skip-update-check]\n                 [--upstream-latest]\n```\n\nBacked by: `specrew update` \u002F `scripts\u002Fspecrew-update.ps1`\n\n## Inputs\n\n| Input | Type | Required | Description |\n| ----- | ---- | -------- | ----------- |\n| `--project-path` | string | No | Target Specrew project path (defaults to current directory) |\n| `--info` | flag | No | Show version and update information without performing updates |\n| `--all` | flag | No | Update all managed components (Specrew, Spec Kit, Squad) |\n| `--specrew` | flag | No | Update Specrew-managed assets only |\n| `--squad` | flag | No | Update Squad-managed assets only |\n| `--spec-kit` | flag | No | Update Spec Kit extension only |\n\u003C!-- specrew-self-ok: the specrew-update skill teaches updating Specrew itself - the tool's registry is a true consumer fact -->\n| `--skip-update-check` | flag | No | Skip the PSGallery version-available check |\n| `--upstream-latest` | flag | No | Target upstream-latest versions instead of Specrew-validated max_tested (use with care; see Outputs) |\n\n## Outputs\n\n- Update report showing which assets were refreshed, skipped, or newly provisioned.\n- `--info` table shows Current \u002F **LatestSupported** (the highest version Specrew has validated against) \u002F **UpstreamLatest** (advisory) \u002F Status \u002F Source for Specrew, Spec Kit, and Squad. Four-state Status: `current`, `update-available-supported`, `ahead-of-supported` (current is beyond Specrew-validated max_tested), `behind-supported` (current is below the floor).\n- Advisory line surfaces when upstream-latest exceeds LatestSupported, explaining \"Specrew has validated only through X.Y.Z\" so the user does not silently adopt untested upstream versions.\n- Default upgrade target is `LatestSupported`. The `--upstream-latest` flag opts into the historical behavior (upgrade to upstream-latest), at the user's own risk.\n- Slash-command surface status after the update.\n\u003C!-- specrew-self-ok: the specrew-update skill teaches updating Specrew itself - the tool's registry is a true consumer fact -->\n- Version availability notice if a newer Specrew version is available on PSGallery.\n\n## Argument Whitelist\n\nOnly the arguments listed above are accepted in v1. Unknown or unsupported arguments are rejected immediately with explicit help guidance.\n\n## Failure Guidance\n\n| Failure mode | Behavior |\n| --- | --- |\n| Unsupported argument | Rejected immediately with command-specific help guidance |\n| Missing project setup | Stop with `specrew init` remediation |\n| Outdated compatibility baseline | Stop with upgrade\u002Fremediation guidance |\n\n## See Also\n\n- `\u002Fspecrew-version` — inspect the current version and compatibility state before updating\n- `\u002Fspecrew-help` — catalog fallback and full command list\n","# specrew-update\n\n**Type**: Operational Skill\n**Schema**: v1\n**Status**: Active\n**Namespace**: `\u002Fspecrew`\n**Canonical command**: `\u002Fspecrew-update`\n\n## Purpose\n\nRefresh Specrew-managed assets and supported platform baselines (Spec Kit, Squad) in the current project.\n\n## When to Use\n\n- When a contributor wants to update Specrew assets in an existing project.\n- When refreshing the slash-command surface after a new Specrew release.\n- When synchronizing Spec Kit or Squad extensions to a newer version.\n- Invoke this skill when the user says: \"Update Specrew\", \"Refresh Specrew assets\", \"Update Spec Kit\", \"Update Squad\".\n\n## Boundary Safety\n\nThis skill updates **distribution-managed assets only**. It does **not** authorize or imply approval to advance any lifecycle boundary. The scope of updates is bounded by the documented argument whitelist — no undocumented expansion occurs.\n\n## Coexistence Contract\n\nThis skill is additive. Refreshing Specrew assets does not remove or shadow `\u002Fspeckit.*` command surfaces.\n\n## Invocation\n\n```text\n\u002Fspecrew-update [--project-path \u003Cpath>] [--info] [--all]\n                 [--specrew] [--squad] [--spec-kit] [--skip-update-check]\n                 [--upstream-latest]\n```\n\nBacked by: `specrew update` \u002F `scripts\u002Fspecrew-update.ps1`\n\n## Inputs\n\n| Input | Type | Required | Description |\n| ----- | ---- | -------- | ----------- |\n| `--project-path` | string | No | Target Specrew project path (defaults to current directory) |\n| `--info` | flag | No | Show version and update information without performing updates |\n| `--all` | flag | No | Update all managed components (Specrew, Spec Kit, Squad) |\n| `--specrew` | flag | No | Update Specrew-managed assets only |\n| `--squad` | flag | No | Update Squad-managed assets only |\n| `--spec-kit` | flag | No | Update Spec Kit extension only |\n\u003C!-- specrew-self-ok: the specrew-update skill teaches updating Specrew itself - the tool's registry is a true consumer fact -->\n| `--skip-update-check` | flag | No | Skip the PSGallery version-available check |\n| `--upstream-latest` | flag | No | Target upstream-latest versions instead of Specrew-validated max_tested (use with care; see Outputs) |\n\n## Outputs\n\n- Update report showing which assets were refreshed, skipped, or newly provisioned.\n- `--info` table shows Current \u002F **LatestSupported** (the highest version Specrew has validated against) \u002F **UpstreamLatest** (advisory) \u002F Status \u002F Source for Specrew, Spec Kit, and Squad. Four-state Status: `current`, `update-available-supported`, `ahead-of-supported` (current is beyond Specrew-validated max_tested), `behind-supported` (current is below the floor).\n- Advisory line surfaces when upstream-latest exceeds LatestSupported, explaining \"Specrew has validated only through X.Y.Z\" so the user does not silently adopt untested upstream versions.\n- Default upgrade target is `LatestSupported`. The `--upstream-latest` flag opts into the historical behavior (upgrade to upstream-latest), at the user's own risk.\n- Slash-command surface status after the update.\n\u003C!-- specrew-self-ok: the specrew-update skill teaches updating Specrew itself - the tool's registry is a true consumer fact -->\n- Version availability notice if a newer Specrew version is available on PSGallery.\n\n## Argument Whitelist\n\nOnly the arguments listed above are accepted in v1. Unknown or unsupported arguments are rejected immediately with explicit help guidance.\n\n## Failure Guidance\n\n| Failure mode | Behavior |\n| --- | --- |\n| Unsupported argument | Rejected immediately with command-specific help guidance |\n| Missing project setup | Stop with `specrew init` remediation |\n| Outdated compatibility baseline | Stop with upgrade\u002Fremediation guidance |\n\n## See Also\n\n- `\u002Fspecrew-version` — inspect the current version and compatibility state before updating\n- `\u002Fspecrew-help` — catalog fallback and full command list\n",{"name":5,"description":7},"main","176da577bfd98859f793bdd1312690c6c3940c67",".github\u002Fskills\u002Fspecrew-update","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI","https:\u002F\u002Fgithub.com\u002Falonf","http:\u002F\u002Falonfliess.me","CTO & Founder of Zionet.\r\nMicrosoft Regional Director and Foundry MVP.\r\n","2026-08-28 05:21:35",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add alonf\u002FKeyContextAI --skill specrew-update",{"tool":38,"command":39},"bunx","bunx skills add alonf\u002FKeyContextAI --skill specrew-update",{"tool":41,"command":42},"pnpm","pnpm dlx skills add alonf\u002FKeyContextAI --skill specrew-update","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fspecrew-update\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},".specrew-managed","OTHER","其他",71,"https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fspecrew-update\u002F.specrew-managed",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7AVHRWWXA0BQ5PXNA8FG30W","windows-compatibility","Cross-platform path handling and command patterns","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fwindows-compatibility\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7AVHABPRYXYM3GWJY1RW92A","versioning-policy","Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fversioning-policy\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7AVH4KNP3TCVQDRVS70VP19","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7AVH18JDSA55Z7KK2GH6X49","test-discipline","Update tests when changing APIs — no exceptions","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftest-discipline\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7AVGVGWYD7NBNXAV4PAZJ92","squad","Squad's command catalog and interactive menu. Invoke via \u002Fsquad (slash command) or natural language (\"squad commands\", \"what can squad do\", \"show me squad options\"). Presents categorized operations (Install & Upgrade, Team Management, Issues & PRs, Plugins & Skills, Model & Cost, Sessions & State) as an interactive picker. Routes to the right squad CLI command or the Squad coordinator agent.","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fsquad\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"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":19},"01M7AVGPSFT1WHW3PK35DHS5XK","squad-version-check","Internals of how @bradygaster\u002Fsquad-cli stamps its version, how `squad upgrade` works (what it preserves vs overwrites), and how to probe the npm registry for the latest version from a coordinator prompt.","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fsquad-version-check\u002FSKILL.md",[],[]]