[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6X1AA7NXDATS70H4K801SRF":3,"skill-same:01M6X1AA7NXDATS70H4K801SRF":79},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6X1AA7NXDATS70H4K801SRF","gh-auth-isolation",null,"Safely manage multiple GitHub identities (EMU + personal) in agent workflows","github\u002Fsquad","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6X0MZ6B0WYMMDPK3Q61KER6",3391,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fpackages\u002Fsquad-cli\u002Ftemplates\u002Fskills\u002Fgh-auth-isolation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,9,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"isolation","gh","gh auth isolation","auth","multi","with","sessions","manage","for","usage","personal","security","cli","github cli","across","when","workflows","authentication","resources","2026-11-10 10:12:30",false,"---\r\nname: \"gh-auth-isolation\"\r\ndescription: \"Safely manage multiple GitHub identities (EMU + personal) in agent workflows\"\r\ndomain: \"security, github-integration, authentication, multi-account\"\r\nconfidence: \"high\"\r\nsource: \"earned (production usage across 50+ sessions with EMU corp + personal GitHub accounts)\"\r\ntools:\r\n  - name: \"gh\"\r\n    description: \"GitHub CLI for authenticated operations\"\r\n    when: \"When accessing GitHub resources requiring authentication\"\r\n---\r\n\r\n## Context\r\n\r\nMany developers use GitHub through an Enterprise Managed User (EMU) account at work while maintaining a personal GitHub account for open-source contributions. AI agents spawned by Squad inherit the shell's default `gh` authentication — which is usually the EMU account. This causes failures when agents try to push to personal repos, create PRs on forks, or interact with resources outside the enterprise org.\r\n\r\nThis skill teaches agents how to detect the active identity, switch contexts safely, and avoid mixing credentials across operations.\r\n\r\n## Patterns\r\n\r\n### Detect Current Identity\r\n\r\nBefore any GitHub operation, check which account is active:\r\n\r\n```bash\r\ngh auth status\r\n```\r\n\r\nLook for:\r\n- `Logged in to github.com as USERNAME` — the active account\r\n- `Token scopes: ...` — what permissions are available\r\n- Multiple accounts will show separate entries\r\n\r\n### Extract a Specific Account's Token\r\n\r\nWhen you need to operate as a specific user (not the default):\r\n\r\n```bash\r\n# Get the personal account token (by username)\r\ngh auth token --user personaluser\r\n\r\n# Get the EMU account token\r\ngh auth token --user corpalias_enterprise\r\n```\r\n\r\n**Use case:** Push to a personal fork while the default `gh` auth is the EMU account.\r\n\r\n### Push to Personal Repos from EMU Shell\r\n\r\nThe most common scenario: your shell defaults to the EMU account, but you need to push to a personal GitHub repo.\r\n\r\n```bash\r\n# Push as the personal account for this one command: gh's credential helper hands git the\r\n# token from GH_TOKEN, so it never appears in a URL, a remote or the command line\r\nGH_TOKEN=\"$(gh auth token --user personaluser)\" \\\r\n  git -c credential.helper= -c 'credential.helper=!gh auth git-credential' \\\r\n  push https:\u002F\u002Fgithub.com\u002Fpersonaluser\u002Frepo.git branch-name\r\n```\r\n\r\n**Why this works:** `gh auth token --user` reads from `gh`'s credential store without switching the active account. The token lives only in that one command's environment: `credential.helper=` clears the stored (EMU) helper for this command, and `gh auth git-credential` answers git's credential request with `GH_TOKEN`. Never put a token in a git URL: it shows up in shell history, process listings, tool logs and `.git\u002Fconfig`.\r\n\r\n### Create PRs on Personal Forks\r\n\r\nWhen the default `gh` context is EMU but you need to create a PR from a personal fork:\r\n\r\n```bash\r\n# Option 1: Use --repo flag (works if token has access)\r\ngh pr create --repo upstream\u002Frepo --head personaluser:branch --title \"...\" --body \"...\"\r\n\r\n# Option 2: Temporarily set GH_TOKEN for one command\r\n$env:GH_TOKEN = $(gh auth token --user personaluser)\r\ngh pr create --repo upstream\u002Frepo --head personaluser:branch --title \"...\"\r\nRemove-Item Env:\\GH_TOKEN\r\n```\r\n\r\n### Config Directory Isolation (Advanced)\r\n\r\nFor complete isolation between accounts, use separate `gh` config directories:\r\n\r\n```bash\r\n# Personal account operations\r\n$env:GH_CONFIG_DIR = \"$HOME\u002F.config\u002Fgh-public\"\r\ngh auth login  # Login with personal account (one-time setup)\r\ngh repo clone personaluser\u002Frepo\r\n\r\n# EMU account operations (default)\r\nRemove-Item Env:\\GH_CONFIG_DIR\r\ngh auth status  # Back to EMU account\r\n```\r\n\r\n**Setup (one-time):**\r\n```bash\r\n# Create isolated config for personal account\r\nmkdir ~\u002F.config\u002Fgh-public\r\n$env:GH_CONFIG_DIR = \"$HOME\u002F.config\u002Fgh-public\"\r\ngh auth login --web --git-protocol https\r\n```\r\n\r\n### Shell Aliases for Quick Switching\r\n\r\nAdd to your shell profile for convenience:\r\n\r\n```powershell\r\n# PowerShell profile\r\nfunction ghp { $env:GH_CONFIG_DIR = \"$HOME\u002F.config\u002Fgh-public\"; gh @args; Remove-Item Env:\\GH_CONFIG_DIR }\r\nfunction ghe { gh @args }  # Default EMU\r\n\r\n# Usage:\r\n# ghp repo clone personaluser\u002Frepo   # Uses personal account\r\n# ghe issue list                       # Uses EMU account\r\n```\r\n\r\n```bash\r\n# Bash\u002FZsh profile\r\nalias ghp='GH_CONFIG_DIR=~\u002F.config\u002Fgh-public gh'\r\nalias ghe='gh'\r\n\r\n# Usage:\r\n# ghp repo clone personaluser\u002Frepo\r\n# ghe issue list\r\n```\r\n\r\n## Examples\r\n\r\n### ✓ Correct: Agent pushes blog post to personal GitHub Pages\r\n\r\n```powershell\r\n# Agent needs to push to personaluser.github.io (personal repo)\r\n# Default gh auth is corpalias_enterprise (EMU)\r\n\r\n$env:GH_TOKEN = gh auth token --user personaluser\r\ngit -c credential.helper= -c 'credential.helper=!gh auth git-credential' push origin main\r\nRemove-Item Env:GH_TOKEN  # the token never touches the remote URL\r\n```\r\n\r\n### ✓ Correct: Agent creates a PR from personal fork to upstream\r\n\r\n```powershell\r\n# Fork: personaluser\u002Fsquad, Upstream: github\u002Fsquad\r\n# Agent is on branch contrib\u002Ffix-docs in the fork clone\r\n\r\ngit push origin contrib\u002Ffix-docs  # Pushes to fork (may need token auth)\r\n\r\n# Create PR targeting upstream\r\ngh pr create --repo github\u002Fsquad --head personaluser:contrib\u002Ffix-docs `\r\n  --title \"docs: fix installation guide\" `\r\n  --body \"Fixes #123\"\r\n```\r\n\r\n### ✗ Incorrect: Blindly pushing with wrong account\r\n\r\n```bash\r\n# BAD: Agent assumes default gh auth works for personal repos\r\ngit push origin main\r\n# ERROR: Permission denied — EMU account has no access to personal repo\r\n\r\n# BAD: Hardcoding tokens in scripts\r\ngit push https:\u002F\u002Fpersonaluser:ghp_xxxxxxxxxxxx@github.com\u002Fpersonaluser\u002Frepo.git main\r\n# SECURITY RISK: Token exposed in command history and process list\r\n```\r\n\r\n### ✓ Correct: Check before you push\r\n\r\n```bash\r\n# Always verify which account has access before operations\r\ngh auth status\r\n# If wrong account, hand git the personal token for this one push:\r\nGH_TOKEN=\"$(gh auth token --user personaluser)\" \\\r\n  git -c credential.helper= -c 'credential.helper=!gh auth git-credential' \\\r\n  push https:\u002F\u002Fgithub.com\u002Fpersonaluser\u002Frepo.git main\r\n```\r\n\r\n## Anti-Patterns\r\n\r\n- ❌ **Hardcoding tokens** in scripts, environment variables, or committed files. Use `gh auth token --user` to extract at runtime.\r\n- ❌ **Assuming the default `gh` auth works** for all repos. EMU accounts can't access personal repos and vice versa.\r\n- ❌ **Switching `gh auth login`** globally mid-session. This changes the default for ALL processes and can break parallel agents.\r\n- ❌ **Storing personal tokens in `.env`** or `.squad\u002F` files. These get committed by Scribe. Use `gh`'s credential store.\r\n- ❌ **Ignoring token cleanup** after inline HTTPS pushes. Always reset the remote URL to avoid persisting tokens.\r\n- ❌ **Using `gh auth switch`** in multi-agent sessions. One agent switching affects all others sharing the shell.\r\n- ❌ **Mixing EMU and personal operations** in the same git clone. Use separate clones or explicit remote URLs per operation.\r\n","## Context\r\n\r\nMany developers use GitHub through an Enterprise Managed User (EMU) account at work while maintaining a personal GitHub account for open-source contributions. AI agents spawned by Squad inherit the shell's default `gh` authentication — which is usually the EMU account. This causes failures when agents try to push to personal repos, create PRs on forks, or interact with resources outside the enterprise org.\r\n\r\nThis skill teaches agents how to detect the active identity, switch contexts safely, and avoid mixing credentials across operations.\r\n\r\n## Patterns\r\n\r\n### Detect Current Identity\r\n\r\nBefore any GitHub operation, check which account is active:\r\n\r\n```bash\r\ngh auth status\r\n```\r\n\r\nLook for:\r\n- `Logged in to github.com as USERNAME` — the active account\r\n- `Token scopes: ...` — what permissions are available\r\n- Multiple accounts will show separate entries\r\n\r\n### Extract a Specific Account's Token\r\n\r\nWhen you need to operate as a specific user (not the default):\r\n\r\n```bash\r\n# Get the personal account token (by username)\r\ngh auth token --user personaluser\r\n\r\n# Get the EMU account token\r\ngh auth token --user corpalias_enterprise\r\n```\r\n\r\n**Use case:** Push to a personal fork while the default `gh` auth is the EMU account.\r\n\r\n### Push to Personal Repos from EMU Shell\r\n\r\nThe most common scenario: your shell defaults to the EMU account, but you need to push to a personal GitHub repo.\r\n\r\n```bash\r\n# Push as the personal account for this one command: gh's credential helper hands git the\r\n# token from GH_TOKEN, so it never appears in a URL, a remote or the command line\r\nGH_TOKEN=\"$(gh auth token --user personaluser)\" \\\r\n  git -c credential.helper= -c 'credential.helper=!gh auth git-credential' \\\r\n  push https:\u002F\u002Fgithub.com\u002Fpersonaluser\u002Frepo.git branch-name\r\n```\r\n\r\n**Why this works:** `gh auth token --user` reads from `gh`'s credential store without switching the active account. The token lives only in that one command's environment: `credential.helper=` clears the stored (EMU) helper for this command, and `gh auth git-credential` answers git's credential request with `GH_TOKEN`. Never put a token in a git URL: it shows up in shell history, process listings, tool logs and `.git\u002Fconfig`.\r\n\r\n### Create PRs on Personal Forks\r\n\r\nWhen the default `gh` context is EMU but you need to create a PR from a personal fork:\r\n\r\n```bash\r\n# Option 1: Use --repo flag (works if token has access)\r\ngh pr create --repo upstream\u002Frepo --head personaluser:branch --title \"...\" --body \"...\"\r\n\r\n# Option 2: Temporarily set GH_TOKEN for one command\r\n$env:GH_TOKEN = $(gh auth token --user personaluser)\r\ngh pr create --repo upstream\u002Frepo --head personaluser:branch --title \"...\"\r\nRemove-Item Env:\\GH_TOKEN\r\n```\r\n\r\n### Config Directory Isolation (Advanced)\r\n\r\nFor complete isolation between accounts, use separate `gh` config directories:\r\n\r\n```bash\r\n# Personal account operations\r\n$env:GH_CONFIG_DIR = \"$HOME\u002F.config\u002Fgh-public\"\r\ngh auth login  # Login with personal account (one-time setup)\r\ngh repo clone personaluser\u002Frepo\r\n\r\n# EMU account operations (default)\r\nRemove-Item Env:\\GH_CONFIG_DIR\r\ngh auth status  # Back to EMU account\r\n```\r\n\r\n**Setup (one-time):**\r\n```bash\r\n# Create isolated config for personal account\r\nmkdir ~\u002F.config\u002Fgh-public\r\n$env:GH_CONFIG_DIR = \"$HOME\u002F.config\u002Fgh-public\"\r\ngh auth login --web --git-protocol https\r\n```\r\n\r\n### Shell Aliases for Quick Switching\r\n\r\nAdd to your shell profile for convenience:\r\n\r\n```powershell\r\n# PowerShell profile\r\nfunction ghp { $env:GH_CONFIG_DIR = \"$HOME\u002F.config\u002Fgh-public\"; gh @args; Remove-Item Env:\\GH_CONFIG_DIR }\r\nfunction ghe { gh @args }  # Default EMU\r\n\r\n# Usage:\r\n# ghp repo clone personaluser\u002Frepo   # Uses personal account\r\n# ghe issue list                       # Uses EMU account\r\n```\r\n\r\n```bash\r\n# Bash\u002FZsh profile\r\nalias ghp='GH_CONFIG_DIR=~\u002F.config\u002Fgh-public gh'\r\nalias ghe='gh'\r\n\r\n# Usage:\r\n# ghp repo clone personaluser\u002Frepo\r\n# ghe issue list\r\n```\r\n\r\n## Examples\r\n\r\n### ✓ Correct: Agent pushes blog post to personal GitHub Pages\r\n\r\n```powershell\r\n# Agent needs to push to personaluser.github.io (personal repo)\r\n# Default gh auth is corpalias_enterprise (EMU)\r\n\r\n$env:GH_TOKEN = gh auth token --user personaluser\r\ngit -c credential.helper= -c 'credential.helper=!gh auth git-credential' push origin main\r\nRemove-Item Env:GH_TOKEN  # the token never touches the remote URL\r\n```\r\n\r\n### ✓ Correct: Agent creates a PR from personal fork to upstream\r\n\r\n```powershell\r\n# Fork: personaluser\u002Fsquad, Upstream: github\u002Fsquad\r\n# Agent is on branch contrib\u002Ffix-docs in the fork clone\r\n\r\ngit push origin contrib\u002Ffix-docs  # Pushes to fork (may need token auth)\r\n\r\n# Create PR targeting upstream\r\ngh pr create --repo github\u002Fsquad --head personaluser:contrib\u002Ffix-docs `\r\n  --title \"docs: fix installation guide\" `\r\n  --body \"Fixes #123\"\r\n```\r\n\r\n### ✗ Incorrect: Blindly pushing with wrong account\r\n\r\n```bash\r\n# BAD: Agent assumes default gh auth works for personal repos\r\ngit push origin main\r\n# ERROR: Permission denied — EMU account has no access to personal repo\r\n\r\n# BAD: Hardcoding tokens in scripts\r\ngit push https:\u002F\u002Fpersonaluser:ghp_xxxxxxxxxxxx@github.com\u002Fpersonaluser\u002Frepo.git main\r\n# SECURITY RISK: Token exposed in command history and process list\r\n```\r\n\r\n### ✓ Correct: Check before you push\r\n\r\n```bash\r\n# Always verify which account has access before operations\r\ngh auth status\r\n# If wrong account, hand git the personal token for this one push:\r\nGH_TOKEN=\"$(gh auth token --user personaluser)\" \\\r\n  git -c credential.helper= -c 'credential.helper=!gh auth git-credential' \\\r\n  push https:\u002F\u002Fgithub.com\u002Fpersonaluser\u002Frepo.git main\r\n```\r\n\r\n## Anti-Patterns\r\n\r\n- ❌ **Hardcoding tokens** in scripts, environment variables, or committed files. Use `gh auth token --user` to extract at runtime.\r\n- ❌ **Assuming the default `gh` auth works** for all repos. EMU accounts can't access personal repos and vice versa.\r\n- ❌ **Switching `gh auth login`** globally mid-session. This changes the default for ALL processes and can break parallel agents.\r\n- ❌ **Storing personal tokens in `.env`** or `.squad\u002F` files. These get committed by Scribe. Use `gh`'s credential store.\r\n- ❌ **Ignoring token cleanup** after inline HTTPS pushes. Always reset the remote URL to avoid persisting tokens.\r\n- ❌ **Using `gh auth switch`** in multi-agent sessions. One agent switching affects all others sharing the shell.\r\n- ❌ **Mixing EMU and personal operations** in the same git clone. Use separate clones or explicit remote URLs per operation.\r\n",{"name":5,"tools":48,"domain":52,"source":53,"confidence":54,"description":7},[49],{"name":25,"when":50,"description":51},"When accessing GitHub resources requiring authentication","GitHub CLI for authenticated operations","security, github-integration, authentication, multi-account","earned (production usage across 50+ sessions with EMU corp + personal GitHub accounts)","high","dev","699589d781f9d9dbb6d8b8c6214c93dc7b828dbd","packages\u002Fsquad-cli\u002Ftemplates\u002Fskills\u002Fgh-auth-isolation",520,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad","https:\u002F\u002Fgithub.github.io\u002Fsquad\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-15 02:13:59",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add github\u002Fsquad --skill gh-auth-isolation",{"tool":71,"command":72},"bunx","bunx skills add github\u002Fsquad --skill gh-auth-isolation",{"tool":74,"command":75},"pnpm","pnpm dlx skills add github\u002Fsquad --skill gh-auth-isolation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fpackages\u002Fsquad-cli\u002Ftemplates\u002Fskills\u002Fgh-auth-isolation\u002FSKILL.md",true,[],[80,88,95,102,109,116],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":87},"01M76752CVNE7K6NWD59CRAYNJ","windows-compatibility","Cross-platform path handling and command patterns","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Fwindows-compatibility\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"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":87},"01M767508W8A4G83NX1FKEW5VN","versioning-policy","SemVer rules for Squad's stable, preview, insider, and local package versions","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Fversioning-policy\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":87},"01M7674X5JJKNJ74B3SS8PGXG2","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":87},"01M7674V3S9H03A76H75M1KSAF","test-discipline","Design assertions that prove the actual contract and fail on realistic regressions","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Ftest-discipline\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":87},"01M7674QB8CA61RNDX2Z0NAK71","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\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Fsquad\u002FSKILL.md",[],[],{"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":122,"publishedAt":87},"01M7674KTQ632N30HQB1TP7TXH","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\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Fsquad-version-check\u002FSKILL.md",[],[]]