Santoryu Skills

Santoryu — setup and usage

Santoryu's orchestration blade. Its blades are its products: this one, Mindmap (the work environment at santoryu.net) and a workspace still to come.

Inside this one: Opus (Claude Code) plans and reviews; two fast runners — a repo-aware Cursor agent and a raw OpenAI-compatible model — do the mechanical work. The goal: cut the number of slow iterations.

The package ships two Claude Code skills, `santoryu` and `query-json`, and puts a console command on PATH for each.

Install

pipx install git+https://github.com/SantoryuLabs/santoryu-skills.git

From a local checkout, `pipx install .` (or `pip install .`) does the same. Python 3.10+; dependencies come with the package.

Then give the Cursor runner a key — export `CURSOR_API_KEY=crsr_...` (User API key from Cursor Dashboard -> API Keys), or write it into `~/.santoryu/.env`:

CURSOR_API_KEY=crsr_...

The key lives there, never inside the package and never in the skills dir.

Register the skills with Claude Code:

santoryu install

That copies each packaged `SKILL.md` into `~/.claude/skills//` verbatim. No filesystem path is written into the installed copy, so moving, renaming, or deleting this checkout cannot break the install. It is idempotent and overwrites a stale earlier install. Restart Claude Code to pick the skills up.

Or install as a Claude Code plugin

This repo is also a plugin marketplace, which is the shorter route: it registers the same skills *and* connects the Mindmap MCP server in one step.

/plugin marketplace add SantoryuLabs/santoryu-skills
/plugin install santoryu@santoryu

The plugin reads its skills straight out of `src/santoryu/data/skills/`, so there is one copy of each `SKILL.md` and no way for the plugin and the pip package to drift apart. Pick one route or the other — installing both leaves Claude Code holding the same skill twice.

**The plugin does not install the CLI.** Claude Code plugins cannot run an in