Expand description
The borg skill (skills/borg/): how borg works and how to set it up, for the drone itself. Compiled
in and copied by borg install into every harness that loads skills (dir), one
Change per file, with an adapter file’s rules: each file is copied whole, a symlinked file is
replaced (never written through), and uninstall removes only a file whose content is exactly this
borg’s, without a backup (borg recreates it exactly), then the skill’s directories once empty. A
skill directory that is itself a symlink is the engineer’s (ln -s into a checkout): left alone.
borg status and borg doctor report a missing or stale skill (an older borg’s, or edited). borg
cannot tell an older borg’s text from an edit, so install backs up either one beside it: after an
upgrade that changed the skill, uninstall leaves those backups and the directory holding them.
Enums§
- State
- How the skill stands in one harness.
Constants§
- FILES
- The skill’s files, relative to its directory, and their content.
Functions§
- checks
borg doctor: the skill’s state for harnessname. A missing skill is a finding only where borg is wired (wired): an upgrade from a borg without the skill.- dir
- Where
hloads theborgskill from:skills/borgin its config directory, the one holding its hook config or its adapter’s directory (Claude Code, codex-cli 0.154.0, omp 17.3.5, opencode.ai/docs/skills);homeandvaras forHarness::target. None for the hidden harness, which loads none. Derived from the wiring, never the name: a harness that loads skills elsewhere needs aHarnessmethod of its own. - plan
- What
actionwould change in the skill directorydir(None: the harness loads no skills), plus notes on what is left alone. - state
- The skill’s state in
dir. - status
borg status: the skill’s state for harnessname, in a few words; None where it loads no skills.- tidy
- After an uninstall: removes the skill’s directories that are now empty, innermost first. Anything still in them (a backup, the engineer’s own file) keeps them.