Skip to content

DOC

Diagnostiquer CLI et Skills avec Tools-Checker

Vérifier l'état des outils installés (CLI, Skills ulk, MCP) et générer un rapport d'environnement

Diagnostiquer CLI et Skills avec Tools-Checker

Contexte

Avant de lancer un agent ulk qui dépend de CLI spécifiques (GitHub, Vercel, Neon, etc.) ou Skills (Figma, Swift, Flutter), vous voulez vérifier que tout est installé et à jour. Tools-Checker scanne tools/cli-registry.json, teste chaque outil, et retourne un rapport clair ✅/❌.

Prérequis

  • Machine avec les CLI/Skills optionnels/recommandés installés
  • Accès Read à tools/cli-registry.json
  • Ligne de commande disponible

Étapes

1. Invocation diagnose

Lancez Tools-Checker :

/ulk:tools-checker

ou

check tools

ou

quels cli sont installés

Tools-Checker démarre Phase 1 (Lecture du registre).

2. Phase 1 — Lecture du registre

Agent lit tools/cli-registry.json :

cat tools/cli-registry.json

Structure du registre :

{
  "tools": [
    {
      "name": "gh",
      "command": "gh --version",
      "priority": "recommended",
      "description": "GitHub CLI"
    },
    {
      "name": "vercel",
      "command": "vercel --version",
      "priority": "recommended",
      "description": "Vercel deployment"
    },
    {
      "name": "neonctl",
      "command": "neonctl --version",
      "priority": "optional",
      "description": "Neon database CLI"
    },
    ...
  ]
}

3. Phase 2 — Test chaque CLI

Pour chaque entrée du registre avec priority != "mcp-only" :

# Test chaque outil
gh --version 2>/dev/null && echo "OK" || echo "MISSING"
vercel --version 2>/dev/null && echo "OK" || echo "MISSING"
neonctl --version 2>/dev/null && echo "OK" || echo "MISSING"

Récupérer :

  • Version installée (si OK)
  • Installation command (si MISSING)
  • Outdated status (si détectable)

4. Phase 3 — Vérifier Skills ulk

Lister les Skills installés :

ls ~/.claude/skills/ulk-*/SKILL.md 2>/dev/null | sed 's|.*/ulk-||;s|/SKILL.md||'

Comparer avec le registre des Skills ulk :

ulk-github
ulk-deploy-vercel
ulk-database-neon
...

5. Phase 4 — Rapport structuré

Format de sortie complet :

=== CLI & Skills Diagnostics ===

CLI TOOLS (Recommended - core)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  ✅ gh              2.88.1
     Usage: Push to GitHub, manage PRs
  
  ✅ npm             10.7.0
     Usage: Install dependencies, run scripts
  
  ⚠️ vercel          50.28.0  [OUTDATED → npm i -g vercel@latest]
     Usage: Deploy to Vercel
  
  ❌ neonctl         [MISSING]
     Usage: Manage Neon database
     Install: npm install -g neonctl && neonctl auth

CLI TOOLS (Optional)
━━━━━━━━━━━━━━━━━━━━
  ✅ pnpm            8.15.6
     Usage: Fast package manager
  
  ✅ pandoc          3.9.0.2
     Usage: Document conversion

  ❌ pgcli           [MISSING]
     Usage: PostgreSQL client
     Install: brew install pgcli
  
  ❌ docker          [MISSING]
     Usage: Container management
     Install: brew install --cask docker

MCP ONLY (No CLI needed)
━━━━━━━━━━━━━━━━━━━━
  — figma            MCP required (design tokens)
  — linear           MCP required (issue tracking)
  — notion           MCP required (documentation)

SKILLS (ulk bundled)
━━━━━━━━━━━━━━━━━━
  ✅ ulk-github                    ~/.claude/skills/ulk-github/
  ✅ ulk-deploy-vercel             ~/.claude/skills/ulk-deploy-vercel/
  ❌ ulk-database-neon             [MISSING]
  ❌ ulk-mobile-ios                [MISSING]
  ✅ figma-implement-design        ~/.claude/skills/figma-implement-design/
  ✅ swift-concurrency-pro         ~/.claude/skills/swift-concurrency-pro/
  ✅ flutter-tester                ~/.claude/skills/flutter-tester/

