Skill
audit-context
Evaluates ambient context artifacts (CLAUDE.md, memory, local skills, settings hooks) for compatibility with swarm governance. Returns a classified report so…
Development
Skill
/suggest-members
Recommends team composition based on outcomes and mode. Invoked by launch commands during team setup.
Install
$ npx -y skills add DheerG/swarms --skill suggest-members --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/suggest-members
Context preview
The summary Claude sees to decide when to auto-load this skill.
Recommends team composition based on outcomes and mode. Invoked by launch commands during team setup.
SKILL.md
suggest-members.SKILL.mdname: suggest-members
user-invocable: false
description: |
Recommends team composition based on outcomes and mode. Invoked by launch commands during team setup.
Suggest additional team members based on the user's outcomes and selected mode. The lead and facilitator are always included.
**Mode guidance:**
- **Code mode** — suggest a mix of technical and domain-specific voices. Include at least one member who represents the customer or business perspective (Director of Customer Success, RevOps lead, BizOps expert).
- **Writing mode** — suggest writing-domain voices: strategist, editor, and at least one domain expert relevant to the subject matter. Researcher as needed. Avoid engineering roles unless the subject requires them.
- **General mode** (the fallback when outcomes fit no specific mode) — suggest domain-relevant voices that match what the outcomes actually require. Include at least one member who represents the broader qualitative or business perspective.
- **Triage mode** — suggest investigators who can gather and weigh evidence from where the symptom points (code, logs, metrics, traces, issue history, user reports); keep roles tool-agnostic (no hardcoded observability vendor); include at least one voice attentive to blast radius — what a change at the breaking point would disturb downstream. Do not apply the Code-mode customer/business-perspective default unless the outcomes call for it.
- **No mode provided** — default to Code mode guidance.
Keep teams to 3-5 members total. Up to 8 for complex multi-domain work. All members except the lead are read-only.
Present your suggestion.
Rules when suggesting team members:
- Avoid constraining dynamic team members too much. Over-describing what their qualities are can result in constrainment
- Be careful of introducing biases which weren't prompted by the user.
Read more
name: suggest-members user-invocable: false description: | Recommends team composition based on outcomes and mode. Invoked by launch commands during team setup.
Suggest additional team members based on the user's outcomes and selected mode. The lead and facilitator are always included.
**Mode guidance:**
- **Code mode** — suggest a mix of technical and domain-specific voices. Include at least one member who represents the customer or business perspective (Director of Customer Success, RevOps lead, BizOps expert).
- **Writing mode** — suggest writing-domain voices: strategist, editor, and at least one domain expert relevant to the subject matter. Researcher as needed. Avoid engineering roles unless the subject requires them.
- **General mode** (the fallback when outcomes fit no specific mode) — suggest domain-relevant voices that match what the outcomes actually require. Include at least one member who represents the broader qualitative or business perspective.
- **Triage mode** — suggest investigators who can gather and weigh evidence from where the symptom points (code, logs, metrics, traces, issue history, user reports); keep roles tool-agnostic (no hardcoded observability vendor); include at least one voice attentive to blast radius — what a change at the breaking point would disturb downstream. Do not apply the Code-mode customer/business-perspective default unless the outcomes call for it.
- **No mode provided** — default to Code mode guidance.
Keep teams to 3-5 members total. Up to 8 for complex multi-domain work. All members except the lead are read-only.
Present your suggestion.
Rules when suggesting team members:
- Avoid constraining dynamic team members too much. Over-describing what their qualities are can result in constrainment
- Be careful of introducing biases which weren't prompted by the user.
Ships withswarm
Describe what you want. Get a reviewed, ship-ready PR — without babysitting the agent.
Get the whole plugin
Other skills on swarm.
Skill
code-mode
Code mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for…
Skill
define-rubric
Builds measurable validation criteria when no existing standards apply. Invoked by team agents during review.
Skill
gate-presentation
Returns the frozen gate constants — question, header, option labels and descriptions, digest field-list, and preview content — for every catalog gate. Invoked…
Skill
general-mode
General mode operational spec for the team lead. Returns lead identity, facilitator identity, suggest-members guidance, and phase arc for general-purpose…
Skill
independent-review-loo…
Independent review loop run before delivery in code work. An independent reviewer (Codex, or fresh Codex-style subagents) reads the whole PR against the…