Agent skill

Ouroboros Settings Opener

Opens or drives the Ouroboros settings GUI, picking a browser, TUI or chat-based approach depending on whether the user can reach a browser window.

MITAuto-check passedAgent Workflows

Install Ouroboros Settings Opener

skills CLI

$ npx skills add Q00/ouroboros --skill ouroboros-config -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Q00/ouroboros ouroboros-config --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Q00/ouroboros.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/config .claude/skills/ouroboros-config && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "ouroboros-config" agent skill from https://github.com/Q00/ouroboros/tree/main/skills/config into .claude/skills/ouroboros-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ouroboros-config", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Q00/ouroboros/tree/main/skills/config

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Q00/ouroboros --skill ouroboros-config -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Q00/ouroboros ouroboros-config --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Q00/ouroboros.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/config .agents/skills/ouroboros-config && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ouroboros-config" agent skill from https://github.com/Q00/ouroboros/tree/main/skills/config into .agents/skills/ouroboros-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ouroboros-config", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Q00/ouroboros --skill ouroboros-config -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Q00/ouroboros ouroboros-config --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Q00/ouroboros.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/config .cursor/skills/ouroboros-config && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ouroboros-config" agent skill from https://github.com/Q00/ouroboros/tree/main/skills/config into .cursor/skills/ouroboros-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ouroboros-config", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Q00/ouroboros.git --path skills/config

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Q00/ouroboros --skill ouroboros-config -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Q00/ouroboros ouroboros-config --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Q00/ouroboros.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/config .gemini/skills/ouroboros-config && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "ouroboros-config" agent skill from https://github.com/Q00/ouroboros/tree/main/skills/config into .gemini/skills/ouroboros-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ouroboros-config", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Q00/ouroboros ouroboros-config

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Q00/ouroboros --skill ouroboros-config -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Q00/ouroboros.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/config .github/skills/ouroboros-config && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "ouroboros-config" agent skill from https://github.com/Q00/ouroboros/tree/main/skills/config into .github/skills/ouroboros-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ouroboros-config", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Q00/ouroboros --skill ouroboros-config -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Q00/ouroboros ouroboros-config --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Q00/ouroboros.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/config .opencode/skills/ouroboros-config && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ouroboros-config" agent skill from https://github.com/Q00/ouroboros/tree/main/skills/config into .opencode/skills/ouroboros-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ouroboros-config", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: ouroboros-config
GitHub stars: 6.2k
Token cost: ~1.2k tokens
SKILL.md length: 485 words
Files: 1
Skills in repo: 23
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Opens or drives the Ouroboros settings GUI, picking a browser, TUI or chat-based approach depending on whether the user can reach a browser window.

