Skip to content
cccskills
FreePublished on GitHub

ouroboros-config

Manage Ouroboros settings through a browser interface or chat commands. Choose agents and models globally or for individual stages, change the LLM backend, review saved settings, and restore the configuration from before the last change.

OriginalShow the original description

Open or drive the Ouroboros settings GUI (browser, TUI, or conversational fallback)

See how to install

Good for

  • Changing the default agent and model
  • Assigning different agents to individual stages
  • Editing settings on a remote host
  • Reviewing or undoing the last configuration change

Files included (1)

  • SKILL.md3.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

/ouroboros:ouroboros-config

Edit ~/.ouroboros/config.yaml: global and per-stage runtime and model choices, the LLM backend, install badges for missing CLIs, and env-override warnings.

ooo config
/ouroboros:ouroboros-config

Instructions

Pick the branch by one question: can the user open a browser pointed at this machine? Run commands with the active runtime's run_shell capability.

Branch A: local harness on the user's own machine

  1. Launch in the background (it serves until stopped):

    if command -v ouroboros >/dev/null 2>&1; then
      ouroboros config
    else
      uvx --python '>=3.12' --from 'ouroboros-ai[tui]' ouroboros config
    fi
    

    In a non-interactive context it serves the settings app on a local web server and opens the browser. The uvx fallback covers a plugin-only install where ouroboros is not on PATH; in a development checkout use uv run ouroboros config.

  2. Relay the http://localhost:<port> line in case the browser did not open.

  3. Tell the user: edit, Save, then ask you to stop the server. A running MCP server may need a reconnect to pick up backend changes. ooo config reopens the settings any time; a saved model choice is never locked.

Branch B: remote host the user can reach (SSH box, home server)

ouroboros config --web --host 0.0.0.0 --no-browser

Relay the printed URL with this host's address substituted, plus the SSH tunnel fallback it prints (ssh -L <port>:localhost:<port> <this-host>).

Branch C: chat gateway with no browser path (e.g. hermes driven from Discord)

Do not start a server nobody can reach. Drive the same settings in chat:

  1. Show the current state with ouroboros config show.

  2. Offer a short menu with current values (default agent, per-stage agents, and models: auto, a tier, or a model id for every role) and ask what to change.

  3. Apply each choice with the validated setter (same write path as the GUI):

    ouroboros config set orchestrator.runtime_backend <agent>
    ouroboros config set orchestrator.runtime_profile.stages.<interview|execute|evaluate|reflect> <agent>
    ouroboros config set models.default <auto|frugal|standard|frontier|model>  # every role
    ouroboros config set models.pin true                            # run the per-role ids below
    ouroboros config set clarification.default_model <model>        # interview & seed
    ouroboros config set execution.default_model <model>            # execute
    ouroboros config set evaluation.semantic_model <model>          # evaluate
    ouroboros config set resilience.reflect_model <model>           # reflect
    ouroboros config set llm.backend <backend>                      # internal LLM calls
    
  4. Confirm with ouroboros config show and summarize what changed.

All branches

Relay any rejected set validation error or missing-dependency hint (pip install 'ouroboros-ai[tui]') verbatim. ouroboros config undo restores the configuration saved before the last change.

RFC #1392 State Breadcrumb Footer

End the final response with exactly one line ◆ <current state> → next: <recommended action>. Derive the state from live session state via ouroboros_session_status when available, otherwise from this skill's actual outcome. Never use a linear Step N of M footer; when the next step is a real choice, list 2-3 options.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

auto

FreeSummary

Turn a multi-file development task or technology migration into a specification with acceptance criteria, then launch background implementation and verification. The workflow clarifies missing requirements, reviews the specification, and tracks progress and blockers through linked jobs.

  • Implementing a feature across multiple files
  • Migrating a framework or programming language
  • Replacing authentication, storage, or API layers
Q00/ouroboros6.2KUpdated Oct 19, 2026

brownfield

FreeSummary

Register and search existing Git repositories and worktrees, then choose which projects Ouroboros interviews use as context. You can also generate a configuration containing verified build, test, and other check commands for the evaluation workflow.

  • Selecting existing projects as interview context
  • Finding registered repositories by topic
  • Rescanning after repositories are added or moved
Q00/ouroboros6.2KUpdated Oct 19, 2026

cancel

FreeSummary

Stop stuck Ouroboros executions or background jobs by ID, or cancel all running and paused executions in the current project. It reports whether cancellation is complete or has been requested, with guidance for checking the final status.

  • Stopping a stuck execution
  • Cancelling a background job by ID
  • Cancelling all active executions in a project
Q00/ouroboros6.2KUpdated Oct 19, 2026

evaluate

FreeSummary

Verify finished work against acceptance criteria using executable checks and a review of whether each requirement is met. Multiple models can review uncertain cases, and rejected work can enter an automated repair loop when the required Seed is available.

  • Checking finished work against its specification
  • Verifying observed behavior against acceptance criteria
  • Requesting multiple model reviews for uncertain results
Q00/ouroboros6.2KUpdated Oct 19, 2026

evolve

FreeSummary

Start and monitor an Ouroboros development loop that revises project concepts and acceptance criteria, the conditions for judging completion. Run and evaluate successive generations, focus revisions on failed criteria, inspect progress, or rewind to an earlier generation.

  • Refining a project through repeated execution and evaluation
  • Inspecting progress across generations
  • Rewinding a development loop to an earlier generation
Q00/ouroboros6.2KUpdated Oct 19, 2026

interview

FreeSummary

Turn a vague development idea into clear goals, constraints, and acceptance criteria through a guided interview. It checks unresolved decisions and confirms the agreed goal before moving toward a Seed, the requirements document used by Ouroboros.

  • Clarifying a vague idea before development
  • Defining completion criteria for a new feature
  • Agreeing on scope and constraints
Q00/ouroboros6.2KUpdated Oct 19, 2026

See all skills by Q00

Report a problem with this skill