Ryuu's Skills

Getting Started

Clone the repository, run the installer, and pick a delivery mode.

Install

Prerequisites: git, gh and Bun 1.4.0 or newer. Installing needs no Python.

git clone https://github.com/ryuudotgg/skills && cd skills && ./install.sh

install.sh symlinks this checkout's skills/ into the canonical store at ~/.agents/skills, then links those skills into the agent tool directories it finds. It creates ~/.claude/skills when ~/.claude exists, and ~/.codex/skills when ~/.codex exists. It also links into existing ~/.cursor/skills, ~/.config/opencode/skills, and ~/.copilot/skills directories without creating them.

With no flags other than --verbose, stdin and stdout at a terminal, and CI unset, skills install asks for the delivery mode, the auto update choice and the optional skills and reviewers. When you pick hub and no HUB_URL is set yet, it asks whether to join a hub, start one or set it up later. It then asks for the arm roster, the families delegated work may use. When the Claude Code, Codex or OpenCode directory exists, it then asks for Deny, Ask, Customize or Don't manage and saves AGENT_RULES in skills.conf. Rule changes are previewed before you confirm. Canceling changes no skill links, agents or settings. Other flags, redirected input or output, and any CI value skip these questions. At a terminal a run with flags still asks the hub question for --with hub when no hub is set, and still asks you to confirm weakening rule changes. Before any of that, install.sh installs the CLI's runtime dependencies with bun install --frozen-lockfile --ignore-scripts --production --filter skills-cli, which reads Bun's cache and reaches the network only for a package it does not hold. skills update runs no install of its own: the release it moves to installs its own dependencies through its install.sh, and a rollback runs the old release's.

At a terminal the installer ends with one row per tool saying what changed, or that it is up to date, with any skip, left, stale, note or warn line beneath it. --verbose lists every line under its row. Redirected output keeps one line per item on every run.

When Claude Code is installed, it copies agents/ into ~/.claude. A personal skill link or agent file with the same name is left alone, and the output lists it on a skip line with the reason.

Whenever ~/.codex (or CODEX_HOME) exists, it adds missing skills entries to that directory's hooks.json. All four hook entries run the skills CLI through the AGENTS_DIR link, which defaults to ~/.agents/skills. An entry this repository shipped for a retired hook is switched to its replacement in place. Personal entries are left alone. You can rerun it safely. By default, nothing is staged, committed, pushed, or posted unless you turn it on.

The installer writes the Claude hooks into Claude Code's settings.json (in CLAUDE_CONFIG_DIR, else ~/.claude). It prints the block for a paste only if it refuses the file. With AGENT_RULES set in skills.conf, it also writes strengthening and neutral permission changes there. At a terminal it lists changes for you to confirm under Add, Update and Remove, all ticked. Unticking a rule group saves its override. Unticking a Claude hook saves CLAUDE_HOOK_<TARGET>=off; delete that line to re-enable it. Non-terminal runs leave weakening rule changes on a left line for you to apply by hand. With AGENT_RULES unset or the file refused, it names the reason instead, and --verbose prints the rule set to paste. When the Codex directory exists, the same levels write Codex's rules/skills.rules (Codex). It removes old shipped hook copies only after rewiring the hooks, and only when every registration it can find can be read and parsed and none names a file under the Claude hooks directory. It reads your Claude settings, your Codex hooks.json, and the .claude/settings.json and .claude/settings.local.json of every project in ~/.claude.json. Personal files and the directory stay. The installer never creates that directory.

Update

./skills/playbook/bin/skills update

Run it from the checkout. It moves the checkout to the newest release, refusing when that release is not on main or its commit is not verified by GitHub, then reruns the installer with no flags and no terminal, so every skills.conf choice stays and weakening rule changes wait on a left line. It refuses, changing nothing, when CI is set, when SKILLS_AUTO_UPDATE=0, when the checkout has changes or local commits or sits on another branch, or while another update runs. If the installer fails, it moves the checkout back and reruns the old installer. --check stops before moving anything and prints available, current or refused.

Other Install Cases

Continue Setup

On this page