hora-addon
How an add-on extends the hora skills — the Hora Kit range it is built for, the wings every hora skill resolves before it acts, how several add-ons combine where they touch the same section, and the precedence a person may set between them. Read by every hora skill once its version is fixed, and again after a resume or a compacted context. Invoked directly as /hora-addon to set or check that precedence. What an add-on itself decides belongs to that add-on's own skill.
openreachtech · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add openreachtech/hora-core --skill hora-addonAbout this skill
name: hora-addon description: How an add-on extends the hora skills — the Hora Kit range it is built for, the wings every hora skill resolves before it acts, how several add-ons combine where they touch the same section, and the precedence a person may set between them. Read by every hora skill once its version is fixed, and again after a resume or a compacted context. Invoked directly as /hora-addon to set or check that precedence. What an add-on itself decides belongs to that add-on's own skill.
hora-addon
The rule every hora skill follows about add-ons. An add-on is a package installed beside Hora Kit that lets the hora skills do what they could not do on their own. This skill says what an add-on may carry, when it takes effect, and what happens where several of them reach the same place. Each add-on describes itself, and the examples here use invented names (alpha-example-addon, beta-example-addon). Hora Kit may name an add-on, public files included. An add-on is protected by its distribution channel — a private package of the npm organization, readable only by the teams that bought it — not by keeping its name out of public files.
An add-on that is not installed changes nothing, and neither does one that is installed but not active. Every rule below starts from the skills as they are written and changes them only where an active add-on says so.
What an add-on carries
An add-on carries skills, wings, or both.
| Part | What it is | Installed at |
|---|---|---|
| a skill | a skill in its own right, invoked as any other | .claude/skills/<skill-name>/ |
| a wing | a file that extends what an existing skill can do. The skill itself stays as written | .hora/wings/<skill-name>/<addon-name>/ |
| its definition | the add-on's name, when it is active, and the Hora Kit it needs | .hora/addons/<addon-name>.json |
The name "wing" carries two readings, and both are meant. A wing lets something fly that could not — a skill gains what it could not do. A wing of a building is joined to the original, which stays standing as it was — the skill is never replaced.
Wings and definitions sit under .hora/, not .claude/. .claude/ holds what Claude Code reads, and both are read only by the hora skills, so they belong in Hora's own directory.
Everything under .hora/wings/ and .hora/addons/ is written by the add-on's installer, and nothing else writes there. Hora Kit's own installer never touches either, so reinstalling Hora Kit leaves every add-on in place. Neither is committed: both are regenerated on every install, unlike the records under .hora/.
The definition goes with the wings pass, whether or not the add-on carries any wings. hora-addon-<name> install --only wings, and install with no --only, places it; uninstalling the wings part removes it; --only skills alone leaves it as it is.
The Hora Kit it was built for
Every add-on states the range of @openreachtech/hora it was built against, as horaKit in its definition, whatever it carries — skills, wings or both. Its definition is read by Hora Kit's resolving, and its wings find their sections by heading. A heading exists in some versions of Hora Kit and not in others, so the range is what says which headings the add-on relies on.
"horaKit": "^1.0.0"
- A condition on the consuming repository, never a dependency. The add-on uses nothing of Hora Kit; Hora Kit's skills read the add-on. As a peer dependency, npm would install Hora Kit into the add-on's own repository as well, where nothing uses it. As a dependency, each add-on could install a Hora Kit of its own, and its wings would be checked against a copy the project never runs.
- The field is never left out. A forgotten range is not read as any: that would place wings beside a Hora Kit that may carry none of their sections.
- The range is the one source. Nothing else restates it.
- The lower bound is the first Hora Kit release carrying every
[wing]section the add-on's wings extend, and the caret stays. Renaming or removing a[wing]section is a breaking release ("The[wing]sections", below), so every version the caret admits still carries them. While Hora Kit is in beta (0.x.x), a range such as>=0.10.0 <1.0.0is allowed as an exception, since a caret there stops at the next minor; any0.xminor may then rename a section the wings extend. - The add-on's installer checks the installed Hora Kit against it, before placing anything, and changes nothing where the definition declares no range, or one
semverdoes not read, where no Hora Kit is installed, or where the one installed is outside the range. It resolves@openreachtech/hora/package.jsonfrom the consuming repository as Node would, reads its version, and holds it against the range with thesemverpackage. npm never reads the field, so this check is the only one, and a wing installed against headings that are not there does nothing at all, without a word. The cheapest place to stop that is before anything is copied.uninstallchecks nothing.
A wing overlays, it never copies
A wing file sits at the same relative path, under its skill's name, as the file it extends, and holds nothing but the [wing] sections it changes.
.claude/skills/hora-plan/SKILL.md the skill as written
.claude/skills/hora/references/asking.md
.hora/wings/hora-plan/alpha-example-addon/SKILL.md overlays hora-plan/SKILL.md
.hora/wings/hora/alpha-example-addon/references/asking.md overlays hora/references/asking.md
- A wing is looked up by the file it extends, never by the skill reading it. A skill reading a file that holds a
[wing]section takes the skill that file belongs to, and looks for a file at the same relative path under.hora/wings/<that skill>/*/.asking.mdbelongs to/hora, so every skill that reads it finds the same wing. - **A file th