multi-llm-advisor
Fetches additional perspectives from OpenAI Codex and Google Gemini for architecture, review, and debugging. Transparently displays all LLM calls.
What this skill does
# Multi-LLM Advisor
This skill calls Codex 5.1 Pro and Gemini 3 Pro to provide additional perspectives.
## When to Activate
- Architecture decisions (new features, refactoring)
- Code review (before commits, PRs)
- Debugging (complex errors, performance issues)
- On explicit request ("second opinion", "different perspective")
## Usage
```
Use the multi-llm-advisor skill to get architecture feedback on [topic]
Use the multi-llm-advisor skill to review this code
Use the multi-llm-advisor skill to debug [issue]
```
## Transparency Format
Every invocation displays the following:
```
+==============================================================+
| MULTI-LLM ADVISOR - [MODE: ARCHITECTURE|REVIEW|DEBUG] |
+==============================================================+
| CONTEXT SENT TO LLMs: |
| - Files: [list] |
| - Question: [prompt] |
| - Tokens: ~[count] |
+--------------------------------------------------------------+
| CODEX 5.1 PRO RESPONSE: |
| [response] |
+--------------------------------------------------------------+
| GEMINI 3 PRO RESPONSE: |
| [response] |
+--------------------------------------------------------------+
| SYNTHESIS (Claude's Recommendation): |
| [combined analysis] |
+==============================================================+
```
## Prompt Templates
### Architecture Mode
```
You are a senior software architect. Analyze this architecture decision:
CONTEXT:
{context}
QUESTION:
{question}
CURRENT STACK:
{stack}
Provide:
1. Pros/Cons of the proposed approach
2. Alternative approaches (max 2)
3. Potential risks and mitigations
4. Recommendation with reasoning
Be concise. Max 300 words.
```
### Review Mode
```
You are a senior code reviewer. Review this code:
CODE:
{code}
LANGUAGE: {language}
PROJECT TYPE: {project_type}
Focus on:
1. Security vulnerabilities (OWASP Top 10)
2. Performance issues
3. Maintainability concerns
4. TypeScript/type safety (if applicable)
Format: Bullet points, max 200 words.
```
### Debug Mode
```
You are a debugging expert. Analyze this issue:
ERROR/SYMPTOM:
{error}
RELEVANT CODE:
{code}
CONTEXT:
{context}
Provide:
1. Root cause analysis (most likely)
2. 2-3 diagnostic steps
3. Suggested fix with code
Be specific and actionable. Max 250 words.
```
## API Configuration
Environment variables (store in `.env` or system env):
- `OPENAI_API_KEY` - For Codex 5.1 Pro
- `GOOGLE_AI_API_KEY` - For Gemini 3 Pro (same as gemini-image-gen)
## Script Location
`~/.claude/skills/multi-llm-advisor/advisor.ts`
## Hook Integration
Triggered via `multi-llm-advisor-hook.ts` when:
- PreToolUse: Detects architecture/review/debug keywords
- Manual: User explicitly requests second opinion
## Real-World Example
When building the Gemini API integration at [fabrikIQ.com](https://www.fabrikiq.com), this skill helped decide between:
- Vertex AI (enterprise, EU region support) vs Google AI Studio (simpler)
- Streaming vs batch responses for large manufacturing datasets
- The synthesis recommended Vertex AI for GDPR compliance, which proved correct.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.