Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By nickwinder
Turn Slack conversation history into distilled persona files representing colleagues, then consult those personas individually or as a deliberating panel to pressure-test ideas, get pushback, and surface team agreement or disagreement.
npx claudepluginhub nickwinder/synthteam --plugin synthteamConsult a distilled persona of a colleague for their likely take, critique, or pushback on an idea — locally, without involving them. Use when the user wants to brainstorm, pressure-test a plan, anticipate a reaction, spot missed objections, or stress-test a decision through a specific person's lens. Personas live at ~/.synthteam/personas/<name>.md and capture knowledge, opinions, and decision-making patterns (not voice or style). Invoke when the user says "ask <name>", "what would <name> think", "get <name>'s take", "/ask-colleague <name> ...", or any similar request for a colleague's perspective.
Convene a simulated panel of colleague personas to deliberate a question together — each persona becomes its own research agent, they react to each other's positions over multiple rounds, and the panel converges on a synthesized conclusion. Use when the user wants more than one perspective on a decision, a cross-functional gut-check, a debate between viewpoints, or a comprehensive answer that surfaces where teammates would agree and disagree. Invoke when the user says "ask the team", "/ask-team ...", "what would the team think", "get a panel on this", "run this past everyone", "convene the personas", or asks for multiple colleagues' takes at once. For a single colleague's take, use ask-colleague instead.
Build or refresh a distilled persona doc for a colleague from their Slack history — dump their channel messages, then run a multi-agent distillation into a structured persona file that the ask-colleague and ask-team skills consume. Use when the user wants to "dump <name>'s Slack", "distill <name>'s persona", "build a persona for <name>", "add <name> as a colleague", "refresh <name>'s persona", or otherwise create/update the source files behind ask-colleague. This is the ingestion-side skill; ask-colleague and ask-team only read what this produces.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Official Slack MCP server for interactive and collaborative workflows. Surface insights, draft messages, and engage teams directly within Slack from Claude Cowork.
Dynamically assemble expert agent teams for complex tasks using Claude Code's agent teams feature
Enterprise search across documents, Slack, email, and other sources via Glean. Requires glean-core.
Compile humans into AI agents through deep interviews. Conducts comprehensive behavioral interviews, analyzes work artifacts via MCP tools, and generates installable Claude Code plugins that embody a person's decision-making, communication style, and expertise.
Slack integration for searching messages, sending communications, managing canvases, and more
Leadership & people skills: Performance Review, Hiring Rubric, Team Offsite Planner. Write structured reviews, build interview scorecards, and plan offsites from goals to minute-by-minute agenda.
A plugin for consulting distilled personas of colleagues — locally, without involving them. Useful for pressure-testing plans, anticipating pushback, or stress-testing decisions through someone else's lens.
Personas are simulations, not the real people. Verify anything load-bearing with the real humans before acting on it.
The plugin has three skills that split into an ingestion side and a consumption side. distill-slack-persona produces persona docs; ask-colleague and ask-team consume them. Every persona that exists is automatically available to both consuming skills.
Turns a colleague's Slack history into a structured persona doc: a natural-language description of what they know, what they believe, and how they decide. It dumps their channel messages with a script, then runs a multi-agent pipeline that distills the raw messages into five facets (strategic priorities, specific opinions, decision-making patterns, domain knowledge, and operational context). The doc captures substance, not voice — no verbatim text, no style mimicry. This is the only skill that writes personas; the others just read them. See how to use it below.
Consults a single distilled persona for their likely take, critique, or pushback on an idea — locally, without involving the real person. Use it to pressure-test a plan, anticipate a reaction, or surface the objection you might dodge by not asking. It answers in first-person as that person would reason, grounded in their persona doc, and flags when it's extrapolating beyond what the doc covers.
Invoke it:
ask alex about <idea>,what would alex think of <plan>, or/ask-colleague alex …
Convenes a simulated panel of all your personas to deliberate a question together. Each persona becomes its own research agent, forms a position, then reacts to everyone else's positions across multiple rounds until the panel converges. The output maps where the team agrees, where it genuinely splits and why, and what only the real humans can settle. More expensive than ask-colleague (~8–12 subagent runs) — reach for it when one perspective isn't enough.
Invoke it:
ask the team about <question>,run this past everyone, or/ask-team …
> ask alex about dropping the offline cache
Alex (Staff Engineer) — likely take:
I'd push back. We added that cache after the Q3 outage when the
upstream API flaked for 40 minutes — dropping it reintroduces a
single point of failure. If the goal is bundle size, I'd argue
for shrinking the cache, not removing it.
⚠ Extrapolating: the persona doc has no signal on the *current*
reliability numbers — check those with the real Alex.
ask-colleague to pressure-test a plan, anticipate one person's pushback, or surface the objection you'd dodge by not asking.ask-team when one perspective isn't enough — cross-functional gut-checks, or decisions that genuinely split a team.Personas and raw Slack dumps live under ~/.synthteam/ — deliberately outside the plugin so they survive reinstalls and are reachable by whichever skills are installed (override the location with the SYNTHTEAM_HOME env var):
~/.synthteam/
├── assets/<slug>/ # raw Slack dumps — local-only, never committed
│ ├── raw-messages.jsonl
│ └── metadata.json
└── personas/<slug>.md # the distilled persona docs the ask-* skills read
synthteam/
├── .claude-plugin/
│ └── plugin.json # plugin manifest
├── .env.example # SLACK_USER_TOKEN for the dump script
├── README.md # this file
├── COMPLIANCE.md # GDPR / works-council / privacy-law notes
└── skills/
├── distill-slack-persona/ # ingestion: dump Slack + distill personas
│ ├── SKILL.md
│ ├── README.md
│ ├── package.json # node deps for the dump script
│ ├── scripts/ # Slack ingestion
│ └── references/ # distillation-facets.md — the pipeline spec
├── ask-colleague/ # consume: single-persona take
│ ├── SKILL.md
│ └── README.md
└── ask-team/ # consume: multi-persona deliberation panel
├── SKILL.md
└── README.md
This repo ships as a plugin marketplace for both Claude Code and Codex. Add the marketplace, then install the plugin from it.
Inside Claude Code, from GitHub: