blinkingsun/claude-team-skill — explained in plain English
Analysis updated 2026-05-18
Add multi-model review to your Claude Code workflow so a second AI checks plans before code is written.
Split a coding task across cheap and expensive models automatically based on difficulty.
Get an independent AI verification pass on generated code before merging it.
Watch a live narrated report of how different AI models disagree and resolve issues on a task.
| blinkingsun/claude-team-skill | 123satyajeet123/bitnet-server | adeilsonrbrito/cross-model-consult | |
|---|---|---|---|
| Stars | 0 | 0 | 0 |
| Language | Shell | Shell | Shell |
| Setup difficulty | moderate | easy | moderate |
| Complexity | — | 2/5 | 3/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Needs a paid SuperGrok or X Premium+ subscription for the auditor and verifier models.
This project is a skill you add to Claude Code, the command line coding assistant from Anthropic. It adds a new command called /team that turns a single coding task into a small team of AI models working together instead of one model doing everything alone. Here is how a run plays out. One model, called Fable, plans the task and breaks it into smaller pieces. A second model, Grok, checks that plan before any code gets written, pointing out risks or gaps and suggesting which pieces could run at the same time. Then the actual coding work goes to Claude models split by difficulty: harder problems go to a stronger model, routine edits go to a cheaper one. Once the work is done, Grok checks it again, this time comparing the result against the original plan and flagging anything that does not match. If problems are found, the same worker gets a chance to fix them before Fable reviews the final result, merges it, and runs the real tests. The idea behind splitting the work this way is that the checking model is never the same model that wrote the code, so mistakes are less likely to slip through unnoticed. It also keeps cost down, since the auditing and verification steps run on a separate Grok subscription rather than eating into your Claude usage. Setting it up takes three steps: installing the Grok command line tool, which needs a paid X or SuperGrok subscription, installing a bridge tool that lets Claude talk to Grok, and then installing this skill itself. Once installed, you configure a roster file that lists which model does which job, and you can edit it freely to add, remove, or swap out models. This is a tool for people who already use Claude Code and want more oversight on their AI generated changes, not a general purpose product for non-coders.
A Claude Code add-on that runs coding tasks through a team of AI models: one plans, another audits and verifies, and Claude models do the actual coding.
Mainly Shell. The stack also includes Shell, Claude Code, Grok.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.