setup skill
Install symbion and set it up in this project, saying what each step writes and asking before each write
- GitHub stars
- 9
- Files
- 1
- Last commit
- Nov 14, 2026
- License
- MIT
- Allowed tools
- —
What does the setup skill do?
setup is an agent skill. Install symbion and set it up in this project, saying what each step writes and asking before each write.
How to install the setup skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the setup skill in Plugin
/plugin marketplace add phreakocious/symbion /plugin install symbion@symbion
Install the setup skill in Claude Code
~/.claude/skills/setup/SKILL.md
$ npx degit phreakocious/symbion/plugin/skills/setup ~/.claude/skills/setupInstall the setup skill in Claude Code (project)
.claude/skills/setup/SKILL.md
$ npx degit phreakocious/symbion/plugin/skills/setup .claude/skills/setupInstall the setup skill in Codex
~/.agents/skills/setup/SKILL.md
$ npx degit phreakocious/symbion/plugin/skills/setup ~/.agents/skills/setupInstall the setup skill in Gemini CLI
~/.gemini/skills/setup/SKILL.md
$ npx degit phreakocious/symbion/plugin/skills/setup ~/.gemini/skills/setupInstall the setup skill in Claude.ai
npx degit phreakocious/symbion/plugin/skills/setup setup && zip -r setup.zip setup # claude.ai → Customize → Skills → + → Create skill → Upload a skill → setup.zip
SKILL.md
View on GitHubSet up symbion in this project. Write nothing before the user approves it. Keep scratch files out of the repo.
Facts, gathered as this skill loaded (run any command left unrun):
- symbion: !
symbion -V 2>&1 || echo "symbion: not installed" - the repo: !
git rev-parse --show-toplevel 2>/dev/null || echo "not a git repository"
- Say in two sentences what symbion is: a notebook and ticket registry kept beside the repo, in a git repo of its own; each new session starts with the open bugs, tasks and questions, and a trap filed on a file reaches the agent when it opens that file. Then say what setup does: install the CLI if needed, make the project's store, bring in its open threads, and open the browser view.
- If the repo line above is not a path, say that the store needs a git repository, and stop.
- The CLI. Under Antigravity,
operation not permittedfrom symbion is agy's sandbox, not a missing install: run each symbion call withBypassSandboxuntil step 4's rules are in. This plugin needs symbion 0.16.1 or later (a.devNcounts), on Python 3.11 or later. Not installed: planuv tool install --python '>=3.11' 'symbion[gui]'whenuvis on PATH (uv may download a Python; say so), elsepipx install 'symbion[gui]', with--pythonnaming a 3.11 or later whenpipx environment --value PIPX_DEFAULT_PYTHONis older. Older: planuv tool upgrade symbionorpipx upgrade symbion, whichever installed it. With neither uv nor pipx, say so, point to https://github.com/phreakocious/symbion#install, and stop. Never run pip into a system Python. - The store. With the CLI installed, run
symbion init, without--yes: it lists each change and makes none. Under Antigravity, everysymbion initin this skill takes--agent antigravity, so its list names the rules agy's auto mode needs: show them, and ask the user to add each at agy's/permissionsbefore approving: a rule may name a store not made yet, and the rest of setup then runs with no prompt. Never write agy's settings yourself. Under Hermes, everysymbion inittakes--agent hermes, which links the skill into Hermes's profile. Show that list, less its notes on the plugin. Without the CLI, say what it does by default: it creates the store../<repo>-notes, a git repo beside this one, and writes nothing into this repo. Setup itself adds one line,- We use symbion for durable notes and tickets., to the instructions file this host reads. Claude Code readsCLAUDE.md. Hermes reads the first of.hermes.md,AGENTS.override.md,AGENTS.mdandCLAUDE.mdit finds: add the line there, else createAGENTS.md. Antigravity never readsCLAUDE.md: add the line toAGENTS.mdorGEMINI.md, whichever exists, else createGEMINI.md, since a newAGENTS.mdwould hideCLAUDE.mdfrom Pi and Hermes. Where that file is gitignored or someone reviews every change to it, propose the line instead of writing it. - Ask for approval of steps 3 and 4 at once. First list, in your message, one line per write: the exact install command and where it puts the CLI, the store's path, and the instructions file with its line. A question dialog alone hides them. The store is outside this repo, so the host may ask before its writes too. On no, stop: nothing was written. On yes, install, then run
command -v symbion. If it finds nothing, the install's bin dir is not on PATH: say where the command went, use its full path for the rest of setup, and ask before any change to a shell's rc file (uv tool update-shell,pipx ensurepath); the hooks find symbion only in a session started from a shell whose PATH has it, and under Hermes only in a gateway started from one. Then, in a call of its own, runsymbion initagain without--yes. If its list differs from what you described, show the difference and ask again. Under Antigravity, next runsymbion -VwithoutBypassSandbox: if it fails, ask the user to add the rules init lists, and wait; once it starts, in auto mode, takeBypassSandboxonly for whatadoption.mdreads outside the repo. Then runsymbion init --yesand append the line, after a newline if the file lacks a final one. - Adoption, empty store or not. Run
symbion skill adoptionand follow it, leaving out what an entry holds. Ifsymbion list --limit 1shows an entry, first ask whether to look for what the store lacks (notes kept before the plugin, a handoff since); if the user says no, go to 8. Scout the TODO files, handoff notes, agent memory and the git log since the last handoff, then build the candidate table and the list of sources to retire, naming each file and what happens to it. Print both in full in your message, then ask for approval. On yes, add the entries as onesymbion add --from-json -, retire the sources asadoption.mdsays, and runsymbion commit. On no, keep the store as it is and say that/symbion:setupruns adoption again. - If the store is still empty, say so, and send the user to https://symbion.nullphase.net/ to see a store that weeks of work filled.
- Start
symbion serve --no-browserin the background with its output to a temp file, and read its first line, the URL, withhead -1. Give the user that URL to look through the store, and say thatsymbion serve --stopstops it and every other serve.
Files in this skill
1setup skill questions
How do I install the setup skill in Claude Code?
Run npx degit phreakocious/symbion/plugin/skills/setup ~/.claude/skills/setup. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the setup skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.