agentsclimarketplace

Llm council

Skill webdevtodayjason/dev-kit/plugins/dev-kit/skills/llm-council

Multi-LLM collaborative brainstorming and planning. Use when user explicitly requests consultation with multiple AI models (ChatGPT, Gemini, other LLMs) before presenting an implementation plan, or asks to "consult the council", "ask other models", or "get perspectives from other AIs". Queries external LLM APIs, synthesizes their perspectives, and presents an adapted implementation plan.From its SKILL.md

Install
npx -y skills add webdevtodayjason/dev-kit --skill llm-council

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.1 KB, 907 tokens by cl100k_base, as published. Nobody here has run it

LLM Council

Consult multiple AI models (ChatGPT and Gemini) for their perspectives before presenting implementation plans to users.

Workflow

When user requests consultation with other AI models, use phrases like:

  • "Consult with ChatGPT and Gemini about..."
  • "Ask other AI models what they think about..."
  • "Get perspectives from the council on..."
  • "Consult the LLM council: [your question]"

Process:

  1. Query external LLMs: Run scripts/query_llms.py with the user's prompt to get perspectives from both ChatGPT and Gemini
  2. Analyze responses: Review what each model suggests, identifying valuable insights, alternative approaches, and potential concerns
  3. Synthesize plan: Create an implementation plan that incorporates the best ideas from all three models (Claude's own analysis + ChatGPT + Gemini)
  4. Present to user: Show the final plan along with a brief summary of key contributions from each model

Setup Requirements

The skill requires API keys and optional model configuration stored in a .env file in the working directory:

OPENAI_API_KEY=sk-...
GEMINI_API_KEY=...

# Optional: Specify which models to use (defaults shown below)
OPENAI_MODEL=gpt-5-nano
GEMINI_MODEL=gemini-3-flash-preview

Default Models:

  • ChatGPT: gpt-5-nano (fastest, most cost-efficient - $0.05/1M input, $0.40/1M output)
  • Gemini: gemini-3-flash-preview (balanced speed and intelligence)

Upgrade Options for Better Collaboration:

OpenAI models (ordered by capability and cost):

  • gpt-5-nano - Fastest, most cost-efficient ($0.05/1M in, $0.40/1M out) - DEFAULT
  • gpt-5-mini - Faster, cost-efficient for well-defined tasks ($0.25/1M in, $2.00/1M out)
  • gpt-5.2 - Best for coding and agentic tasks ($1.75/1M in, $14.00/1M out)
  • gpt-5.2-pro - Smarter, more precise for complex problems ($21.00/1M in, $168.00/1M out)

All models support reasoning tokens, 400K context window, and image input.

Gemini models (ordered by capability):

  • gemini-2.5-flash-lite - Ultra-fast, optimized for throughput
  • gemini-2.5-flash - Best price-performance, large-scale processing
  • gemini-3-flash-preview - Balanced speed and frontier intelligence (default)
  • gemini-3-pro-preview - Most intelligent multimodal model, best for complex reasoning

Higher-tier models provide more sophisticated analysis but cost more per API call.

If the .env file doesn't exist or keys are missing, inform the user and provide setup instructions.

Usage Example

User input: "Consult the council: How should I architect a real-time data pipeline for IoT sensors?"

Claude's process:

  1. Execute: python3 scripts/query_llms.py "How should I architect a real-time data pipeline for IoT sensors?"
  2. Parse JSON responses from ChatGPT and Gemini
  3. Analyze their suggestions (e.g., ChatGPT suggests Kafka, Gemini recommends considering edge computing)
  4. Synthesize final plan incorporating valuable insights from all models
  5. Present the adapted plan to user with attribution

Output Format

Present the final implementation plan naturally, mentioning key insights from other models inline where relevant. For example:

"Based on consultation with ChatGPT and Gemini, here's the recommended architecture:

[Implementation plan with inline references like "ChatGPT highlighted the importance of..." or "Gemini suggested..."]

Key contributions:

  • ChatGPT: [brief summary]
  • Gemini: [brief summary]"

Error Handling

  • If API keys are missing, inform user and provide setup instructions
  • If an API call fails, note which model's perspective is unavailable and proceed with available responses
  • If both APIs fail, inform user and offer to provide Claude's own analysis without external consultation

What ships with it: 3 files

10.9 KB alongside SKILL.md, 1 of them executable

references/

scripts/

Gives 0 of the 12 instructions most context ai engineering skills give in 907 tokens

Counted across 1,193 of the 1,976 authors here whose files we hold, read 2026-08-07

  • Dispatch a fresh implementer subagent per taskin 48 of 1193, across 19 files
  • Dispatch a final code reviewer after all tasksin 33 of 1193, across 8 files
  • Provide full task text to the subagentin 30 of 1193, across 9 files
  • Review spec compliance before code qualityin 27 of 1193, across 10 files
  • Make the hook script executablein 26 of 1193, across 8 files
  • Re-snapshot after navigation or DOM changesin 25 of 1193, across 19 files
  • Read files before editing themin 22 of 1193, across 11 files
  • Answer subagent questions before proceedingin 22 of 1193, across 7 files
  • Mark task complete in TodoWrite after approvalin 22 of 1193, across 6 files
  • Merge hook into existing settingsin 21 of 1193, across 3 files
  • Ask if installation is global or projectin 20 of 1193, across 2 files
  • Copy the hook script to target locationin 20 of 1193, across 2 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,750. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.