foxrun-ai/foxrun / plugins/foxrun/skills/foxrun-setup
foxrun-setup
VerifiedInstall the Foxrun core when it is missing, or rerun the setup again, all of it or one part. Parts: the questions, the agent threads, the hooks, and the backup. Use for /foxrun-setup, /foxrun-setup <part>, a thread's first boot, or when someone asks to redo, check, or finish setup.
foxrun-setup
Install sets Foxrun up once. This skill reruns it: all four parts in order, or the one part the person names.
If the Foxrun core is not installed yet, this skill installs it first.
bin/setup status reads where each part stands and gives the next open question. It writes nothing.
Ask each question with the runtime's question tool, one at a time, so the person answers with one tap.
Steps
-
Check the core. If
~/.foxrun/foxrun.pyis missing, the core is not installed, andbin/setup statusreads an empty home. Ask for the name, the first workspace, and the runtime, one question each. Offer the runtime you run in first. Show the person these commands, and run them only on their yes:uv tool install git+https://github.com/foxrun-ai/foxrun foxrun install --home "$HOME/.foxrun" --portfolio "$HOME/foxrun" --yes --person <name> --workspace <workspace> --runtime <claude|codex|both> python3 "$HOME/.foxrun/foxrun.py" doctorIf
uvis missing, send the person to https://docs.astral.sh/uv/ first. On Windows, usepy -3in place ofpython3. Done when doctor printsDoctor: 0 failed, or the core was already there.Update an existing core. After a plugin upgrade, tell the person that the plugin refreshed only its three skills. Show these commands and ask them to run the update, or run it on their explicit yes:
uv tool upgrade foxrun foxrun update --home "$HOME/.foxrun"For a clone install, use
git pull, thenpython3 foxrun.py update --home "$HOME/.foxrun"from the product folder. Use the person's custom home path when needed. Success ends withDoctor: 0 failed. Keep the printed backup path if update fails. A plugin upgrade alone does not update the core. -
Read the state. Run
bin/setup status, orbin/setup status --part <part>for one part. Done when you have thepartslist and itsnext. -
Questions. For each item in the questions part's
open, ask itsquestionwith itschoices. To change an answer, runbin/setup set --field <key>=<value> --dry-run, show the person thechanges, and on their yes run it again without--dry-run. Onlyruntimeanddefault_workspacechange here. A new name is a new install; a new workspace is a workspace job. Done when the questions part has noopenitem, or the person skipped it. -
Threads. Use the
threadskill. Offer each seat in the threads part'sopen, one question at a time. Done when each offered seat has a thread or the person said no. -
Hooks. If the hooks part has an
openitem, ask itsquestionword for word, withYes (recommended)first. Then runbin/setup hooks --answer yesor--answer no. On yes, it runsfoxrun.py hookupfor each app with missing hooks. That command copies the app's settings file to the backup folder first, adds only the Foxrun entries, and keeps every other entry. Show the person the result in plain words: each settings file inconnected, what it turns on fromwhat_it_does, and each folder inbackups. Then saynext. Ifstill_missingis not empty or the command fails, show the error and stop. Do not edit a settings file yourself. Done when the person answered and saw the result. -
Backup. If the nightly job is off, show its
commandand run it only on the person's yes. A state remote is a change on an outside platform: tell the person the steps; never make the remote for them. Done whenopenis empty, or the person said no to each item. -
Report. Rerun
bin/setup status. Say in one line per part what changed and what stays open. Done when the person has that list.
Gotchas
- The whole setup runs the parts in the order above. One part runs only that step and the report.
- A new thread's boot prompt runs
bin/setup statusand asks itsnext. Ifnextis empty, setup is done; ask what to work on. statuscounts the nightly job as on when it ran in the last two days, even if install did not turn it on.- Hooks are checked by script path. A hook entry that runs the same script from another path shows as missing.
- Claude and Codex keep four hooks: session-start, after-compact, before-compact, and session-end. start-rules is for Hermes only, so
statusnever reports it missing here. bin/setup hooks --answer yesis safe to run twice. The second run finds every entry and writes nothing. An older core with nohookupcommand gets an error that says to update the core first.- The same command works by hand:
python3 "$HOME/.foxrun/foxrun.py" hookup --runtime <claude|codex|both>.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |