Claude projection copies all 50 template skills, including Squad's own repo/release skills, into user projects; Copilot gets 19, so the hosts see different skill sets
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 66/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, typescript
- Domain
- cli, developer-experience
Research direction
Start with projectClaudeSkills in packages/squad-sdk/src/client/adapters/claude-skills.ts and TEMPLATE_MANIFEST in packages/squad-cli/src/cli/core/templates.ts. Compare the projected skills after init --roles --client copilot,claude, including the listed skip rules and any team overrides. Done when both hosts receive the same user-facing template skills, with only the stated host-specific differences.
Written by the indexing model from the issue text.
Description
Version: CLI built from release/prepare-2.0.0-preview.5 @ 38d45d02 (package version 2.0.0-preview.6).
What happens
After a fresh init --client copilot,claude, the two hosts get very different skill sets:
D=$(mktemp -d); cd "$D"; git init -q
node <squad-cli>/dist/cli-entry.js init --roles --client copilot,claude
ls -1 .squad/templates/skills | wc -l # 50
ls -1 .github/skills | wc -l # 19
ls -1 .claude/skills | wc -l # 53 (50 templates − 2 skipped init-mode + 5 squad-coordinator-*)
There are 35 skills only in .claude/skills/. Several of them are about developing and releasing Squad itself and mean nothing in a user's project:
| Skill | Description (frontmatter) |
|---|---|
release-process |
"Prepare, publish, recover, and verify Squad insider, preview, and stable releases" |
versioning-policy |
"SemVer rules for Squad's stable, preview, insider, and local package versions" |
cli-wiring |
"Checklist for wiring a new Squad CLI command: route it in cli-entry.ts, …" |
ci-validation-gates |
Squad's own CI gates (semver validation, token checks, draft detection) |
windows-compatibility |
Squad's cross-platform path handling |
gh-aw-enlistment |
Enlisting a repo into Squad's gh-aw bootstrap |
e2e-template-testing |
"End-to-end validation of coordinator and agent template changes" |
docs-standards |
Squad-specific documentation patterns |
.github/skills/squad-conventions is also Squad-internal ("Core conventions and patterns used in the Squad codebase"), so Copilot projects get one of these too.
Why it matters:
- Claude Code lists every
.claude/skills/*skill to the model and auto-loads them on description match. In a user's repo, "prepare a release" or "bump the version" can pull in Squad's npm release runbook. - The same team behaves differently on each host. The Copilot coordinator's skill-aware routing (core protocol item 17) also scans
.claude/skills/, so in a dual-host repo the leak reaches Copilot spawns as well. - The only workaround today is adding a line to every charter telling members to ignore these skills.
Expected
- One explicit list of user-facing skills drives every host's projection, the same way
TEMPLATE_MANIFESTalready drives.github/skills. Template skills that are about the Squad repo itself either aren't shipped in.squad/templates/skills/or are marked (for exampleaudience: squad-repoin frontmatter) and skipped by every projection. .claude/skillsand.github/skillscarry the same user-facing template skills. The only differences are deliberate host-specific ones, like thesquad-coordinator-*skills and the skipped Copilot Init Mode.
Source
packages/squad-sdk/src/client/adapters/claude-skills.ts,projectClaudeSkills, line 74:for (const name of dirs(templatesAbs))projects every directory under.squad/templates/skills/. It skips onlyCLAUDE_SKIPPED_TEMPLATE_SKILLS(init-mode,coordinator-init-mode) and team-overridden names.packages/squad-cli/src/cli/core/templates.ts(TEMPLATE_MANIFEST,../.github/skills/...entries from line ~217): the explicit 19-skill list for.github/skills.
Related: #2438 / #2469 (Claude host), #1436 (drop the template folder from .squad).
🤖 Generated with Claude Code
- Dominant language
- TypeScript
- Stars
- 3.4k
- Forks
- 516
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 116
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/squad
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
Similar issues
-
bot:ai-assisted component:platform-js status:untriaged
Difficulty 1/5 Under an hour Newbie friendliness 74/100
midnightntwrk/platform-js#38 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ranxianglei/billion-context#7068 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mybigday/whisper.rn#348 ·
-
enhancement severity:low
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Battle-Cattle/BCUK-Bot-4#1075 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
ilan-pinto/roaring-lions#1552 ·
Maintainers usually reply within 1 day