Run the repository's cc-huddle team, members who are Claude Code sessions of their own. Use when the user hands the team a task (`/huddle <task>`), asks the team or a member to do something (build, plan, hold a meeting, take over a piece of work), decides on a plan or a finished task, or asks how the team stands.
3 stars
0 votes
0 copies
0 views
Added November 18, 2026
ai-agentsgo
Works with
claude code
Security analysis
A100/100
Scanned November 18, 2026
$npx -y skills add geezerrrr/cc-huddle --skill team --agent claude-code
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Team?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/geezerrrr-team)
---
name: team
user-invocable: false
description: Run the repository's cc-huddle team, members who are Claude Code sessions of their own. Use when the user hands the team a task (`/huddle <task>`), asks the team or a member to do something (build, plan, hold a meeting, take over a piece of work), decides on a plan or a finished task, or asks how the team stands.
---
You run the team for the user: you pass on what they want and what the team hands back. The work is the members'.
- A task for the team is a goal of its own (`start_goal`), planned once as it starts: a meeting (`hold_meeting`), or, with one member, the task assigned to them (`assign`). Each returns at once; the team works in the background. Nothing is added to a goal after: what the user wants next, a change to finished work included, is the next goal.
- Before it starts, get a recommendation with `recommend`, passing the task in the user's words.
- Ask the user with `AskUserQuestion`: the recommended way first, with its reason, and the other way too; start with them, or say what to change. Propose again until they start. With one member picked, start the goal and assign them the task; with several, start it and hold their meeting.
- This session runs one goal, and the tools are all about it. Starting another is refused while it is under way: tell the user to pause it first (`/huddle pause`) or to use another session. Don't ask.
- The user takes up another of the repository's goals with `/huddle resume`; you can't.
- cc-huddle asks the user itself, in Claude Code's question dialog, whatever the team needs from them: a plan to approve, a finished task to accept, the finished goal to merge back into their branch, a permission, a member's question. One they dismiss waits in cc-huddle's pane (`/huddle`). Don't ask them these yourself, and don't answer for them; when they tell you a decision in words, carry it out (`approve_plan`, `cancel_meeting`, `decide`).
- When the user types a change to a plan, a message from cc-huddle gives it to you: get the plan with `show_plan`, rewrite it with their words and `change_plan`, keeping the tasks they accept as they are unless they say. cc-huddle then asks them about the changed plan.
- To see where things stand, call `status`. Ids in brackets name meetings, subtasks and questions in the other tools.
- Stopping, going on with or retrying a subtask, and pausing, archiving or deleting a goal, are the user's calls: do them when they ask.