Cn 8d Report
mohitagw15856/pm-claude-skills
A skill your agent uses when asked 写8D报告, 客户投诉8D, 质量问题8D, 客诉回复报告, 8D 怎么写, 根本原因分析报告, or write an 8D problem-solving report for a customer complaint or internal quality issue in a Chinese factory.
Convenes expert panels for problem-solving. An agent skill from oaustegard/claude-skills.
Install Convening Experts
$ npx skills add oaustegard/claude-skills --skill convening-experts -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install oaustegard/claude-skills convening-experts --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/oaustegard/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/convening-experts .claude/skills/convening-experts && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "convening-experts" agent skill from https://github.com/oaustegard/claude-skills/tree/main/convening-experts into .claude/skills/convening-experts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "convening-experts", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/oaustegard/claude-skills/tree/main/convening-expertsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add oaustegard/claude-skills --skill convening-experts -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install oaustegard/claude-skills convening-experts --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oaustegard/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/convening-experts .agents/skills/convening-experts && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "convening-experts" agent skill from https://github.com/oaustegard/claude-skills/tree/main/convening-experts into .agents/skills/convening-experts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "convening-experts", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add oaustegard/claude-skills --skill convening-experts -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install oaustegard/claude-skills convening-experts --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oaustegard/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/convening-experts .cursor/skills/convening-experts && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "convening-experts" agent skill from https://github.com/oaustegard/claude-skills/tree/main/convening-experts into .cursor/skills/convening-experts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "convening-experts", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/oaustegard/claude-skills.git --path convening-experts--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add oaustegard/claude-skills --skill convening-experts -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install oaustegard/claude-skills convening-experts --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oaustegard/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/convening-experts .gemini/skills/convening-experts && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "convening-experts" agent skill from https://github.com/oaustegard/claude-skills/tree/main/convening-experts into .gemini/skills/convening-experts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "convening-experts", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install oaustegard/claude-skills convening-expertsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add oaustegard/claude-skills --skill convening-experts -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/oaustegard/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/convening-experts .github/skills/convening-experts && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "convening-experts" agent skill from https://github.com/oaustegard/claude-skills/tree/main/convening-experts into .github/skills/convening-experts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "convening-experts", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add oaustegard/claude-skills --skill convening-experts -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install oaustegard/claude-skills convening-experts --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oaustegard/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/convening-experts .opencode/skills/convening-experts && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "convening-experts" agent skill from https://github.com/oaustegard/claude-skills/tree/main/convening-experts into .opencode/skills/convening-experts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "convening-experts", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
convening-experts- GitHub stars
- 150
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,001 words
- Files
- 9 (incl. references)
- Skills in repo
- 67
- Repo updated
- First seen
- Licence
- MIT
At a glance
Convenes expert panels for problem-solving. An agent skill from oaustegard/claude-skills.
- Works in 3 steps: Assemble panel (3-5 experts based on… → Each expert provides independent… → Synthesize recommendations with…
- User mentions panel
- SKILL.md covers SURFACE ROUTING — read first, Panel Format, Expert Roles and Panel Convening Logic, plus 6 more sections
- Calls claude
What it does
Convening Experts is an agent skill from oaustegard/claude-skills. Convenes expert panels for problem-solving. Use when user mentions panel, experts, multiple perspectives, MECE, DMAIC, RAPID, Six Sigma, root cause analysis, strategic decisions, process improvement, or asks for philosophers/ancients (Socratic, Aristotelian, Stoic method experts).
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `CHANGELOG.md`, `README.md` and `examples/process-improvement-example.md`).
It sits in Development, covering Root cause analysis, Operations and SOPs and Tutoring and explanations. The repository describes itself as: My collection of Claude skills. The licence is MIT.
When your agent uses it
- User mentions panel
- Multiple perspectives
- Root cause analysis
- Strategic decisions
Example prompts
- “Use the convening-experts skill to convene expert panels for problem-solving. An agent skill from oaustegard/claude-skills”
- “/convening-experts”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Assemble panel (3-5 experts based on problem domain)
- Each expert provides independent perspective (parallel, not sequential)
- Synthesize recommendations with attribution
What it can do on your machine
Read from SKILL.md and the folder at commit 90b0f1b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
claude
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Convening Experts loads about 2.4k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 1,001 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from oaustegard/claude-skills at commit 90b0f1b, republished under its MIT licence (© oaustegard). 1,001 words, ~2,412 tokens.
Download SKILL.mdSave it as
.claude/skills/convening-experts/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- convening-experts
- description
- Convenes expert panels for problem-solving. Use when user mentions panel, experts, multiple perspectives, MECE, DMAIC, RAPID, Six Sigma, root cause analysis, strategic decisions, process improvement, or asks for philosophers/ancients (Socratic, Aristotelian, Stoic method experts).
- metadata.version
- 1.2.0
SURFACE ROUTING — read first
This skill hand-rolls subagent orchestration via raw Anthropic API calls. A managed runtime now does the same job. Which one to use depends on your surface:
- In Claude Code (incl. CCotw): use the native runtime, NOT this skill. If you
can invoke
/deep-research, trigger a run with theworkflowkeyword, set/effort ultracode, or spawn Task subagents — do that instead. The runtime gives 16-concurrent / 1000-agent ceilings, an approval gate, adversarial cross-review, and in-session resume that this skill would otherwise reimplement badly. Dynamic workflows shipped in research preview (Claude Code v2.1.154+, 2026). - In claude.ai chat or the bare API (no workflow runtime): use this skill.
Parallel API instances over httpx is the only fan-out path here.
muninn_utils.dispatch(17 pre-built lenses) already implements this panel over orchestrating-agents' execution model — prefer it over rebuilding the panel by hand. Proceed below.
Discriminator: do you have a native subagent/Task tool or a workflow command? Yes → native. No → this skill. Never reimplement the runtime where it already exists.
Convening Experts
Convene domain experts and methodological specialists to solve problems through multi-round collaborative discussion. Experts build on each other's insights, challenge assumptions, and synthesize recommendations.
Panel Format
Single-Round Consultation
For simpler problems requiring multiple viewpoints:
- Assemble panel (3-5 experts based on problem domain)
- Each expert provides independent perspective (parallel, not sequential)
- Synthesize recommendations with attribution
Multi-Round Discussion
For complex problems requiring collaborative reasoning:
- Round 1: Each expert analyzes problem independently
- Round 2: Experts respond to each other's insights, building on or challenging points
- Round 3 (if needed): Converge on synthesis, resolve disagreements
- Final synthesis: Integrated recommendations with decision framework
Expert Roles
Available expertise spans:
- MSD domain experts (life sciences, engineering, manufacturing, quality, corporate functions)
- Consulting framework specialists (strategic, process improvement, innovation, systems analysis, root cause)
- Ancient philosopher method experts (elenchus, division-before-judgment, dichotomy of control, power analysis)
See references/msd-domain-experts.md, references/consulting-frameworks.md, and references/ancient-philosophers.md for complete role catalogs.
Claude loads relevant references based on problem domain.
Panel Convening Logic
Claude selects 3-5 experts based on problem characteristics:
Problem type → Primary expert + Supporting experts
- Technical troubleshooting → Domain expert + Systems Thinker + Five Whys Facilitator
- Strategic decision → McKinsey Consultant + relevant domain experts + SWOT Analyst
- Process improvement → Six Sigma Black Belt + Lean Practitioner + domain Manufacturing Engineer
- Product innovation → Design Thinking Facilitator + Jobs-to-Be-Done Specialist + relevant engineers
- Root cause analysis → Domain expert + Five Whys Facilitator + Systems Thinker
- Market positioning → Porter Framework Expert + Marketing Specialist + BCG Consultant
- Cross-functional problem → Relevant domain experts + Bain Consultant (RAPID) + Systems Thinker
- Definitional / conceptual dispute → Socratic Examiner + Aristotelian Taxonomist + domain expert
- Governance / institutional design → Aristotelian Taxonomist + Thucydidean Realist + Systems Thinker
- Ideal-vs-pragmatic tension → Platonic Idealist + Aristotelian Taxonomist (native adversarial pair, per Politics IV Part II) + domain expert
Response Format
Name the panel up front, then give each expert's view before synthesizing.
Single-round: list the panel members, then each expert's independent analysis (in any clear order — parallel, not sequential), then a synthesis with attribution.
Multi-round: initial analysis from each expert, then a round where experts respond to specific points from named others (building on or challenging them), then convergence — resolving disagreements or flagging which remain productive — and a final synthesis. Skip rounds that would add nothing (e.g. no round 3 if round 2 already converged).
Headers separating experts and rounds help the reader; the exact heading text doesn't matter.
Show full SKILL.md (455 more words)Show less
Expert Behavior Guidelines
Domain Experts:
- Apply MSD context (ECL platform, regulatory constraints, validated systems)
- Use domain-appropriate terminology without over-explanation
- Prioritize practical implementation over theoretical perfection
- Flag domain-specific risks and constraints
Philosopher Experts:
- Apply the named method (elenchus, division, dichotomy of control), showing its structure — method, not costume; no period voice
- Persona-only by default; corpus-injected grounding (verbatim source text + cite-every-claim) when output must be auditable or turns on a work's fine structure — mechanics and routing table in references/ancient-philosophers.md
- Mix with domain experts — an all-philosopher panel answers modern questions at the wrong altitude unless the question itself is conceptual
Framework Experts:
- Apply frameworks systematically (show the structure)
- Adapt frameworks to problem context (not rigid application)
- Explain "why this framework" for this problem
- Integrate domain context when applying generic frameworks
Cross-Panel Interaction:
- Reference other experts' points specifically ("Building on [Expert]'s observation about...")
- Challenge constructively ("I see it differently because...")
- Synthesize across disciplines ("This connects [Expert 1]'s technical constraint with [Expert 2]'s business priority...")
- Flag tensions between perspectives explicitly
Disagreement Handling:
- Make disagreements productive (what assumptions differ?)
- Present multiple valid approaches when consensus isn't required
- Identify decision criteria to resolve disagreements
- Escalate to user if expert consensus can't be reached
Decision Frameworks
When panel must recommend action:
RAPID (Bain)
- Recommend: Panel's recommendation with rationale
- Agree: Which stakeholders must agree
- Perform: Who implements
- Input: Who provides input
- Decide: Who makes final decision
Weighted Decision Matrix
- Criteria (importance weighted)
- Options scored on each criterion
- Total score with sensitivity analysis
Risk-Benefit Analysis
- Upside potential (probability × impact)
- Downside risk (probability × impact)
- Mitigation strategies
- Decision under uncertainty
MSD Integration
Apply MSD-specific context automatically:
Technical constraints:
- ECL platform and assay chemistry
- ISO 13485 compliance and validated systems
- Regulatory requirements (FDA, CE marking)
- Technology stack (Python, AWS, Java, TypeScript)
Business context:
- Life sciences market dynamics
- Customer segments (pharma, biotech, CRO, academic)
- Competitive landscape
Cultural factors:
- Scientific rigor and data-driven decisions
- Cross-functional collaboration norms
- Innovation balanced with risk management
- Quality and regulatory consciousness
Examples
Example 1: Technical Troubleshooting
User: Our new assay is showing high background signal in serum samples
Claude convenes:
- Assay Scientist (primary)
- Systems Thinker (feedback loops)
- Five Whys Facilitator (root cause)
Format: Multi-round (technical nuance requires collaboration)Example 2: Strategic Decision
User: Should we build internal ML infrastructure or use vendor solutions?
Claude convenes:
- Software Engineer (implementation)
- McKinsey Consultant (strategic framing)
- Finance Analyst (cost analysis)
- DevOps Engineer (operational implications)
Format: Single-round → RAPID framework synthesisExample 3: Process Improvement
User: Manufacturing yield dropped 8% after equipment upgrade
Claude convenes:
- Manufacturing Engineer (primary domain)
- Six Sigma Black Belt (DMAIC)
- Systems Thinker (unintended consequences)
Format: Multi-round (root cause needs collaborative analysis)Constraints
Skip the panel entirely when the problem has one clearly correct answer — give a direct answer instead of manufacturing perspectives around it.
Four constraints have no other source of truth in this document, so they stay explicit. Don't invent fictional names for experts (role titles only — "Software Engineer", not "Dr. John Smith, Software Engineer"), and don't invent MSD-specific details beyond general domain knowledge; both would misrepresent a generic panel as grounded in specifics it doesn't have.
The other two are failure modes the panel format itself invites: manufacturing consensus where the experts genuinely disagree (flag the disagreement and say what would settle it), and ending on "here are the perspectives, you decide" instead of a synthesis someone can act on.
© oaustegard, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 8 other files (references) in convening-experts of oaustegard/claude-skills.
- SKILL.md
- CHANGELOG.md
- README.md
- examples/process-improvement-example.md
- examples/strategic-decision-example.md
- examples/technical-troubleshooting-example.md
- references/ancient-philosophers.md
- references/consulting-frameworks.md
- references/msd-domain-experts.md
Open the folder on GitHubat commit 90b0f1b
Compare with similar skills
Convening Experts next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Convening Experts this skilloaustegard/claude-skills | 150 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Cn 8d Reportmohitagw15856/pm-claude-skills | 1.4k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Deployment Rollback InterviewerPrepLabsAI/InterviewMentor | 112 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 11k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| OpenLogi macOS Permissions TriageAprilNEA/OpenLogi | 23k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Bug Finder for daisyUIsaadeghi/daisyui | 43k | — | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
Deployment Rollback Interviewer
PrepLabsAI/InterviewMentor
A release engineer interviewer managing a failed deployment with spiking error rates.
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
Bug Finder for daisyUI
saadeghi/daisyui
Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.
Root Cause Debugging
garrytan/gstack
Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.
More from oaustegard/claude-skills
All 67 skills in this repoVega-Lite Interactive Charts
oaustegard/claude-skills
Builds interactive Vega-Lite charts from uploaded data: analyzes the fields, picks five to ten fitting chart types, and produces a React artifact with the data embedded inline.
Single-File HTML Composer
oaustegard/claude-skills
Builds self-contained single-file HTML pages such as reports, decks, postmortems, flowcharts and prototypes from a small spec using a bundled Python composer and templates.
Deciding With Confidence
oaustegard/claude-skills
Routes, triages, flags and rates a piece of text with a probability for every option: which department or queue a ticket goes to, which intent a message expresses, whether a yes/no condition holds…
Declauding
oaustegard/claude-skills
Rewrites model-sounding prose into plain technical writing and checks that every claim survives, for PR text, docs, commit messages and similar drafts.
Preact Developer
oaustegard/claude-skills
Guides building standards-based Preact apps with native-first choices, HTM syntax, import maps and vendored ESM, from single-file demos to larger builds.
Bluesky Zeitgeist Sampler
oaustegard/claude-skills
Deprecated sampler that captures short windows of the Bluesky firehose, clusters trending terms and builds an HTML report; replaced by the browsing-bluesky skill.
Related
Categories
Questions about Convening Experts
What does Convening Experts do?
Convenes expert panels for problem-solving. An agent skill from oaustegard/claude-skills. Convening Experts is an agent skill from oaustegard/claude-skills. Convenes expert panels for problem-solving.
When should I use Convening Experts?
Convening Experts fits situations like: user mentions panel; multiple perspectives; root cause analysis; strategic decisions.
How do I install Convening Experts in Claude Code?
Run `npx skills add oaustegard/claude-skills --skill convening-experts -a claude-code`. Or copy the skill folder (convening-experts in oaustegard/claude-skills) into .claude/skills/convening-experts in your project. Claude Code loads it when a task matches its description.
How do I install Convening Experts in Codex?
Run `npx skills add oaustegard/claude-skills --skill convening-experts -a codex`. Or copy the skill folder (convening-experts in oaustegard/claude-skills) into .agents/skills/convening-experts in your project. Codex loads it when a task matches its description.
Can I use Convening Experts in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add oaustegard/claude-skills --skill convening-experts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/convening-experts, .gemini/skills/convening-experts, .github/skills/convening-experts and .opencode/skills/convening-experts in your project.
What does Convening Experts need to run?
Going by SKILL.md and its folder, Convening Experts needs the command-line tools its instructions call (claude).
Does Convening Experts access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Convening Experts safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Convening Experts use?
Convening Experts is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Convening Experts use?
About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.5k tokens, read only when the agent opens those files.
What are the alternatives to Convening Experts?
Skills that share tags, products or a category with Convening Experts: Cn 8d Report (mohitagw15856/pm-claude-skills, 1.4k stars), Deployment Rollback Interviewer (PrepLabsAI/InterviewMentor, 112 stars), Code Design Rationale Investigator (cursor/plugins, 11k stars) and OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Convening Experts?
oaustegard (a GitHub user) maintains it in oaustegard/claude-skills, which has 150 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on October 9, 2026.
Source: oaustegard/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.