Configuration des agents d'avis secondaires

VérifiéSûr

Configuration interactive des agents IA pour obtenir un second avis. Suivez les étapes pour activer et configurer les agents.

Spar Skills Guide Bot
DeveloppementDébutant
1025/07/2026
Claude Code
#second-opinion#configuration#ai-agents#setup

Recommandé pour

Notre avis

Ce skill configure interactivement les agents d'IA utilisés pour les second avis dans Claude Code.

Points forts

  • Configuration interactive sans édition manuelle de fichiers
  • Détection automatique du token GitHub via gh CLI
  • Prise en charge de plusieurs fournisseurs d'IA
  • Stockage sécurisé des clés API

Limites

  • Nécessite des clés API pour la plupart des agents
  • Fonctionne uniquement dans Claude Code
  • Ne supporte pas tous les modèles d'IA
Quand l'utiliser

Utilisez ce skill lorsque vous souhaitez activer et configurer des agents d'IA externes pour des second avis dans Claude Code.

Quand l'éviter

Ne l'utilisez pas si vous ne voulez que les réponses d'un seul modèle ou si vous n'utilisez pas Claude Code.

Analyse de sécurité

Sûr
Score qualité85/100

The skill is a configuration wizard for second-opinion AI agents. It uses AskUserQuestion for input, checks files, and runs a benign shell command (`gh auth token`) for token auto-detection. It writes API keys to a local file as expected for this feature. No destructive or exfiltrating actions are instructed.

Aucun point d'attention détecté

Exemples

Setup second opinion
setup second opinion
Configure agents
configure agents for second opinions
Enable OpenAI
enable second opinion with OpenAI

name: setup description: | Configure which AI agents to use for second opinions. Use when user says "setup second opinion", "configure agents", "enable/disable agents", "which agents", or wants to change second-opinion settings.

Second Opinion Setup

Interactive configuration for second-opinion agents. The user should NEVER need to edit any files manually.

Instructions

Follow these steps exactly:

Step 1: Show Current Status

First, check if .claude/second-opinion.json exists and show current configuration:

## Current Configuration

Config file: .claude/second-opinion.json
Status: [exists | not configured]
Enabled agents: [list or "none"]

Step 2: Ask User to Select Agents

Use AskUserQuestion with multiSelect=true:

{
  "questions": [{
    "question": "Which AI agents do you want to enable for second opinions?",
    "header": "Agents",
    "multiSelect": true,
    "options": [
      {
        "label": "OpenAI (GPT-4o)",
        "description": "Requires OpenAI API key"
      },
      {
        "label": "Google Gemini",
        "description": "Requires Google AI API key"
      },
      {
        "label": "GitHub Models",
        "description": "Uses GitHub token (auto-detected from gh CLI if installed)"
      },
      {
        "label": "Anthropic (Claude)",
        "description": "Requires Anthropic API key. Note: Excluded when running in Claude Code"
      }
    ]
  }]
}

Step 3: Check for Existing Keys & Auto-Detect GitHub Token

After user selects agents, for each selected agent:

  1. For GitHub: Run gh auth token to check if a token is available

    • If available, note that it will be auto-detected (no input needed)
    • If not available, mark as needing manual input
  2. For others: Check if key already exists in .claude/second-opinion.json

    • If exists, note it's already configured
    • If missing, mark as needing input

Step 4: Prompt for Missing API Keys

For each selected agent that needs an API key, use AskUserQuestion to prompt:

{
  "questions": [{
    "question": "Please paste your OpenAI API key (starts with sk-):",
    "header": "OpenAI Key",
    "multiSelect": false,
    "options": [
      {
        "label": "Enter key now",
        "description": "Paste your API key when prompted"
      },
      {
        "label": "Skip for now",
        "description": "Configure later"
      }
    ]
  }]
}

If user selects "Enter key now", they will type in "Other" - that's the API key. If user selects "Skip for now", don't save a key for that agent.

Key format hints to tell the user:

  • OpenAI: starts with sk-
  • Anthropic: starts with sk-ant-
  • Google: alphanumeric string
  • GitHub: starts with ghp_ or gho_ (unless using gh CLI)

Step 5: Save Configuration

Map user choices to agent IDs:

  • "OpenAI (GPT-4o)" → openai
  • "Google Gemini" → gemini
  • "GitHub Models" → github
  • "Anthropic (Claude)" → anthropic

Create the .claude directory if needed, then write to .claude/second-opinion.json:

{
  "enabledAgents": ["openai", "gemini", "github"],
  "apiKeys": {
    "openai": "sk-...",
    "gemini": "AI..."
  },
  "updatedAt": "2026-01-16T12:00:00Z"
}

Important: GitHub keys are NOT stored if auto-detected from gh auth token.

Step 6: Show Confirmation

## Configuration Saved

**File:** .claude/second-opinion.json

### Enabled Agents

- openai: ✓ configured
- gemini: ✓ configured
- github: ✓ auto-detected from gh CLI

### Note

- Make sure .claude/ is in your .gitignore to protect API keys
- GitHub token is auto-detected from `gh auth token` - no key stored
- To change agents, run `/second-opinion setup` again

Important Notes

  • NEVER ask user to edit files manually
  • Use AskUserQuestion for ALL user input
  • Auto-detect GitHub token from gh auth token when possible
  • Store keys in .claude/second-opinion.json (user doesn't touch this)
  • Remind user to add .claude/ to .gitignore
  • Anthropic agent is auto-excluded when SECOND_OPINION_HOST=claude-code
Skills similaires