Skip to content
Back to skills

Setup Cobbler

ASecurity

Configure Cobbler model routes and external-agent preferences for this checkout. Use when the user types /setup-cobbler, asks to set up Cobbler model routes, onboard models, or update which tools handle planning/implement/review in Claude Code.

  • 222 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
developmentpythonbashapi

Works with

  • claude code
  • cli
  • api

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add aigorahub/elves --skill setup-cobbler --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Setup Cobbler?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Setup Cobbler
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aigorahub-setup-cobbler/badge)](https://www.skillsdirectory.com/skills/aigorahub-setup-cobbler)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: setup-cobbler
description: Configure Cobbler model routes and external-agent preferences for this checkout. Use when the user types /setup-cobbler, asks to set up Cobbler model routes, onboard models, or update which tools handle planning/implement/review in Claude Code.
disable-model-invocation: true
---

<!-- elves-managed-alias: claude-skill-alias v1 -->

# Setup Cobbler / Model Onboarding

This is an Elves-managed Claude Code alias for `/setup-cobbler`.

Run the **model onboarding** contract from the main `elves` skill and
`references/model-onboarding.md`. Operator CLI:

```bash
python3 scripts/cobbler_agents.py onboard plan|show|apply|probe [--json]
python3 scripts/cobbler_agents.py setup …   # apply-only / inventory
```

Setup must not require OpenRouter or any external provider key. Native-only Elves remains fully
usable without running setup.

## Default behavior (both Claude Code and Codex)

1. **Plan:** `onboard plan --json` — inventory tools, detect env **names** present (never values),
   emit purpose→route questions.
2. **Interview the user** for each purpose (planning, implement, review, scout, validate, synthesize,
   optional math evolutionary search). Offer **host-native first**. Respect available CLIs/keys.
3. **Apply:** `onboard apply` writes ignored `.elves/models.toml` only. Never stage it. Never paste
   API keys into TOML, chat, or the Survival Guide.
4. **Probe:** `onboard probe` runs structural checks (PATH, `--help`, env names). Optional
   `--smoke` only if the user wants a paid live check — host runs a real tiny completion; fake
   smoke does not count.
5. **Update later:** same flow (`show` → re-interview → `apply --force` → `probe`).
6. Recommend routes by capability, not prestige model names. Keep host-native fallbacks.
7. Snapshot effective routes into the Survival Guide during Elves staging for reviewable provenance.

Codex equivalent (not a top-level slash command): `$elves setup-cobbler` or natural language such as
"Set up Cobbler external-agent preferences" / "onboard my models."

Compatibility: `/setup-council` is the same setup contract with a Council-era name.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…