bchanot/claude
1
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

job3: B2 profile — document actual plugin/MCP toggling (BDR-008)

Browse Source
This commit is contained in:
Bastien Chanot
2026-07-06 16:54:08 +02:00
parent 16a5a26cc9
commit 28ce7325dd
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/profile/SKILL.md
+4 -3
View File
@@ -116,8 +116,9 @@ bash "$HOME/.claude/lib/profile.sh" $ARGUMENTS
- gstack skills still depend on `~/.claude/skills/gstack/bin/` for telemetry, - gstack skills still depend on `~/.claude/skills/gstack/bin/` for telemetry,
update-check, learnings — script doesn't touch that infra. Disabled skills update-check, learnings — script doesn't touch that infra. Disabled skills
are just hidden from Claude Code's scanner; the gstack repo stays installed. are just hidden from Claude Code's scanner; the gstack repo stays installed.
- Profile changes do NOT toggle Claude Code plugins (ui-ux-pro-max, etc.) or - Profile changes DO toggle the managed Claude Code plugins (ui-ux-pro-max,
MCP servers — those are advisory only. The user runs `claude plugin plugin-dev, pr-review-toolkit) and the `magic` MCP — see the Mechanism table
enable|disable` and `claude mcp add|remove` manually. above (BDR-008). Anything outside that managed set stays manual:
`claude plugin enable|disable`, `claude mcp add|remove`.
- `set` is destructive in the sense that it disables non-listed gstack skills. - `set` is destructive in the sense that it disables non-listed gstack skills.
Use `apply` if the user wants additive behavior. Use `apply` if the user wants additive behavior.