panel
Skill0 starsChanged 5 months agoMITView on GitHub
Use to get independent perspectives on a topic from multiple models (a strong Claude model + Codex by default). Use with /core-skills:synthesize to merge.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- Vinix24/vnx-orchestrationtheir own version, first seen Nov 6, 2026
- leek/agent-skillstheir own version, first seen Nov 2, 2026
- ilchemla/agent-skillstheir own version, first seen Oct 13, 2026
- raine/consult-llm-mcptheir own version, first seen Oct 8, 2026
- scrypster/muninndbtheir own version, first seen Oct 8, 2026
- dkpapadopoulos/auto-claude-skillstheir own version, first seen Sep 22, 2026
Used with
Projects with it also use implement.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- scrypster/muninndb★ 332same name
- raine/consult-llm-mcp★ 148same name
- Vinix24/vnx-orchestration★ 63same name
- Reef123/OpenVera★ 9same name
- dkpapadopoulos/auto-claude-skills★ 6same name
- leek/agent-skills★ 5same name
- ilchemla/agent-skills★ 4same name
- niieani/caara★ 4same name
- diazhh/claude-expert-panel★ 1same name
- heiyuneo/claude-skills★ 1same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- clean-codeSkill
- create-design-briefSkill
- dddSkill
- goosSkill
- ingest-designSkill
- kaizenSkill
- researchSkill
- review-loopSkill
- software-designSkill
- sopSkill
- synthesizeSkill
- tddSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Must be run from main thread (reason: subagents can't spawn other subagents)
- Distinctive: line 44
If a requested panelist is unavailable (e.g.
- Very specific: line 46
Write the responses to /tmp/panel-<timestamp>-<slot>.md.
- Distinctive: line 52
Do not synthesise, reconcile, or edit.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Panel
Precondition
Must be run from main thread (reason: subagents can't spawn other subagents)
Usage
/core-skills:panel <prompt>
Prompt is mandatory — if missing, fail loudly; don't infer.
Goal
Get independent perspectives on a topic from multiple models. Default line-up: the strongest available Claude model + Codex. Callers (or project config, e.g. auto-task's bindings) may specify different panelists.
Step 1: Expand Skill References
If the prompt invokes a skill (explicit /name only — not bare names in prose/diagrams), inline its SKILL.md, clearly fenced, after the instruction. Recurse into /name invocations found inside, but inline each skill at most once — never re-expand one already present (terminates; prevents cycles and bloat).
Example: /core-skills:panel please /at:plan-task 054 but don't write to the task file.
Expanded prompt:
""" Please /at:plan-task 054 but don't write to the task file.
Skill references: === BEGIN plan-task SKILL.md === [full content of the plan-task skill's SKILL.md — resolve the skill wherever it is installed, e.g. the plugin cache under ~/.claude/plugins/cache/ or the project's .claude/skills/] === END plan-task SKILL.md === """
Step 2: Append Anti-Sycophancy Block
Append the block below to the prompt:
Answer directly and honestly. Do not hedge or soften to be agreeable. If your honest answer differs substantively from what the prompt seems to expect, give that one.
Step 3: Dispatch
Spawn one subagent per panelist in parallel and pass through the prompt — by default a Codex panelist (via codex:codex-rescue) and a Claude panelist (strongest available model).
If a requested panelist is unavailable (e.g. usage limit), fail loudly — do not substitute or skip.
Write the responses to /tmp/panel-<timestamp>-<slot>.md.
Step 4: Deliver
Present all responses verbatim, each directly attributed to its model (e.g. Codex / Claude), including the paths to the raw responses.
Do not synthesise, reconcile, or edit.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.