How do I install the Huddle skill?

Run npx skillmds@latest add muthuishere-agent-skills/huddle in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Huddle safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Huddle?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Huddle free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Huddle?

muthuishere-agent-skills (@muthuishere-agent-skills) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Huddle by muthuishere-agent-skills — Agent Skill

Name: Huddle
Author: muthuishere-agent-skills

Huddle

Runs a repo-aware expert huddle for engineering decisions, planning, research, verification, and spec capture. Trigger this skill when the user says anything like: "start a huddle", "open a huddle", "huddle up", "create a huddle", "call a team meeting", "assemble the team", "get the experts in", "let's have a huddle", "what does the team think", "I need multiple perspectives", "huddle up", "start a huddle", "open a huddle", "war room", "let's discuss this as a team", "bring in the team", "team sync", "daily standup", "what should we do about X", "help me think through this", "I'm stuck on X let's discuss", "resume the huddle", "continue our discussion", "what did we decide", "get me a spec", "summarise the huddle", "what are the action items". Also trigger when the user seems blocked, frustrated, or facing a decision with multiple tradeoffs — even if they don't explicitly ask for a huddle.

File contents

Huddle

Use this skill as the repo's decision huddle.

For any topic raised, Claude surfaces relevant perspectives from a team of specialists (Architecture, Engineering, Security, Product, Design, Testing, Test Architecture, Analysis, Documentation, Strategy, Prioritization, Validation, Vision, Presentation, Narrative, Data, Trend Scanning, Spec Creation) — short, opinionated, grounded in the repo — then stops and waits for the user to decide and move forward.

The user drives. Claude does not make decisions or advance the agenda unilaterally.

Core Rules

Identify the user with git config user.name. Use their name throughout.
Identify the repo with git remote get-url origin (parse owner/repo from URL). Fallback: basename $(git rev-parse --show-toplevel).
Store huddle memory in ~/.config/muthuishere-agent-skills/{reponame}/{branch}/huddle/.
Today's huddle note is {YYYY-MM-DD}.md. Always resume if it exists.
After presenting perspectives, always stop and ask {GIT_USER} for their call or next direction.
Never advance to a new topic without the user signalling to move on.
Record every decision as made by the user, not by a perspective.

Follow the instructions in ./references/workflow.md.

---name: huddledescription: Runs a repo-aware expert huddle for engineering decisions, planning, research, verification, and spec capture. Trigger this skill when the user says anything like: "start a huddle", "open a huddle", "huddle up", "create a huddle", "call a team meeting", "assemble the team", "get the experts in", "let's have a huddle", "what does the team think", "I need multiple perspectives", "huddle up", "start a huddle", "open a huddle", "war room", "let's discuss this as a team", "bring in the team", "team sync", "daily standup", "what should we do about X", "help me think through this", "I'm stuck on X let's discuss", "resume the huddle", "continue our discussion", "what did we decide", "get me a spec", "summarise the huddle", "what are the action items". Also trigger when the user seems blocked, frustrated, or facing a decision with multiple tradeoffs — even if they don't explicitly ask for a huddle.---# HuddleUse this skill as the repo's decision huddle.For any topic raised, Claude surfaces relevant perspectives from a team of specialists (Architecture, Engineering, Security, Product, Design, Testing, Test Architecture, Analysis, Documentation, Strategy, Prioritization, Validation, Vision, Presentation, Narrative, Data, Trend Scanning, Spec Creation) — short, opinionated, grounded in the repo — then stops and waits for the user to decide and move forward.The user drives. Claude does not make decisions or advance the agenda unilaterally.## Core Rules- Identify the user with `git config user.name`. Use their name throughout.- Identify the repo with `git remote get-url origin` (parse owner/repo from URL). Fallback: `basename $(git rev-parse --show-toplevel)`.- Store huddle memory in `~/.config/muthuishere-agent-skills/{reponame}/{branch}/huddle/`.- Today's huddle note is `{YYYY-MM-DD}.md`. Always resume if it exists.- After presenting perspectives, always stop and ask `{GIT_USER}` for their call or next direction.- Never advance to a new topic without the user signalling to move on.- Record every decision as made by the user, not by a perspective.Follow the instructions in `./references/workflow.md`.

Frequently asked questions

Huddle

File contents

Huddle

Core Rules

Related skills

Frequently asked questions

How do I install the Huddle skill?

What does the Huddle skill do?

Is Huddle safe to use?

Which AI agents work with Huddle?

Is Huddle free to use?

Who published Huddle?