═══════════════════════════════════════════════════════════════

SUMMARY
━━━━━━━━━━━━
CLI (Recommended)     : 2/3 installed (66%)  🟡
CLI (Optional)        : 2/6 installed (33%)  🟡
Skills                : 5/8 installed (62%)  🟡

Environment Score     : 6/10

Missing Recommended   : neonctl
Missing Optional      : pgcli, docker, ranger
Missing Skills        : ulk-database-neon, ulk-mobile-ios

6. Recommandations groupées

Proposer actions prioritaires :

=== ACTION ITEMS ===

BLOCKING (agents won't work)
  None — all recommended tools present

REQUIRED FOR SPECIFIC WORKFLOWS
  [ ] neonctl     → npm i -g neonctl && neonctl auth
      Needed if: Using Neon PostgreSQL

RECOMMENDED (improve experience)
  [ ] docker      → brew install --cask docker
      Benefit: Local testing, reproducible builds

  [ ] pgcli       → brew install pgcli
      Benefit: PostgreSQL terminal client

OPTIONAL (nice-to-have)
  [ ] ulk-database-neon    → ./install.sh --with-database-neon
  [ ] ulk-mobile-ios       → ./install.sh --with-mobile-ios

═══════════════════════════════════════════════════════════════

NEXT STEPS
  1. Install neonctl if using Neon
  2. Run: ./install.sh --with-[missing-skill] to add Skills
  3. Recheck: /ulk:tools-checker (verify installation)

7. Mode compact (pour sub-agents)

Si invoqué avec mode: compact, retourner seulement :

{
  "cli_score": 6,
  "missing_recommended": ["neonctl"],
  "missing_optional": ["pgcli", "docker", "ranger"],
  "skills_ok": 5,
  "skills_total": 8,
  "ready_for_deploy": true,
  "ready_for_mobile": false
}

8. Diagnostic approfondi (optionnel)

Pour chaque CLI trouvé, proposer test supplémentaire :

# Test complet pour gh
gh auth status                    # Vérifier auth
gh repo list --limit 1            # Tester accès API

# Test complet pour vercel
vercel whoami                     # Vérifier auth
vercel projects                   # Lister projets

# Test complet pour npm
npm whoami                        # Vérifier auth
npm config get registry           # Vérifier registre

Rapport détaillé :

=== DETAILED CLI CHECKS ===

GitHub CLI (gh)
  ✅ Command available
  ✅ Version: 2.88.1
  ✅ Authenticated (user: johndoe)
  ✅ API accessible
  Status: READY FOR USE

Vercel CLI (vercel)
  ✅ Command available
  ⚠️ Version: 50.28.0 (latest: 50.30.0)
  ✅ Authenticated
  ✅ 3 projects accessible
  Status: READY (recommend update)

npm
  ✅ Command available
  ✅ Version: 10.7.0
  ✅ Authenticated (npm account)
  ✅ Registry: https://registry.npmjs.org/
  Status: READY FOR USE

Variantes

  • Variante A — Quick check : Juste CLI status (pas de détail)
  • Variante B — Full diagnostic : Test approfondi, auth verification
  • Variante C — Setup guide : Proposer commandes install manquantes
  • Variante D — Scheduled check : /schedule tools-checker --cron "0 9 * * 1" (weekly)

Agents enchaînés

Flux typique : godspeed (00) start → tools-checker (43) diagnose → bruce (25) orchestrate.

Troubleshooting

SymptômeCause probableRésolution
Tous CLI manquantsPATH not setVérifier $PATH, réinstaller
Faux positif “MISSING”Version output différenteAjouter pattern dans registry
Auth failedToken expiréRe-login : gh auth login, vercel login
Skills not found~/.claude/skills absentRelancer ./install.sh

Voir aussi

  • agents/audit/43-tools-checker.md — agent complet
  • tools/cli-registry.json — complete registry
  • ./install.sh --check — equivalent command
  • agents/orchestrators/00-godspeed.md — startup diagnostic