[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BBN3M4EP7BRQ1CP954BNM":3,"skill-same:01M69BBN3M4EP7BRQ1CP954BNM":146},{"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":24,"linkOnly":25,"markdownContent":26,"markdownBody":27,"frontMatter":28,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M69BBN3M4EP7BRQ1CP954BNM","cross-squad",null,"Coordinating work across multiple Squad instances — discovery, delegation, and disambiguation when the user says 'squad' (the product) vs casual English 'group of agents'.","microsoft\u002Ffsi-banking-payments-dispute-resolution-accelerator","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BAVFSPPF5KP50DCBC2R4Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcross-squad\u002FSKILL.md",[],[19,20,21,22,23],"cross squad","squad","review","orchestration","create","2026-11-10 10:12:30",false,"---\nname: \"cross-squad\"\ndescription: \"Coordinating work across multiple Squad instances — discovery, delegation, and disambiguation when the user says 'squad' (the product) vs casual English 'group of agents'.\"\ndomain: \"orchestration\"\nconfidence: \"medium\"\nsource: \"manual\"\ntriggers:\n  - \"spawn N squads\"\n  - \"spawn a squad\"\n  - \"another squad\"\n  - \"two squads of\"\n  - \"second squad\"\n  - \"fan out to squads\"\n  - \"delegate to a squad\"\n  - \"set up squads for\"\n  - \"create a squad to review\"\n  - \"ask the other squad\"\ntools:\n  - name: \"squad-discover\"\n    description: \"List known squads and their capabilities\"\n    when: \"When you need to find which squad can handle a task\"\n  - name: \"squad-delegate\"\n    description: \"Create work in another squad's repository\"\n    when: \"When a task belongs to another squad's domain\"\n---\n\n## Context\n\n> **Read this FIRST any time the user says \"squad\" as a thing to spawn, delegate to, address, or fan out to** — e.g., *\"spawn two squads of designers and devs\"*, *\"ask the other squad\"*, *\"delegate to a squad\"*. In Squad-PRODUCT vocabulary, \"squad\" is a **peer** (an independent installation with its own `.squad\u002F`, `team.md`, MCP server, and agents) — NOT a generic English synonym for \"team\" or \"group\". Do not fan out raw `task` agents inside your own coordinator context when the user means \"another squad\". Use the discovery and communication patterns below (and the companion `cross-squad-communication` skill for the actual protocols).\n\nWhen an organization runs multiple Squad instances (e.g., platform-squad, frontend-squad, data-squad), those squads need to discover each other, share context, and hand off work across repository boundaries. This skill teaches agents how to coordinate across squads without creating tight coupling.\n\n> **Companion skill — for protocol details:** `cross-squad-communication\u002FSKILL.md` covers the four communication patterns (synchronous CLI, read-only knowledge query, git-based async, and GitHub-issue-based delegation) once a peer squad is discovered via the registry below. This skill answers \"who?\" — the companion answers \"how?\".\n\nCross-squad orchestration applies when:\n- A task requires capabilities owned by another squad\n- An architectural decision affects multiple squads\n- A feature spans multiple repositories with different squads\n- A squad needs to request infrastructure, tooling, or support from another squad\n\n## Disambiguation: \"squad\" vs ad-hoc agents\n\nWhen the user uses the word **\"squad\" \u002F \"squads\"** or asks to **\"spawn a team\"**, the coordinator MUST treat it as a literal reference to a Squad install (a `.squad\u002F` directory with its own roster, casting, and coordinator) — NOT as a casual synonym for \"a group of sub-agents\".\n\n### Default behaviour (apply unless explicitly told otherwise)\n\n| User says | Coordinator does |\n|---|---|\n| *\"spawn two squads of X and Y\"* \u002F *\"set up squads for X, Y, Z\"* | Bootstrap N **real** Squad installs — separate folder + `git init` + `squad init` per squad — then use the cross-squad patterns below (`.squad\u002Fmanifest.json`, `squad registry add`, `squad delegate`) and the protocols in the `cross-squad-communication` skill |\n| *\"ask the other squad about X\"* \u002F *\"delegate to the data squad\"* | Discover the peer via `squad registry list` (or by reading a known `.squad\u002Fmanifest.json`), then use `cross-squad-communication` Pattern 0 \u002F 1 \u002F 2 \u002F 3 — never re-implement the protocol with `task` |\n| *\"spawn a few agents to do X\"* \u002F *\"have some agents review X\"* \u002F *\"in parallel, get sub-agents to...\"* | Ad-hoc `task` fan-out is fine — no `.squad\u002F` bootstrap needed. This is the only path where raw `task` is appropriate when the user mentioned a multi-agent activity |\n\n### Ambiguous? `ask_user`, never silently downgrade\n\nIf the request **could** be either interpretation AND bootstrapping real squads is non-trivial (more than one or two `squad init` runs), you MUST use the `ask_user` tool with a 2-choice prompt before proceeding:\n\n```\nquestion: \"Should I create separate Squad installs or just dispatch ad-hoc agents?\"\nchoices:\n  - \"Real squads — separate .squad\u002F per squad (heavier, persistent, can be re-engaged later)\"\n  - \"Ad-hoc agents — one-shot `task` dispatch (lighter, ephemeral, no .squad\u002F created)\"\n```\n\nThe cost of asking is one `ask_user`. The cost of getting it wrong is the user has to redo the work. **Never silently pick the cheaper option just because it feels disproportionate for the task size — surface the trade-off and let the user pick.**\n\n### Anti-patterns (every one of these is a real failure mode observed in production)\n\n- **Calling `task` sub-agents \"squad-alpha\" \u002F \"squad-beta\"** and treating them as squads. Naming something a squad doesn't make it one — a squad has its own `.squad\u002F`, `team.md`, MCP server, and coordinator. If those aren't there, it's not a squad.\n- **Matching a prior session's ad-hoc pattern without re-checking current intent.** If you see existing `reviews\u002Fsquad-alpha\u002F` folders from a previous run, that's a hint, NOT a contract — the user may have meant something different this time. Re-evaluate from scratch.\n- **Silently choosing the cheaper interpretation because \"bootstrapping two real squads for a 30-line app feels disproportionate\".** That's a judgment call for the USER to make, not the coordinator. Use `ask_user`.\n- **Loading the `cross-squad` skill, reading it, then doing `task` fan-out anyway** because the eager-execution \u002F parallel-fan-out doctrine pulled you back. The disambiguation rule on this page OVERRIDES the generic fan-out doctrine when \"squad\" was the trigger.\n\n## Patterns\n\n### Discovery via Manifest\nEach squad publishes a `.squad\u002Fmanifest.json` declaring its name, capabilities, and contact information. Squads discover each other through two mechanisms:\n\n1. **`.squad\u002Fsquad-registry.json`** — **discovery-only.** Peer squads are findable via `squad discover` and addressable via `squad delegate`, but their skills\u002Fdecisions\u002Fwisdom are NOT loaded into your coordinator. Manage with `squad registry add\u002Flist\u002Fremove`.\n2. **`.squad\u002Fupstream.json`** — **discovery + inheritance.** Squads listed here are also discoverable, AND your coordinator inherits their skills\u002Fdecisions\u002Fwisdom\u002Frouting at session start. Manage with `squad upstream add\u002Flist\u002Fremove\u002Fsync`.\n\nBoth forms read the peer's manifest via the same code path. The `path` field is the **repository root** (e.g. `..\u002Ffriend-repo`), and Squad appends `.squad\u002Fmanifest.json` internally. Pointing at the `.squad\u002F` directory works too — Squad accepts both forms (`readManifest` strips a trailing `.squad` if present).\n\n```json\n{\n  \"name\": \"platform-squad\",\n  \"version\": \"1.0.0\",\n  \"description\": \"Platform infrastructure team\",\n  \"capabilities\": [\"kubernetes\", \"helm\", \"monitoring\", \"ci-cd\"],\n  \"contact\": {\n    \"repo\": \"org\u002Fplatform\",\n    \"labels\": [\"squad:platform\"]\n  },\n  \"accepts\": [\"issues\", \"prs\"],\n  \"skills\": [\"helm-developer\", \"operator-developer\", \"pipeline-engineer\"]\n}\n```\n\n### Context Sharing\nWhen delegating work, share only what the target squad needs:\n- **Capability list**: What this squad can do (from manifest)\n- **Relevant decisions**: Only decisions that affect the target squad\n- **Handoff context**: A concise description of why this work is being delegated\n\nDo NOT share:\n- Internal team state (casting history, session logs)\n- Full decision archives (send only relevant excerpts)\n- Authentication credentials or secrets\n\n### Work Handoff Protocol\n1. **Check manifest**: Verify the target squad accepts the work type (issues, PRs)\n2. **Create issue**: Use `gh issue create` in the target repo with:\n   - Title: `[cross-squad] \u003Cdescription>`\n   - Label: `squad:cross-squad` (or the squad's configured label)\n   - Body: Context, acceptance criteria, and link back to originating issue\n3. **Track**: Record the cross-squad issue URL in the originating squad's orchestration log\n4. **Poll**: Periodically check if the delegated issue is closed\u002Fcompleted\n\n### Feedback Loop\nTrack delegated work completion:\n- Poll target issue status via `gh issue view`\n- Update originating issue with status changes\n- Close the feedback loop when delegated work merges\n\n## Examples\n\n### Registering a peer squad (no inheritance)\n```bash\n# Friend's repo is checked out at ..\u002Ffriend-platform\u002F\nsquad registry add platform-squad ..\u002Ffriend-platform\n\n# Verify\nsquad registry list\nsquad discover\n```\n\n### Discovering squads\n```bash\n# List all squads discoverable from registry + upstreams\nsquad discover\n\n# Output:\n#   platform-squad  →  org\u002Fplatform  (kubernetes, helm, monitoring)\n#   frontend-squad  →  org\u002Ffrontend  (react, nextjs, storybook)\n#   data-squad      →  org\u002Fdata      (spark, airflow, dbt)\n```\n\n### Delegating work\n```bash\n# Delegate a task to the platform squad\nsquad delegate platform-squad \"Add Prometheus metrics endpoint for the auth service\"\n\n# Creates issue in org\u002Fplatform with cross-squad label and context\n```\n\n### Manifest in squad.config.ts\n```typescript\nexport default defineSquad({\n  manifest: {\n    name: 'platform-squad',\n    capabilities: ['kubernetes', 'helm'],\n    contact: { repo: 'org\u002Fplatform', labels: ['squad:platform'] },\n    accepts: ['issues', 'prs'],\n    skills: ['helm-developer', 'operator-developer'],\n  },\n});\n```\n\n## Anti-Patterns\n- **Direct file writes across repos** — Never modify another squad's `.squad\u002F` directory. Use issues and PRs as the communication protocol.\n- **Tight coupling** — Don't depend on another squad's internal structure. Use the manifest as the public API contract.\n- **Unbounded delegation** — Always include acceptance criteria and a timeout. Don't create open-ended requests.\n- **Skipping discovery** — Don't hardcode squad locations. Use manifests and the discovery protocol.\n- **Sharing secrets** — Never include credentials, tokens, or internal URLs in cross-squad issues.\n- **Circular delegation** — Track delegation chains. If squad A delegates to B which delegates back to A, something is wrong.\n","## Context\n\n> **Read this FIRST any time the user says \"squad\" as a thing to spawn, delegate to, address, or fan out to** — e.g., *\"spawn two squads of designers and devs\"*, *\"ask the other squad\"*, *\"delegate to a squad\"*. In Squad-PRODUCT vocabulary, \"squad\" is a **peer** (an independent installation with its own `.squad\u002F`, `team.md`, MCP server, and agents) — NOT a generic English synonym for \"team\" or \"group\". Do not fan out raw `task` agents inside your own coordinator context when the user means \"another squad\". Use the discovery and communication patterns below (and the companion `cross-squad-communication` skill for the actual protocols).\n\nWhen an organization runs multiple Squad instances (e.g., platform-squad, frontend-squad, data-squad), those squads need to discover each other, share context, and hand off work across repository boundaries. This skill teaches agents how to coordinate across squads without creating tight coupling.\n\n> **Companion skill — for protocol details:** `cross-squad-communication\u002FSKILL.md` covers the four communication patterns (synchronous CLI, read-only knowledge query, git-based async, and GitHub-issue-based delegation) once a peer squad is discovered via the registry below. This skill answers \"who?\" — the companion answers \"how?\".\n\nCross-squad orchestration applies when:\n- A task requires capabilities owned by another squad\n- An architectural decision affects multiple squads\n- A feature spans multiple repositories with different squads\n- A squad needs to request infrastructure, tooling, or support from another squad\n\n## Disambiguation: \"squad\" vs ad-hoc agents\n\nWhen the user uses the word **\"squad\" \u002F \"squads\"** or asks to **\"spawn a team\"**, the coordinator MUST treat it as a literal reference to a Squad install (a `.squad\u002F` directory with its own roster, casting, and coordinator) — NOT as a casual synonym for \"a group of sub-agents\".\n\n### Default behaviour (apply unless explicitly told otherwise)\n\n| User says | Coordinator does |\n|---|---|\n| *\"spawn two squads of X and Y\"* \u002F *\"set up squads for X, Y, Z\"* | Bootstrap N **real** Squad installs — separate folder + `git init` + `squad init` per squad — then use the cross-squad patterns below (`.squad\u002Fmanifest.json`, `squad registry add`, `squad delegate`) and the protocols in the `cross-squad-communication` skill |\n| *\"ask the other squad about X\"* \u002F *\"delegate to the data squad\"* | Discover the peer via `squad registry list` (or by reading a known `.squad\u002Fmanifest.json`), then use `cross-squad-communication` Pattern 0 \u002F 1 \u002F 2 \u002F 3 — never re-implement the protocol with `task` |\n| *\"spawn a few agents to do X\"* \u002F *\"have some agents review X\"* \u002F *\"in parallel, get sub-agents to...\"* | Ad-hoc `task` fan-out is fine — no `.squad\u002F` bootstrap needed. This is the only path where raw `task` is appropriate when the user mentioned a multi-agent activity |\n\n### Ambiguous? `ask_user`, never silently downgrade\n\nIf the request **could** be either interpretation AND bootstrapping real squads is non-trivial (more than one or two `squad init` runs), you MUST use the `ask_user` tool with a 2-choice prompt before proceeding:\n\n```\nquestion: \"Should I create separate Squad installs or just dispatch ad-hoc agents?\"\nchoices:\n  - \"Real squads — separate .squad\u002F per squad (heavier, persistent, can be re-engaged later)\"\n  - \"Ad-hoc agents — one-shot `task` dispatch (lighter, ephemeral, no .squad\u002F created)\"\n```\n\nThe cost of asking is one `ask_user`. The cost of getting it wrong is the user has to redo the work. **Never silently pick the cheaper option just because it feels disproportionate for the task size — surface the trade-off and let the user pick.**\n\n### Anti-patterns (every one of these is a real failure mode observed in production)\n\n- **Calling `task` sub-agents \"squad-alpha\" \u002F \"squad-beta\"** and treating them as squads. Naming something a squad doesn't make it one — a squad has its own `.squad\u002F`, `team.md`, MCP server, and coordinator. If those aren't there, it's not a squad.\n- **Matching a prior session's ad-hoc pattern without re-checking current intent.** If you see existing `reviews\u002Fsquad-alpha\u002F` folders from a previous run, that's a hint, NOT a contract — the user may have meant something different this time. Re-evaluate from scratch.\n- **Silently choosing the cheaper interpretation because \"bootstrapping two real squads for a 30-line app feels disproportionate\".** That's a judgment call for the USER to make, not the coordinator. Use `ask_user`.\n- **Loading the `cross-squad` skill, reading it, then doing `task` fan-out anyway** because the eager-execution \u002F parallel-fan-out doctrine pulled you back. The disambiguation rule on this page OVERRIDES the generic fan-out doctrine when \"squad\" was the trigger.\n\n## Patterns\n\n### Discovery via Manifest\nEach squad publishes a `.squad\u002Fmanifest.json` declaring its name, capabilities, and contact information. Squads discover each other through two mechanisms:\n\n1. **`.squad\u002Fsquad-registry.json`** — **discovery-only.** Peer squads are findable via `squad discover` and addressable via `squad delegate`, but their skills\u002Fdecisions\u002Fwisdom are NOT loaded into your coordinator. Manage with `squad registry add\u002Flist\u002Fremove`.\n2. **`.squad\u002Fupstream.json`** — **discovery + inheritance.** Squads listed here are also discoverable, AND your coordinator inherits their skills\u002Fdecisions\u002Fwisdom\u002Frouting at session start. Manage with `squad upstream add\u002Flist\u002Fremove\u002Fsync`.\n\nBoth forms read the peer's manifest via the same code path. The `path` field is the **repository root** (e.g. `..\u002Ffriend-repo`), and Squad appends `.squad\u002Fmanifest.json` internally. Pointing at the `.squad\u002F` directory works too — Squad accepts both forms (`readManifest` strips a trailing `.squad` if present).\n\n```json\n{\n  \"name\": \"platform-squad\",\n  \"version\": \"1.0.0\",\n  \"description\": \"Platform infrastructure team\",\n  \"capabilities\": [\"kubernetes\", \"helm\", \"monitoring\", \"ci-cd\"],\n  \"contact\": {\n    \"repo\": \"org\u002Fplatform\",\n    \"labels\": [\"squad:platform\"]\n  },\n  \"accepts\": [\"issues\", \"prs\"],\n  \"skills\": [\"helm-developer\", \"operator-developer\", \"pipeline-engineer\"]\n}\n```\n\n### Context Sharing\nWhen delegating work, share only what the target squad needs:\n- **Capability list**: What this squad can do (from manifest)\n- **Relevant decisions**: Only decisions that affect the target squad\n- **Handoff context**: A concise description of why this work is being delegated\n\nDo NOT share:\n- Internal team state (casting history, session logs)\n- Full decision archives (send only relevant excerpts)\n- Authentication credentials or secrets\n\n### Work Handoff Protocol\n1. **Check manifest**: Verify the target squad accepts the work type (issues, PRs)\n2. **Create issue**: Use `gh issue create` in the target repo with:\n   - Title: `[cross-squad] \u003Cdescription>`\n   - Label: `squad:cross-squad` (or the squad's configured label)\n   - Body: Context, acceptance criteria, and link back to originating issue\n3. **Track**: Record the cross-squad issue URL in the originating squad's orchestration log\n4. **Poll**: Periodically check if the delegated issue is closed\u002Fcompleted\n\n### Feedback Loop\nTrack delegated work completion:\n- Poll target issue status via `gh issue view`\n- Update originating issue with status changes\n- Close the feedback loop when delegated work merges\n\n## Examples\n\n### Registering a peer squad (no inheritance)\n```bash\n# Friend's repo is checked out at ..\u002Ffriend-platform\u002F\nsquad registry add platform-squad ..\u002Ffriend-platform\n\n# Verify\nsquad registry list\nsquad discover\n```\n\n### Discovering squads\n```bash\n# List all squads discoverable from registry + upstreams\nsquad discover\n\n# Output:\n#   platform-squad  →  org\u002Fplatform  (kubernetes, helm, monitoring)\n#   frontend-squad  →  org\u002Ffrontend  (react, nextjs, storybook)\n#   data-squad      →  org\u002Fdata      (spark, airflow, dbt)\n```\n\n### Delegating work\n```bash\n# Delegate a task to the platform squad\nsquad delegate platform-squad \"Add Prometheus metrics endpoint for the auth service\"\n\n# Creates issue in org\u002Fplatform with cross-squad label and context\n```\n\n### Manifest in squad.config.ts\n```typescript\nexport default defineSquad({\n  manifest: {\n    name: 'platform-squad',\n    capabilities: ['kubernetes', 'helm'],\n    contact: { repo: 'org\u002Fplatform', labels: ['squad:platform'] },\n    accepts: ['issues', 'prs'],\n    skills: ['helm-developer', 'operator-developer'],\n  },\n});\n```\n\n## Anti-Patterns\n- **Direct file writes across repos** — Never modify another squad's `.squad\u002F` directory. Use issues and PRs as the communication protocol.\n- **Tight coupling** — Don't depend on another squad's internal structure. Use the manifest as the public API contract.\n- **Unbounded delegation** — Always include acceptance criteria and a timeout. Don't create open-ended requests.\n- **Skipping discovery** — Don't hardcode squad locations. Use manifests and the discovery protocol.\n- **Sharing secrets** — Never include credentials, tokens, or internal URLs in cross-squad issues.\n- **Circular delegation** — Track delegation chains. If squad A delegates to B which delegates back to A, something is wrong.\n",{"name":5,"tools":29,"domain":22,"source":38,"triggers":39,"confidence":50,"description":7},[30,34],{"name":31,"when":32,"description":33},"squad-discover","When you need to find which squad can handle a task","List known squads and their capabilities",{"name":35,"when":36,"description":37},"squad-delegate","When a task belongs to another squad's domain","Create work in another squad's repository","manual",[40,41,42,43,44,45,46,47,48,49],"spawn N squads","spawn a squad","another squad","two squads of","second squad","fan out to squads","delegate to a squad","set up squads for","create a squad to review","ask the other squad","medium","main","5494201db9619bc6c0de7999caa5ae7ae315e6be",".github\u002Fskills\u002Fcross-squad",3,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-10-27 01:08:00",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add microsoft\u002Ffsi-banking-payments-dispute-resolution-accelerator --skill cross-squad",{"tool":66,"command":67},"bunx","bunx skills add microsoft\u002Ffsi-banking-payments-dispute-resolution-accelerator --skill cross-squad",{"tool":69,"command":70},"pnpm","pnpm dlx skills add microsoft\u002Ffsi-banking-payments-dispute-resolution-accelerator --skill cross-squad","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcross-squad\u002FSKILL.md",true,[74,80,84,88,92,96,100,104,108,112,116,120,126,130,134,138,142],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fapproval-checklist.md","REFERENCE","参考文档",4224,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Freferences\u002Fapproval-checklist.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fasset-organization.md",5110,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Freferences\u002Fasset-organization.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fbrand-guideline-template.md",3572,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Freferences\u002Fbrand-guideline-template.md",{"path":89,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fcolor-palette-management.md",4254,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Freferences\u002Fcolor-palette-management.md",{"path":93,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fconsistency-checklist.md",1926,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Freferences\u002Fconsistency-checklist.md",{"path":97,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Flogo-usage-rules.md",5464,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Freferences\u002Flogo-usage-rules.md",{"path":101,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fmessaging-framework.md",1763,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Freferences\u002Fmessaging-framework.md",{"path":105,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Ftypography-specifications.md",5042,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Freferences\u002Ftypography-specifications.md",{"path":109,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fupdate.md",3842,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Freferences\u002Fupdate.md",{"path":113,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fvisual-identity.md",1884,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Freferences\u002Fvisual-identity.md",{"path":117,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":118,"sourceHtmlUrl":119},"references\u002Fvoice-framework.md",1997,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Freferences\u002Fvoice-framework.md",{"path":121,"resourceType":122,"resourceTypeDesc":123,"sizeBytes":124,"sourceHtmlUrl":125},"scripts\u002Fextract-colors.cjs","SCRIPT","脚本",9182,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Fscripts\u002Fextract-colors.cjs",{"path":127,"resourceType":122,"resourceTypeDesc":123,"sizeBytes":128,"sourceHtmlUrl":129},"scripts\u002Finject-brand-context.cjs",9677,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Fscripts\u002Finject-brand-context.cjs",{"path":131,"resourceType":122,"resourceTypeDesc":123,"sizeBytes":132,"sourceHtmlUrl":133},"scripts\u002Fsync-brand-to-tokens.cjs",14209,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Fscripts\u002Fsync-brand-to-tokens.cjs",{"path":135,"resourceType":122,"resourceTypeDesc":123,"sizeBytes":136,"sourceHtmlUrl":137},"scripts\u002Ftests\u002Ftest_sync_brand_to_tokens.py",12460,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Fscripts\u002Ftests\u002Ftest_sync_brand_to_tokens.py",{"path":139,"resourceType":122,"resourceTypeDesc":123,"sizeBytes":140,"sourceHtmlUrl":141},"scripts\u002Fvalidate-asset.cjs",10173,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Fscripts\u002Fvalidate-asset.cjs",{"path":143,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":144,"sourceHtmlUrl":145},"templates\u002Fbrand-guidelines-starter.md",6638,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fnextlevelbuilder_ui-ux-pro-max\u002Fbrand\u002Ftemplates\u002Fbrand-guidelines-starter.md",[147,162,169,175,189,203],{"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":158,"publishedAt":24},"01M69BCQ2R27TFYA8Q03XFNFWM","{skill-name}","{what this skill teaches agents}","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskill.md",[153],{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[159,160,161],"{skill name}","testing","design",{"skillNo":163,"name":164,"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":165,"categories":166,"keywords":167,"publishedAt":24},"01M69BCNFGJTKKASKWDB0MM668","azd-seed-hook","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.squad\u002Fskills\u002Fazd-seed-hook\u002FSKILL.md",[],[168],"azd seed hook",{"skillNo":170,"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":171,"categories":172,"keywords":174,"publishedAt":24},"01M69BCDES6M5FRTCMY7214B94","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.squad\u002Fskill.md",[173],{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},[159,160,161],{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":185,"publishedAt":24},"01M69BCBAGT24AD5SBDP876P09","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[181,184],{"categoryNo":182,"categoryName":183,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},[186,187,161,188],"memory","tiered memory","performance",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":198,"publishedAt":24},"01M69BC9SWSK7ZX02AKTVT16E9","test-discipline","Update tests when changing APIs — no exceptions","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftest-discipline\u002FSKILL.md",[195],{"categoryNo":196,"categoryName":197,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000008","测试与质量",[199,200,201,202],"test discipline","test","sync","update",{"skillNo":204,"name":20,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":208,"publishedAt":24},"01M69BC7MR12QTSH97DCQYB81N","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\u002Fmicrosoft\u002Ffsi-banking-payments-dispute-resolution-accelerator\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsquad\u002FSKILL.md",[],[20,209,210,211],"cli","squad commands","sessions"]