Works in 3 steps: Launch in the background (the command… → Relay the http://localhost: line from… → Tell the user: edit → Save → then ask…
Opening Ouroboros settings on your own machine
SKILL.md covers Usage, Instructions and RFC #1392 State Breadcrumb…
Calls uvx, uv and ssh

What it does

The deciding question is whether the user can open a browser pointed at the machine the agent is running on. On the user's own local machine it launches the settings app in the background, which serves itself over a local web server and auto-opens the browser, relaying the printed localhost URL in case the browser didn't pop up, and noting that a running server may need a reconnect to pick up changes and that a saved model choice is never permanent.

On a remote host the user can reach over the network, it serves without auto-opening and hands over the URL along with an SSH tunnel command as a fallback. On a chat gateway with no browser path at all, it never starts a server nobody can reach; instead it shows the current configuration as text and presents a short menu of per-stage runtime and model choices for the user to pick from conversationally.

When your agent uses it

Opening Ouroboros settings on your own machine
Configuring Ouroboros on a remote SSH host you can reach
Changing a model or agent setting through a chat interface with no browser

Example prompts

“Open the Ouroboros settings so I can change the default model.”
“Configure Ouroboros on this remote server and give me the URL.”
“Show my current Ouroboros config and let me change the per-stage agents.”

Requirements

The `ouroboros` CLI or its MCP server

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Launch in the background (the command serves until stopped)
Relay the http://localhost: line from the output so the user can
Tell the user: edit → Save → then ask you to stop the server. Remind them

What it can do on your machine

Read from SKILL.md and the folder at commit f587795. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- uvx
- uv
- ssh
- pip
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uvx, uv, ssh and pip, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ouroboros Settings Opener loads about 1.2k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 485 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~25
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Q00/ouroboros at commit f587795, republished under its MIT licence (© Q00). 485 words, ~1,167 tokens.

Download SKILL.mdSave it as .claude/skills/ouroboros-config/SKILL.md (or your agent's skills folder).

name: ouroboros-config
description: Open or drive the Ouroboros settings GUI (browser, TUI, or conversational fallback)

/ouroboros:ouroboros-config

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

Usage

ooo config
/ouroboros:ouroboros-config

Trigger keywords: "ooo config", "open settings", "configure ouroboros", "change model", "change agent"

Instructions

Pick the branch that matches where you (the agent) are running. The decisive question: can the user open a browser pointed at this machine?

Branch A — local harness (Claude Code / Codex on the user's own machine)

Launch in the background (the command serves until stopped):
bash
```
if command -v ouroboros >/dev/null 2>&1; then
  ouroboros config
else
  uvx --python '>=3.12' --from 'ouroboros-ai[tui]' ouroboros config
fi
```
The command detects the non-interactive context itself and serves the settings app over a local web server, auto-opening the user's browser. The uvx fallback is required for a Marketplace-plugin-only install, where the MCP server exists but ouroboros is not on PATH. In a development checkout use uv run ouroboros config.
Relay the http://localhost:<port> line from the output so the user can open it manually if the browser did not pop up.
Tell the user: edit → Save → then ask you to stop the server. Remind them a running MCP server may need a reconnect to pick up backend changes. Tell them they can reopen these settings any time with ooo config; saving a model choice never locks it permanently.

Branch B — remote host the user can reach over the network (SSH box, home server)

The user cannot see a browser opened here, but may be able to reach this host. Serve without auto-open and hand over the URL:

bash

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 the command prints (ssh -L <port>:localhost:<port> <this-host>).

Show full SKILL.md (291 more words)Show less

Branch C — chat gateway, no browser path at all (e.g. hermes driven from Discord)

Do NOT start a server nobody can reach. Drive the same settings conversationally over the scriptable surface:

Show the current state:
bash
```
ouroboros config show
```
Present the user a short menu in chat (default agent, per-stage agents, and models: auto, a tier, or a model id for every role) with the current values, and ask what to change.

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

bash

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

Confirm with ouroboros config show and summarize what changed.

If a set is rejected, relay the validation error verbatim — it lists the valid keys/values.

All branches

If the command fails with a missing-dependency hint, relay it verbatim (pip install 'ouroboros-ai[tui]'). Scriptable edits always remain on ouroboros config show|set|backend|init|validate.

End your final message with the state breadcrumb footer (RFC #1392), e.g.:

◆ Settings GUI serving at <url> → next: Save in browser, then stop the server
◆ Config updated via chat (<keys>) → next: reconnect MCP if the backend changed

Your final response MUST end with exactly one breadcrumb footer line:

◆ <current state> → next: <recommended action>

Derive <current state> from live session state via ouroboros_session_status when that MCP projection is available; otherwise derive it from this skill's actual outcome. Never use a linear Step N of M footer because Ouroboros is an evolutionary loop. When the next action is genuinely a choice, list 2-3 honest options in the next: clause. The breadcrumb line must be the last line of the response.

Files

Just SKILL.md in skills/config of Q00/ouroboros.

Open the folder on GitHubat commit f587795

Compare with similar skills

Ouroboros Settings Opener next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ouroboros Settings Opener compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ouroboros Settings Opener this skillQ00/ouroboros	6.2k	—	~1.2k	Automated safety check: Pass	MIT	2 days ago
MCP Server Builderanthropics/skills	180k	63 repos	~2.3k	Automated safety check: Pass	Apache-2.0	today
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official	38k	10 repos	~4.1k	Automated safety check: Notes	Apache-2.0	today
Using Superpowersfarm-fe/farm	5.6k	35 repos	~1.4k	Automated safety check: Pass	MIT	18 days ago
Executing Plans Inlineobra/superpowers	297k	2 repos	~5.1k	Automated safety check: Pass	MIT	today
Skill CreatorAzure/azqr	796	89 repos	~8.2k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

MCP Server Builder
anthropics/skills
Official
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
180k GitHub starsUsed in 63 repos~2.3k tokens
Agent WorkflowsAuto-check passed
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
38k GitHub starsUsed in 10 repos~4.1k tokens
Agent WorkflowsAuto-check: notes
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
5.6k GitHub starsUsed in 35 repos~1.4k tokens
Agent WorkflowsAuto-check passed
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
297k GitHub starsUsed in 2 repos~5.1k tokens
Agent WorkflowsAuto-check passed
Skill Creator
Azure/azqr
Official
Create new skills, modify and improve existing skills, and measure skill performance.
796 GitHub starsUsed in 89 repos~8.2k tokens
Agent WorkflowsAuto-check passed
Claude Code Agent Development
anthropics/claude-plugins-official
Official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
38k GitHub starsUsed in 7 repos~2.8k tokens
Agent WorkflowsAuto-check passed

Questions about Ouroboros Settings Opener

What does Ouroboros Settings Opener do?

Opens or drives the Ouroboros settings GUI, picking a browser, TUI or chat-based approach depending on whether the user can reach a browser window. The deciding question is whether the user can open a browser pointed at the machine the agent is running on. On the user's own local machine it launches the settings app in the background, which serves itself over a local web server and auto-opens the browser, relaying the printed localhost URL in case the browser didn't pop up, and noting that a running server may need a reconnect to pick up changes and that a saved model choice is never permanent.

When should I use Ouroboros Settings Opener?

Ouroboros Settings Opener fits situations like: opening Ouroboros settings on your own machine; configuring Ouroboros on a remote SSH host you can reach; changing a model or agent setting through a chat interface with no browser.

How do I install Ouroboros Settings Opener in Claude Code?

Run `npx skills add Q00/ouroboros --skill ouroboros-config -a claude-code`. Or copy the skill folder (skills/config in Q00/ouroboros) into .claude/skills/ouroboros-config in your project. Claude Code loads it when a task matches its description.

How do I install Ouroboros Settings Opener in Codex?

Run `npx skills add Q00/ouroboros --skill ouroboros-config -a codex`. Or copy the skill folder (skills/config in Q00/ouroboros) into .agents/skills/ouroboros-config in your project. Codex loads it when a task matches its description.

Can I use Ouroboros Settings Opener in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Q00/ouroboros --skill ouroboros-config -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ouroboros-config, .gemini/skills/ouroboros-config, .github/skills/ouroboros-config and .opencode/skills/ouroboros-config in your project.

What does Ouroboros Settings Opener need to run?

Going by SKILL.md and its folder, Ouroboros Settings Opener needs the command-line tools its instructions call (uvx, uv, ssh and pip). Our summary lists: The `ouroboros` CLI or its MCP server.

Does Ouroboros Settings Opener access the network?

SKILL.md contains no URLs. Its commands use uvx, uv, ssh and pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Ouroboros Settings Opener safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ouroboros Settings Opener use?

Ouroboros Settings Opener is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ouroboros Settings Opener use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ouroboros Settings Opener?

Skills that share tags, products or a category with Ouroboros Settings Opener: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ouroboros Settings Opener?

Q00 (a GitHub user) maintains it in Q00/ouroboros, which has 6,193 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 7, 2026.

Source: Q00/ouroboros on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Ouroboros Settings Opener

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

/ouroboros:ouroboros-config

Usage

Instructions

Branch A — local harness (Claude Code / Codex on the user's own machine)

Branch B — remote host the user can reach over the network (SSH box, home server)

Branch C — chat gateway, no browser path at all (e.g. hermes driven from Discord)

All branches

RFC #1392 State Breadcrumb Footer

Files

Compare with similar skills

Similar skills

More from Q00/ouroboros

Related

Questions about Ouroboros Settings Opener