diff --git a/.agents/skills/browser/SKILL.md b/.agents/skills/browser/SKILL.md
index dfeb0d8dd..e299f7fa7 100644
--- a/.agents/skills/browser/SKILL.md
+++ b/.agents/skills/browser/SKILL.md
@@ -5,24 +5,24 @@ description: A real browser you drive from the shell, to see or act on a web pag
 
 # The browser
 
-A headless Chrome of your own, on an empty profile: nobody's logins are in it. Drive it with the `browser` command, a dependency of this repository (`@openagt/skill-browser`), run as `npx browser`. When that fails for a missing `node_modules`, install with the lockfile's package manager (`npm install` for `package-lock.json`) and run it again. It needs Chrome on the machine, or `CHROME_PATH` set to a Chrome or Chromium executable.
+A headless Chrome of your own, on an empty profile: nobody's logins are in it. Drive it with the `browser` command, always run by its full name: `npx @openagt/skill-browser@0.1`. It needs Chrome on the machine, or `CHROME_PATH` set to a Chrome or Chromium executable.
 
 ```
-npx browser open <address>       open the address, starting the browser if none is open
-npx browser read                 print the page again
-npx browser click <n>            click element n
-npx browser type <n> <text>      replace what element n holds with the text; on a select, pick that option;
-                                 on a date or time field, give the value as 2024-01-31, 13:45, 2024-01
-npx browser press <key>          Enter, Tab, Escape, Backspace, Space, ArrowUp, ArrowDown, ArrowLeft, ArrowRight
-npx browser screenshot [file]    save what the page shows as a PNG and print its path (a temporary file
-                                 when none is named; never name one inside the repository)
-npx browser eval <script>        run a JavaScript expression in the page and print its value, as JSON
-                                 (`document.title`, not `return document.title`; `await` works; an
-                                 element prints as `{}`, so ask for its properties)
-npx browser close                close the browser
+npx @openagt/skill-browser@0.1 open <address>       open the address, starting the browser if none is open
+npx @openagt/skill-browser@0.1 read                 print the page again
+npx @openagt/skill-browser@0.1 click <n>            click element n
+npx @openagt/skill-browser@0.1 type <n> <text>      replace what element n holds with the text; on a select, pick that option;
+                                                    on a date or time field, give the value as 2024-01-31, 13:45, 2024-01
+npx @openagt/skill-browser@0.1 press <key>          Enter, Tab, Escape, Backspace, Space, ArrowUp, ArrowDown, ArrowLeft, ArrowRight
+npx @openagt/skill-browser@0.1 screenshot [file]    save what the page shows as a PNG and print its path (a temporary file
+                                                    when none is named; never name one inside the repository)
+npx @openagt/skill-browser@0.1 eval <script>        run a JavaScript expression in the page and print its value, as JSON
+                                                    (`document.title`, not `return document.title`; `await` works; an
+                                                    element prints as `{}`, so ask for its properties)
+npx @openagt/skill-browser@0.1 close                close the browser
 ```
 
-Quote a `<text>` or `<script>` with spaces as one argument: `npx browser type 2 'Ada Lovelace'`.
+Quote a `<text>` or `<script>` with spaces as one argument: `npx @openagt/skill-browser@0.1 type 2 'Ada Lovelace'`.
 
 `open`, `read`, `click`, `type` and `press` print the page once it has loaded (or after 10 seconds, as it stands): its title, its address, its text (the first 10,000 characters), then its elements (links, buttons, fields; the first 300) numbered `[n]`. What is inside an iframe or a shadow root is not printed; reach it with `eval`. `click` and `type` take that number, from the last print: when the page changes, the numbers do too. The numbers are written on the page's elements as `data-browser-ref` attributes. An address without `http://` or `https://` gets `http://`; no other kind opens. A dialog the page opens (alert, confirm, prompt) is accepted at once, and the next print begins with a `Dialog, accepted:` line naming it.
 
diff --git a/.agents/skills/discord/SKILL.md b/.agents/skills/discord/SKILL.md
index ad63d0c5b..446babe4b 100644
--- a/.agents/skills/discord/SKILL.md
+++ b/.agents/skills/discord/SKILL.md
@@ -5,16 +5,16 @@ description: Post a message to the team's Discord channel from the shell, when a
 
 # Discord
 
-Post one message to a Discord channel with the `discord` command, a dependency of this repository (`@openagt/skill-discord`), run as `npx discord`. When that fails for a missing `node_modules`, install with the lockfile's package manager (`npm install` for `package-lock.json`) and run it again.
+Post one message to a Discord channel with the `discord` command, always run by its full name: `npx @openagt/skill-discord@0.1`.
 
 ```
-npx discord send "<message>"     post the message to this machine's webhook
-npx discord status               whether this machine has a webhook, and where it comes from
+npx @openagt/skill-discord@0.1 send "<message>"     post the message to this machine's webhook
+npx @openagt/skill-discord@0.1 status               whether this machine has a webhook, and where it comes from
 ```
 
 Quote the message as one argument. It is posted as a Discord message, so Discord's markdown formats it (`*`, `_`, backticks), up to 2,000 characters (a longer one is cut and says so); `@everyone` and other mentions in it do not ping anyone.
 
-The channel is the one whose webhook this machine was given, by a person: `npx discord setup <webhook>` saves it for this user on this machine, `npx discord setup --clear` forgets it, and `DISCORD_WEBHOOK` in the environment wins over the saved one. Never ask for the webhook, never print it, and never write it into the repository: anyone holding it can post to the channel.
+The channel is the one whose webhook this machine was given, by a person: `npx @openagt/skill-discord@0.1 setup <webhook>` saves it for this user on this machine, `npx @openagt/skill-discord@0.1 setup --clear` forgets it, and `DISCORD_WEBHOOK` in the environment wins over the saved one. Never ask for the webhook, never print it, and never write it into the repository: anyone holding it can post to the channel.
 
 `send`, `setup` and `status` print one JSON line on stdout. A refusal exits 1 with the reason on stderr: `no-webhook` (none on this machine: say so and go on, a person sets it), `not-posted` (Discord or the network refused it; the detail says which, never the URL), `empty`, and for `setup`, `invalid`. A wrong command line exits 2 with the usage on stderr.
 
@@ -23,5 +23,5 @@ The channel is the one whose webhook this machine was given, by a person: `npx d
 A tool that runs coding agents may run a line of the person's when a run ends, with the message in `$MESSAGE`. This is the line:
 
 ```
-npx discord send "$MESSAGE"
+npx @openagt/skill-discord@0.1 send "$MESSAGE"
 ```
diff --git a/.agents/skills/github/SKILL.md b/.agents/skills/github/SKILL.md
index da4952bcd..7a5219f0a 100644
--- a/.agents/skills/github/SKILL.md
+++ b/.agents/skills/github/SKILL.md
@@ -9,14 +9,14 @@ The project's pull requests and issues are on GitHub. This skill is how you reac
 
 ## The command
 
-`github` is a dependency of this repository (`@openagt/skill-github`). If `node_modules` is missing, install with the lockfile's package manager (`npm install` for `package-lock.json`). Then run `npx github` inside your checkout. It prints JSON; a refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage.
+Run the `github` command inside your checkout, always by its full name: `npx @openagt/skill-github@0.1`. It prints JSON; a refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage.
 
 ## Your pull request
 
 Open a pull request only when your task or the person asks for one, or asks you to publish your work. Push your branch first (your branches skill says how), then:
 
 ```
-npx github open --title "<one line naming what the change does>" --body "<what changed, and why>"
+npx @openagt/skill-github@0.1 open --title "<one line naming what the change does>" --body "<what changed, and why>"
 ```
 
 It opens the pull request for the branch you are on and prints it in `request` (`number`, `url`). A branch that already has an open pull request gets no second one: that one is answered, with `existing` true. Add `--merge` when the work may land on its own: the pull request then merges once its checks pass, also where the repository does not allow auto-merge (`merge` in the answer says `auto-armed`, `merged` or `watching`). Add `--draft` instead for a pull request a person should look at first; with `--merge` too, `--draft` is dropped.
@@ -26,7 +26,7 @@ A pull request whose body has a line `Closes #<number>` closes that issue when i
 ## Reading pull requests and issues
 
 ```
-npx github requests [--branch <b>] [--state open|merged|all] [--since <iso>]
+npx @openagt/skill-github@0.1 requests [--branch <b>] [--state open|merged|all] [--since <iso>]
 ```
 
 The project's newest 50 pull requests, newest first, all states unless `--state`, only `<b>`'s with `--branch`; `--since` keeps those created since, or merged since with `--state merged`. Each has `number`, `url`, `state` (`open`, `merged`, `closed`), `title`, `draft`, `branch`, `head`, `createdAt`, and for a merged one `mergedAt` and `mergeCommit` (the commit it landed as).
@@ -36,7 +36,7 @@ For a pull request's discussion and diff, and for the project's issues, use `gh`
 ## Landing a pull request for a person
 
 ```
-npx github merge <number>
+npx @openagt/skill-github@0.1 merge <number>
 ```
 
 A draft is marked ready, then the merge is armed as `--merge` arms it: `outcome` says `auto-armed`, `merged` or `watching`; a request no longer open is refused as `not-open`. Only when whoever started you asked you to land it.
diff --git a/.agents/skills/logs/SKILL.md b/.agents/skills/logs/SKILL.md
index b8878184e..7648ce88e 100644
--- a/.agents/skills/logs/SKILL.md
+++ b/.agents/skills/logs/SKILL.md
@@ -7,21 +7,21 @@ description: The record of every run agents made on this project — what was as
 
 Every run an agent made on this project leaves a record on the branch `agent-data`, never on a code branch; your checkout does not contain it. A run is two files under `agents/<who>/`: the card, `<id>.json` — what was asked, the branch, the pull request, how it ended, what it cost — and the diary, `<id>.jsonl` — what the agent said along the way, its result.
 
-Read them with the `logs` command, a dependency of this repository (`@openagt/skill-logs`), run as `npx logs`. When that fails for a missing `node_modules`, install with the lockfile's package manager (`npm install` for `package-lock.json`) and run it again. You only read: the program that ran an agent records its run, at its end. The command's `delete` and `patch`, and its `--local` and `--full` flags, are for the dashboard that shows the runs; never use them. A refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage.
+Read them with the `logs` command, always run by its full name: `npx @openagt/skill-logs@0.1`. You only read: the program that ran an agent records its run, at its end. The command's `delete` and `patch`, and its `--local` and `--full` flags, are for the dashboard that shows the runs; never use them. A refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage.
 
 ## Read
 
 ```
-npx logs [--branch <name>] [--limit N]
-                                 the runs, newest first, as one JSON array of cards — the newest 20
-                                 unless --limit says otherwise; --branch keeps the runs on one branch
-npx logs show <id>               one run: its card, plus `diary`, the lines of what the agent
-                                 said, its result, how it ended, and what it cost
+npx @openagt/skill-logs@0.1 [--branch <name>] [--limit N]
+                                                    the runs, newest first, as one JSON array of cards — the newest 20
+                                                    unless --limit says otherwise; --branch keeps the runs on one branch
+npx @openagt/skill-logs@0.1 show <id>               one run: its card, plus `diary`, the lines of what the agent
+                                                    said, its result, how it ended, and what it cost
 ```
 
 ## Before you plan or work a ticket, read its earlier runs
 
-A ticket may have been worked before. Claiming it names who claimed it before you: a run's id, shaped like `2026-09-08T18-14-30-111Z`, read with `npx logs show <id>`, or else a branch, read with `npx logs --branch <name>`; no run on that branch means no record: read the branch itself. A `stopped` or `failed` run tells you what to avoid: read what its agent said before it ended. A `done` run with a `pr` means the work may already be there: read the pull request before doing it again.
+A ticket may have been worked before. Claiming it names who claimed it before you: a run's id, shaped like `2026-09-08T18-14-30-111Z`, read with `npx @openagt/skill-logs@0.1 show <id>`, or else a branch, read with `npx @openagt/skill-logs@0.1 --branch <name>`; no run on that branch means no record: read the branch itself. A `stopped` or `failed` run tells you what to avoid: read what its agent said before it ended. A `done` run with a `pr` means the work may already be there: read the pull request before doing it again.
 
 ## The card
 
diff --git a/.agents/skills/orchestration/SKILL.md b/.agents/skills/orchestration/SKILL.md
index 5b00d8c4b..47e3a7272 100644
--- a/.agents/skills/orchestration/SKILL.md
+++ b/.agents/skills/orchestration/SKILL.md
@@ -5,16 +5,16 @@ description: "Split your task across subagents: plan it, get the person's yes, s
 
 # Orchestration
 
-A subagent is another coding agent you start on one part of your task: it works alone, in its own checkout. Use the `orchestration` command, a dependency of this repository (`@openagt/skill-orchestration`), run as `npx orchestration`. When that fails for a missing `node_modules`, install with the lockfile's package manager (`npm install` for `package-lock.json`) and run it again.
+A subagent is another coding agent you start on one part of your task: it works alone, in its own checkout. Use the `orchestration` command, always run by its full name: `npx @openagt/skill-orchestration@0.1`.
 
 ```
-npx orchestration plan <file>    save the file as your plan; answers the `question` to ask the person
-npx orchestration start --level <simple|hard> "<task>"
-                                 start a subagent on the task; answers its id at once, without waiting for it
-npx orchestration list           your subagents, newest first, as one JSON array
-npx orchestration read <id>      one subagent: its `status`, and once it ended its `branch` and `result`, its last reply
-npx orchestration stop <id>      stop a subagent that is running
-npx orchestration land <id>      merge an ended subagent's branch into yours, then delete that branch
+npx @openagt/skill-orchestration@0.1 plan <file>    save the file as your plan; answers the `question` to ask the person
+npx @openagt/skill-orchestration@0.1 start --level <simple|hard> "<task>"
+                                                    start a subagent on the task; answers its id at once, without waiting for it
+npx @openagt/skill-orchestration@0.1 list           your subagents, newest first, as one JSON array
+npx @openagt/skill-orchestration@0.1 read <id>      one subagent: its `status`, and once it ended its `branch` and `result`, its last reply
+npx @openagt/skill-orchestration@0.1 stop <id>      stop a subagent that is running
+npx @openagt/skill-orchestration@0.1 land <id>      merge an ended subagent's branch into yours, then delete that branch
 ```
 
 A refusal exits 1 with a line on stderr saying why.
diff --git a/.agents/skills/plan-tickets/SKILL.md b/.agents/skills/plan-tickets/SKILL.md
index cd6f0fb74..629eb40d2 100644
--- a/.agents/skills/plan-tickets/SKILL.md
+++ b/.agents/skills/plan-tickets/SKILL.md
@@ -6,7 +6,7 @@ schedule:
   every: 6h
   waits-for: when a ticket that is not waiting, claimed, in review or queued has no plan, or an outdated one
   when: |-
-    npx tickets list | jq --argjson q "$(npx queue)" '[.[] | select(((.planned | not) or .outdated) and .pr == null and (.waiting | not) and (.locked | not) and ((.file | rtrimstr(".md")) as $s | $q | any(contains($s)) | not)) | .file]'
+    npx @openagt/skill-tickets@0.1 list | jq --argjson q "$(npx @openagt/skill-queue@0.1)" '[.[] | select(((.planned | not) or .outdated) and .pr == null and (.waiting | not) and (.locked | not) and ((.file | rtrimstr(".md")) as $s | $q | any(contains($s)) | not)) | .file]'
 ---
 
 Queue plans for the tickets that need one. Nobody will answer you: never ask, decide yourself. You only queue work, you never do it: write no plan yourself, the only thing you change is the queue.
diff --git a/.agents/skills/post-merge-cleanup/SKILL.md b/.agents/skills/post-merge-cleanup/SKILL.md
index b7464c756..8df0f0abc 100644
--- a/.agents/skills/post-merge-cleanup/SKILL.md
+++ b/.agents/skills/post-merge-cleanup/SKILL.md
@@ -6,7 +6,7 @@ schedule:
   every: 1h
   waits-for: when a pull request merged since the last clean-up has no clean-up yet
   when: |-
-    gh pr list --state merged --limit 50 --json number,body --search "merged:>=$(npx logs --limit 200 | jq -r '[.[] | select(.intent == "/post-merge-cleanup" and .status == "done")][0].startedAt // (now - 86400 | todate)')" | jq '[.[] | select(.body | contains("Post-merge cleanup done.") | not) | .number]'
+    gh pr list --state merged --limit 50 --json number,body --search "merged:>=$(npx @openagt/skill-logs@0.1 --limit 200 | jq -r '[.[] | select(.intent == "/post-merge-cleanup" and .status == "done")][0].startedAt // (now - 86400 | todate)')" | jq '[.[] | select(.body | contains("Post-merge cleanup done.") | not) | .number]'
 ---
 
 Write what merged work decided and taught into the project's knowledge files. Nobody will answer you: never ask, decide yourself.
diff --git a/.agents/skills/queue/SKILL.md b/.agents/skills/queue/SKILL.md
index a3337a5fb..c77b51c15 100644
--- a/.agents/skills/queue/SKILL.md
+++ b/.agents/skills/queue/SKILL.md
@@ -7,22 +7,22 @@ description: Where the project's agent queue lives, how to read it and change it
 
 The agent queue (`TODO_AGENTS.md`) lives on the branch `agent-data`, never on a code branch; your checkout does not contain it. It lists every task agents will work on next, in the order they will be taken.
 
-Read and change it with the `queue` command, a dependency of this repository (`@openagt/skill-queue`), run as `npx queue`. When that fails for a missing `node_modules`, install with the lockfile's package manager (`npm install` for `package-lock.json`) and run it again. Every change it makes is one commit on the `agent-data` branch, pushed straight to the remote when the project shares its records. The command's `--local` and `--full` flags are for the dashboard that shows the queue; never use them. A refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage.
+Read and change it with the `queue` command, always run by its full name: `npx @openagt/skill-queue@0.1`. Every change it makes is one commit on the `agent-data` branch, pushed straight to the remote when the project shares its records. The command's `--local` and `--full` flags are for the dashboard that shows the queue; never use them. A refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage.
 
 ## Read
 
 ```
-npx queue                        the open entries, in order of work, as one JSON array
+npx @openagt/skill-queue@0.1                        the open entries, in order of work, as one JSON array
 ```
 
 ## Change
 
 ```
-npx queue add <text> [--priority N]
-                                 put an entry on the queue; --priority (0-10) places it at the end of
-                                 that section; without it, the entry goes at the end of the file
-npx queue done <entry>           remove an entry: one quoted argument, exactly as `npx queue`
-                                 printed it; done means deleted
+npx @openagt/skill-queue@0.1 add <text> [--priority N]
+                                                    put an entry on the queue; --priority (0-10) places it at the end of
+                                                    that section; without it, the entry goes at the end of the file
+npx @openagt/skill-queue@0.1 done <entry>           remove an entry: one quoted argument, exactly as `npx @openagt/skill-queue@0.1`
+                                                    printed it; done means deleted
 ```
 
 ## Format
@@ -44,4 +44,4 @@ npx queue done <entry>           remove an entry: one quoted argument, exactly a
 ...
 ```
 
-The queue lists *all* tasks AI will work on next, sorted by priority. Priority 10 is rarely used (e.g. critical production bugs) and is treated as the utmost priority. Within a priority, the first tasks have higher priority (they are the "next" tasks within that "priority queue"). A done entry is removed (`npx queue done`).
+The queue lists *all* tasks AI will work on next, sorted by priority. Priority 10 is rarely used (e.g. critical production bugs) and is treated as the utmost priority. Within a priority, the first tasks have higher priority (they are the "next" tasks within that "priority queue"). A done entry is removed (`npx @openagt/skill-queue@0.1 done`).
diff --git a/.agents/skills/tickets/SKILL.md b/.agents/skills/tickets/SKILL.md
index 395fef716..495844b36 100644
--- a/.agents/skills/tickets/SKILL.md
+++ b/.agents/skills/tickets/SKILL.md
@@ -7,48 +7,48 @@ description: Where the project's tickets live, how to read and change them, how
 
 The tickets (`tickets/<DATE>_<SLUG>.md`, with their `.plan.md` and `.lock.md` siblings) live on the branch `agent-data`, never on a code branch. A `tickets` link at the repository root, if present, is a possibly stale copy: never write there.
 
-Read and change them with the `tickets` command, a dependency of this repository (`@openagt/skill-tickets`), run as `npx tickets`. When that fails for a missing `node_modules`, install with the lockfile's package manager (`npm install` for `package-lock.json`) and run it again. Every change it makes is one commit on the `agent-data` branch, pushed straight to the remote when the project shares its records. Never pass `--local` or `--force`: they are a person's.
+Read and change them with the `tickets` command, always run by its full name: `npx @openagt/skill-tickets@0.1`. Every change it makes is one commit on the `agent-data` branch, pushed straight to the remote when the project shares its records. Never pass `--local` or `--force`: they are a person's.
 
 Every command prints one JSON document; a refusal is `{"ok":false,"reason":…}` with why on stderr, exit 1; a wrong command line prints the usage on stderr, nothing on stdout, exit 2. Every `<file>` below is a ticket's filename (`2042-01-01_some-ticket.md`) or the `tickets/…` path a queue entry links to; `put` also takes the ticket's `.plan.md` and `meta.json`.
 
 ## Read
 
 ```
-npx tickets list                 every open ticket, as one JSON array; a row: file, title, summary, date,
-                                 planned, and when set priority, topics, issue, pr (set: the ticket is in
-                                 review), waiting (what it waits on), effort, uncertainty, outdated (the
-                                 plan says so), locked, lockedBy
-npx tickets show <file>          one ticket: its text, its plan, who holds it
-npx tickets meta                 when the tickets last caught up with the issue tracker:
-                                 {"lastImportedAt": <ISO 8601>}, or {} when no import was recorded
+npx @openagt/skill-tickets@0.1 list                 every open ticket, as one JSON array; a row: file, title, summary, date,
+                                                    planned, and when set priority, topics, issue, pr (set: the ticket is in
+                                                    review), waiting (what it waits on), effort, uncertainty, outdated (the
+                                                    plan says so), locked, lockedBy
+npx @openagt/skill-tickets@0.1 show <file>          one ticket: its text, its plan, who holds it
+npx @openagt/skill-tickets@0.1 meta                 when the tickets last caught up with the issue tracker:
+                                                    {"lastImportedAt": <ISO 8601>}, or {} when no import was recorded
 ```
 
 ## Change
 
 ```
-npx tickets put <file>           write one whole file under tickets/ from stdin, creating it if new
-                                 (npx tickets put <file> < draft.md): a ticket, its plan, or meta.json
-                                 holding the object meta shows
-npx tickets close <file>         when the ticket is not wanted, when its work is done with no pull
-                                 request to merge, or for the tracker update once its pull request merged:
-                                 remove the ticket with its plan and claim; refused while someone else
-                                 holds it; its queue entry, if any, stays: `npx queue done` it
+npx @openagt/skill-tickets@0.1 put <file>           write one whole file under tickets/ from stdin, creating it if new
+                                                    (npx @openagt/skill-tickets@0.1 put <file> < draft.md): a ticket, its plan, or meta.json
+                                                    holding the object meta shows
+npx @openagt/skill-tickets@0.1 close <file>         when the ticket is not wanted, when its work is done with no pull
+                                                    request to merge, or for the tracker update once its pull request merged:
+                                                    remove the ticket with its plan and claim; refused while someone else
+                                                    holds it; its queue entry, if any, stays: `npx @openagt/skill-queue@0.1 done` it
 ```
 
 ## Claim before you plan or work a ticket
 
 ```
-npx tickets claim <file>         {"ok":true,"file":…,"holder":…,"earlier":[…]}: the ticket is yours;
-                                 earlier: who claimed it before you, newest first, each a run's id or
-                                 a branch; read what they did before you start
-                                 {"ok":false,"reason":"claimed","holder":…}: someone else's: pick another,
-                                 and never remove or overwrite their claim
-npx tickets release <file>       lift your own claim when the plan or the work is done, and before you
-                                 stop unless you closed the ticket: nothing lifts a claim on a timeout
-                                 {"ok":true,"file":…,"holder":…}: your claim is lifted
-                                 {"ok":false,"reason":"no-lock"}: nobody holds it: nothing to lift
-                                 {"ok":false,"reason":"not-holder","holder":…}: someone else holds it:
-                                 leave their claim
+npx @openagt/skill-tickets@0.1 claim <file>         {"ok":true,"file":…,"holder":…,"earlier":[…]}: the ticket is yours;
+                                                    earlier: who claimed it before you, newest first, each a run's id or
+                                                    a branch; read what they did before you start
+                                                    {"ok":false,"reason":"claimed","holder":…}: someone else's: pick another,
+                                                    and never remove or overwrite their claim
+npx @openagt/skill-tickets@0.1 release <file>       lift your own claim when the plan or the work is done, and before you
+                                                    stop unless you closed the ticket: nothing lifts a claim on a timeout
+                                                    {"ok":true,"file":…,"holder":…}: your claim is lifted
+                                                    {"ok":false,"reason":"no-lock"}: nobody holds it: nothing to lift
+                                                    {"ok":false,"reason":"not-holder","holder":…}: someone else holds it:
+                                                    leave their claim
 ```
 
 `put` ignores claims. You claim as `AGENT_ID` when it is set and not blank, else as your current branch: release from the branch you claimed on, or the claim stays until a person lifts it.
@@ -58,10 +58,10 @@ npx tickets release <file>       lift your own claim when the plan or the work i
 When the repository has the `queue` skill, a ticket goes on the agent queue as a link, its title as the label, at the ticket's own `Priority:` (5 when it has none):
 
 ```
-npx queue add '[<title>](tickets/<file>)' --priority <N>
+npx @openagt/skill-queue@0.1 add '[<title>](tickets/<file>)' --priority <N>
 ```
 
-Once the work is committed and its pull request is open: `npx queue done` the entry, its exact text, write the pull request into the ticket as its `PR:` line (`put` the whole ticket, the line added above the title), and release your claim. The ticket is in review. Do not close it: it closes when the pull request merges, through the update from the issue tracker, which reads the line `Closes tickets/<file>` in the pull request's body; add `Closes #<number>` when the ticket has an issue.
+Once the work is committed and its pull request is open: `npx @openagt/skill-queue@0.1 done` the entry, its exact text, write the pull request into the ticket as its `PR:` line (`put` the whole ticket, the line added above the title), and release your claim. The ticket is in review. Do not close it: it closes when the pull request merges, through the update from the issue tracker, which reads the line `Closes tickets/<file>` in the pull request's body; add `Closes #<number>` when the ticket has an issue.
 
 ## Formats
 
diff --git a/.agents/skills/triage/SKILL.md b/.agents/skills/triage/SKILL.md
index d9196b573..a1072b5d2 100644
--- a/.agents/skills/triage/SKILL.md
+++ b/.agents/skills/triage/SKILL.md
@@ -7,12 +7,12 @@ schedule:
     every: 6h
     waits-for: when a planned ticket is a quick win and is not waiting, claimed, in review or queued
     when: |-
-      npx tickets list | jq --argjson q "$(npx queue)" '[.[] | select(.planned and .pr == null and (.waiting | not) and (.locked | not) and (.outdated | not) and .effort != null and .uncertainty != null and .effort <= 2 and .uncertainty <= 2 and (.file as $f | $q | any(contains($f)) | not)) | .file]'
+      npx @openagt/skill-tickets@0.1 list | jq --argjson q "$(npx @openagt/skill-queue@0.1)" '[.[] | select(.planned and .pr == null and (.waiting | not) and (.locked | not) and (.outdated | not) and .effort != null and .uncertainty != null and .effort <= 2 and .uncertainty <= 2 and (.file as $f | $q | any(contains($f)) | not)) | .file]'
   - word: consensual
     every: 7d
     waits-for: when a planned ticket is consensual work and is not waiting, claimed, in review or queued
     when: |-
-      npx tickets list | jq --argjson q "$(npx queue)" '[.[] | select(.planned and .pr == null and (.waiting | not) and (.locked | not) and (.outdated | not) and .effort != null and .uncertainty != null and .uncertainty <= 3 and (.effort > 2 or .uncertainty > 2) and (.file as $f | $q | any(contains($f)) | not)) | .file]'
+      npx @openagt/skill-tickets@0.1 list | jq --argjson q "$(npx @openagt/skill-queue@0.1)" '[.[] | select(.planned and .pr == null and (.waiting | not) and (.locked | not) and (.outdated | not) and .effort != null and .uncertainty != null and .uncertainty <= 3 and (.effort > 2 or .uncertainty > 2) and (.file as $f | $q | any(contains($f)) | not)) | .file]'
 ---
 
 Choose work for the agent queue. Nobody will answer you: never ask, decide yourself. You only queue work, you never do it: the only thing you change is the queue. The word after the command is the mode: `quick`, `consensual`, or nothing for both.
diff --git a/.agents/skills/update-tickets/SKILL.md b/.agents/skills/update-tickets/SKILL.md
index 1620cf5a1..590e423bf 100644
--- a/.agents/skills/update-tickets/SKILL.md
+++ b/.agents/skills/update-tickets/SKILL.md
@@ -6,7 +6,7 @@ schedule:
   every: 15m
   waits-for: when an issue changed or a pull request that closes a ticket merged since the last import, or nothing was imported yet
   when: |-
-    { gh issue list --state all --limit 1 --json number --search "updated:>=$(npx tickets meta | jq -r .lastImportedAt)"; gh pr list --state merged --limit 100 --json number,body --search "merged:>=$(npx tickets meta | jq -r .lastImportedAt)" | jq '[.[] | select(.body | test("(?m)^Closes tickets/\\w")) | {number}]'; npx tickets meta | jq --argjson t "$(npx tickets list)" '[select(.lastImportedAt == null and ($t | length) == 0) | "first import"]'; } | jq -s add
+    { gh issue list --state all --limit 1 --json number --search "updated:>=$(npx @openagt/skill-tickets@0.1 meta | jq -r .lastImportedAt)"; gh pr list --state merged --limit 100 --json number,body --search "merged:>=$(npx @openagt/skill-tickets@0.1 meta | jq -r .lastImportedAt)" | jq '[.[] | select(.body | test("(?m)^Closes tickets/\\w")) | {number}]'; npx @openagt/skill-tickets@0.1 meta | jq --argjson t "$(npx @openagt/skill-tickets@0.1 list)" '[select(.lastImportedAt == null and ($t | length) == 0) | "first import"]'; } | jq -s add
 ---
 
 Bring the tickets up to date with the project's issue tracker and its merged pull requests. Nobody will answer you: never ask, decide yourself.
diff --git a/.agents/skills/work-queue/SKILL.md b/.agents/skills/work-queue/SKILL.md
index c15acd86b..6c4da1190 100644
--- a/.agents/skills/work-queue/SKILL.md
+++ b/.agents/skills/work-queue/SKILL.md
@@ -5,7 +5,7 @@ disable-model-invocation: true
 schedule:
   waits-for: when the queue holds a task nobody has claimed
   when: |-
-    npx queue | jq --argjson t "$(npx tickets list)" '[.[] | . as $e | select($t | any(.[]; .locked and ((.file | rtrimstr(".md")) as $s | $e | contains($s))) | not)]'
+    npx @openagt/skill-queue@0.1 | jq --argjson t "$(npx @openagt/skill-tickets@0.1 list)" '[.[] | . as $e | select($t | any(.[]; .locked and ((.file | rtrimstr(".md")) as $s | $e | contains($s))) | not)]'
 ---
 
 Work one task off the project's agent queue. Nobody will answer you: never ask, decide yourself.
diff --git a/packages/agent-scheduler/DECISIONS.md b/packages/agent-scheduler/DECISIONS.md
index 5e05db892..4e3a81d4b 100644
--- a/packages/agent-scheduler/DECISIONS.md
+++ b/packages/agent-scheduler/DECISIONS.md
@@ -50,7 +50,7 @@ already made, and lists it in its pull request; for anything else it proposes an
   branch head (every commit was a start, most of them empty), over the tool reading the
   queue (the tool would know a skill), and over a bare clock (empty runs). A `schedule` the
   tool cannot read is skipped and named, never guessed.
-- A skill's check may name the commands of other skills (`npx queue`, `npx tickets`),
+- A skill's check may name the commands of other skills (the queue's, the tickets'),
   though the words a command skill gives the agent name none. The scheduler runs the check;
   the agent is never given the shell line, only what it printed. Picked over keeping the
   checks in a file of the project, away from the skill they belong to.
diff --git a/packages/agent-scheduler/package.json b/packages/agent-scheduler/package.json
index bd116426f..198a1cede 100644
--- a/packages/agent-scheduler/package.json
+++ b/packages/agent-scheduler/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/agent-scheduler",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "Start coding agents on a schedule: a project's skills say which commands can run on a schedule, each with its check, its pace and how many at once, and each person switches them on for their own machine; the scheduler pulls the project's agent-data branch, checks, and asks agent-runner to run one agent per due command; and it brings the dashboard's Automations page, where a person switches each scheduled command, sets its pace and how many agents work on it at once, and picks how far its runs publish, the Scheduler section of its Settings page, the Scheduler card of its Overview and the stop line on its usage bar.",
   "license": "MIT",
   "repository": {
diff --git a/packages/agent-scheduler/src/schedule.ts b/packages/agent-scheduler/src/schedule.ts
index a81e7511f..544113faa 100644
--- a/packages/agent-scheduler/src/schedule.ts
+++ b/packages/agent-scheduler/src/schedule.ts
@@ -16,7 +16,7 @@ import { parseInterval, type Interval } from './pace.js'
  *     disable-model-invocation: true
  *     schedule:
  *       every: 15m
- *       when: npx tickets meta | jq …
+ *       when: npx @openagt/skill-tickets@0.1 meta | jq …
  *       waits-for: when an issue changed since the last import
  *     ---
  *
@@ -385,7 +385,7 @@ export function promptCommand(prompt: string, schedule: Schedule): string | unde
 /**
  * Whether a check's output says the command is due (#1774): the output parsed as JSON is
  * something other than empty — `[]`, `{}`, `null`, `false`, `""`, `0` and no output at all are not
- * due. Every skill command prints JSON on stdout, so a check like `npx queue` needs no piping.
+ * due. Every skill command prints JSON on stdout, so a check like `npx @openagt/skill-queue@0.1` needs no piping.
  * Output that is not JSON counts by its text: anything non-blank is due.
  */
 export function isDue(stdout: string): boolean {
diff --git a/packages/openagent/src/project-modules.ts b/packages/openagent/src/project-modules.ts
index e86252ebe..abf781a5e 100644
--- a/packages/openagent/src/project-modules.ts
+++ b/packages/openagent/src/project-modules.ts
@@ -110,7 +110,7 @@ const MAX_ARG_LENGTH = 4096
 /**
  * Run one of a module package's own commands in the project, with the given arguments, and read
  * its standard output as JSON. This is how a module reads its data: the same command an agent runs
- * (`npx logs`), so the module and the agent see the same thing and OpenAgent knows neither.
+ * (`npx @openagt/skill-logs@0.1`), so the module and the agent see the same thing and OpenAgent knows neither.
  *
  * `command` picks one of the package's commands; a package with exactly one needs none. The
  * command runs with Node (a package's commands are Node scripts), in the project root, never
diff --git a/packages/skill-branches/DECISIONS.md b/packages/skill-branches/DECISIONS.md
index 829f9b94d..a9bf007e5 100644
--- a/packages/skill-branches/DECISIONS.md
+++ b/packages/skill-branches/DECISIONS.md
@@ -19,14 +19,15 @@ already made, and lists it in its pull request; for anything else it proposes an
 - The repository's exclude file hides `.branches/` from the first checkout on: an
   untracked folder at the root would ride a sweeping `git add -A` onto a code branch, and
   `.gitignore` is tracked.
-- A checkout starts as branch `agent-<id>` in folder `.branches/agent-<id>/`; `<id>` comes
-  from the program that starts the agent, and must match `[A-Za-z0-9_-]+`, so no id can
-  build a path outside `.branches/`. `npx branches name <name>` (`[a-z0-9-]+`; the skill
-  asks for a leading letter or digit: at the command line a leading `-` reads as a flag, a
-  usage error, and the name check itself does not mind it) renames the branch to
-  `agent-<name>`: a rename, not a new branch, so nothing is left behind; the folder keeps
-  the id, since the agent is running inside it. A checkout on no branch is neither renamed
-  nor reclaimed; `status` answers it without a `branch`.
+- A checkout starts as branch `agent-<id>` in folder `.branches/agent-<id>/`; `<id>`
+  comes from the program that starts the agent, and must match `[A-Za-z0-9_-]+`, so no
+  id can build a path outside `.branches/`.
+  `npx @openagt/skill-branches@0.1 name <name>` (`[a-z0-9-]+`; the skill asks for a
+  leading letter or digit: at the command line a leading `-` reads as a flag, a usage
+  error, and the name check itself does not mind it) renames the branch to
+  `agent-<name>`: a rename, not a new branch, so nothing is left behind; the folder
+  keeps the id, since the agent is running inside it. A checkout on no branch is neither
+  renamed nor reclaimed; `status` answers it without a `branch`.
 - After a checkout is made, and after the command names or removes one, each checkout
   whose branch differs from its folder name gets a sibling link `.branches/<branch>` to
   its folder, relative; a detached checkout or a slashed branch gets none. A link whose
@@ -108,10 +109,10 @@ ending.
   the package opening the request itself, which put the git host's tool inside the git skill
   and made another git host a change to this package.
 - The agent pushes its branch only when asked to publish, by its task or by the person:
-  `npx branches push`, once its checkout is clean. Until then its work stays on this
-  machine. Pushing when it finishes was the earlier rule and was dropped: a branch on the
-  remote is in front of everyone who watches the repository, and that is the person's
-  act. Picked over whoever started the agent pushing for it.
+  `npx @openagt/skill-branches@0.1 push`, once its checkout is clean. Until then its
+  work stays on this machine. Pushing when it finishes was the earlier rule and was
+  dropped: a branch on the remote is in front of everyone who watches the repository,
+  and that is the person's act. Picked over whoever started the agent pushing for it.
 - A person pushes a finished agent's branch through the same `push`, by name
   (`--branch`): the checkout on it under the agent's clean rule, else the branch itself,
   pushed when this machine has it and left as it is when only origin has it. Picked over
@@ -136,14 +137,16 @@ ending.
 - The command has a second caller, the dashboard, for `list`, `show`, `push --branch` and
   `remove`, declared as the project's branches provider
   (`"openagent": { "branches": "branches" }`).
-- Before its first change the agent names its session, saying what the work is, unless its
-  branch already differs from its folder name, as a continued agent's does: it is already
-  named. The agent finishes only when `npx branches status` reports the checkout clean, or
-  after saying what remains is not its own; an agent that needs anything outside its
-  checkout stops and says so.
-- The skill says: when `node_modules` is missing, install with the lockfile's package
-  manager, then `npx branches`, never a bare `branches`: on a fresh clone no such command
-  exists yet.
+- Before its first change the agent names its session, saying what the work is, unless
+  its branch already differs from its folder name, as a continued agent's does: it is
+  already named. The agent finishes only when `npx @openagt/skill-branches@0.1 status`
+  reports the checkout clean, or after saying what remains is not its own; an agent that
+  needs anything outside its checkout stops and says so.
+- The skill calls the command by its full name and a version range,
+  `npx @openagt/skill-branches@0.1`: the name is ours on npm, so no other package can
+  run under it, and nothing is installed in the project. Picked over `npx branches` with
+  the package as a dependency of the project, which ran whatever package holds that name
+  on npm where the install was missing, and which a project without Node could not have.
 - Every command that runs prints one JSON document on stdout: the result or the refusal. A
   refusal (a rule saying no) adds one line for a person on stderr and exits 1. A malformed
   command line (an unknown flag, the wrong argument count) never gets that far: the usage
@@ -165,12 +168,14 @@ ending.
   `agent-<name>` branch with git before its first change, another name if that one exists
   locally or on origin. `status`, `name` and a bare `push` are the agent's commands; the
   rest are the caller's.
-- Every checkout holds the package's own command, linked as `node_modules/.bin/branches` and
-  hidden through the repository's exclude, unless the project installed its own copy. The
-  skill says `npx branches`, and in a project with nothing installed `npx` would otherwise
-  download whatever package holds that name on npm and run it. Picked over telling the agent
-  to install first, which an empty project cannot do, and over a bare `branches` in the
-  skill, which a fresh clone on another machine does not have.
+- Every checkout holds the package's command and the package itself, linked as
+  `node_modules/.bin/branches` and `node_modules/@openagt/skill-branches` and hidden
+  through the repository's exclude, unless the project installed its own copy. `npx`
+  runs a copy of the package it finds in the checkout, by the command's name, so the
+  skill's full name runs the copy that made the checkout, with nothing downloaded and no
+  network. Beside another tool that holds the name `branches` in the project the package
+  is not linked, and the full name is left to npm. Picked over leaving the full name to
+  npm alone, which takes a second a call and fails where the network is down.
 - Each agent tool (Claude Code, Codex) looks for skills in its own folder at the checkout
   root: `.claude/skills`, `.agents/skills`. In every checkout it makes, the package links
   its own folder, which holds `SKILL.md`, into both as `branches`, hidden through the
diff --git a/packages/skill-branches/SKILL.md b/packages/skill-branches/SKILL.md
index 51fe1a768..113ae06db 100644
--- a/packages/skill-branches/SKILL.md
+++ b/packages/skill-branches/SKILL.md
@@ -9,12 +9,12 @@ Your work goes on a branch named `agent-<name>`, unless whoever started you cont
 
 ## The command
 
-`branches` is a dependency of this repository (`@openagt/skill-branches`). If `node_modules` is missing, install with the lockfile's package manager (`npm install` for `package-lock.json`). Then run `npx branches` inside your checkout, never a bare `branches`: a fresh clone has none. `status`, `name` and `push` (with no flag) are yours; the rest are the caller's.
+Run the `branches` command inside your checkout, always by its full name: `npx @openagt/skill-branches@0.1`. `status`, `name` and `push` (with no flag) are yours; the rest are the caller's.
 
 ## Where you are
 
 ```
-npx branches status
+npx @openagt/skill-branches@0.1 status
 ```
 
 It prints JSON; `branch` is the branch you are on.
@@ -24,7 +24,7 @@ It prints JSON; `branch` is the branch you are on.
 Before your first change, name the session with `[a-z0-9-]+`, starting with a letter or digit, saying what the work is, unless your branch already differs from `path`'s last segment: then it is named, keep it.
 
 ```
-npx branches name <name>
+npx @openagt/skill-branches@0.1 name <name>
 ```
 
 It renames your branch to `agent-<name>` and prints it in `branch`: `agent-<name>-2`, `-3`, … when `<name>` was taken; a name outside `[a-z0-9-]+` is refused as `invalid-name`.
@@ -44,7 +44,7 @@ Nothing is committed for you.
 ## Before you finish
 
 ```
-npx branches status
+npx @openagt/skill-branches@0.1 status
 ```
 
 It must report `"clean": true`. `clean` is false while anything is uncommitted or untracked: commit or delete what you added; if what remains is not yours, say so and finish.
@@ -54,7 +54,7 @@ It must report `"clean": true`. `clean` is false while anything is uncommitted o
 Only when your task or the person asks you to push or publish your work, and once clean:
 
 ```
-npx branches push
+npx @openagt/skill-branches@0.1 push
 ```
 
 It pushes your branch to origin and prints it in `branch`. `clean` false is refused as `dirty`: commit or delete first.
@@ -64,7 +64,7 @@ It pushes your branch to origin and prints it in `branch`. `clean` false is refu
 Only when the person asks you to merge your work into the project's main branch, and once clean:
 
 ```
-npx branches merge <your branch>
+npx @openagt/skill-branches@0.1 merge <your branch>
 ```
 
 It merges your branch into the main branch, in the project's own folder. A conflict changes nothing and names the files in `files`: say so and stop. Your checkout and your branch stay.
diff --git a/packages/skill-branches/package.json b/packages/skill-branches/package.json
index fa2c48686..9f4b01d9d 100644
--- a/packages/skill-branches/package.json
+++ b/packages/skill-branches/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-branches",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "Branch management for coding agents: one git checkout per agent under .branches/, named as its branch, reclaimed once its work is on the remote.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-branches/src/checkout.ts b/packages/skill-branches/src/checkout.ts
index 438275b41..b257590c5 100644
--- a/packages/skill-branches/src/checkout.ts
+++ b/packages/skill-branches/src/checkout.ts
@@ -46,8 +46,8 @@ export async function attachCheckout(
  * directory at the root, `.branches/` would ride any sweeping `git add -A` onto a code branch —
  * through the repository's own exclude file, so no tracked file changes; `node_modules` is
  * gitignored, so a fresh checkout has none and a link that cannot be made is a worse run, not a
- * failed one; the package's own command is linked into a checkout that has none, so the skill's
- * `npx branches` runs it and downloads nothing (`command-link.ts`); a link under `.branches/` is a view, and the next reconcile pass makes it.
+ * failed one; the package and its command are linked into a checkout that has neither, so the skill's
+ * `npx @openagt/skill-branches@0.1` runs this copy and downloads nothing (`command-link.ts`); a link under `.branches/` is a view, and the next reconcile pass makes it.
  */
 async function settle(repo: string, path: string, git: GitRunner, skills: readonly SkillLink[] = []): Promise<void> {
   await excludeFromGit(repo, `/${BRANCHES_DIR}`, undefined, git).catch(() => {})
diff --git a/packages/skill-branches/src/cleanup.test.ts b/packages/skill-branches/src/cleanup.test.ts
index 71b41062a..b4cc9e06a 100644
--- a/packages/skill-branches/src/cleanup.test.ts
+++ b/packages/skill-branches/src/cleanup.test.ts
@@ -79,7 +79,7 @@ test('cleanup: checkouts go under the reclaim rule; uncommitted work, branches w
     assert.equal(await readlink(join(repo, '.branches', 'agent-fix-title')), 'agent-dirty', 'the kept checkout keeps its link')
     assert.ok((await branches(repo)).includes(work!), 'the branch with work on it stays, at the same commit')
     const hidden = await excludeOf(repo)
-    for (const rule of ['/.branches', '/node_modules/.bin/branches', '/.claude/skills/branches', '/.agents/skills/branches']) {
+    for (const rule of ['/.branches', '/node_modules/@openagt/skill-branches', '/node_modules/.bin/branches', '/.claude/skills/branches', '/.agents/skills/branches']) {
       assert.ok(hidden.split('\n').includes(rule), `${rule} still hides what a kept checkout holds`)
     }
     assert.equal(await outside(repo), before)
@@ -121,7 +121,7 @@ test('cleanup: the rules are the repository\'s: they stay while another checkout
   const { base, repo } = await project()
   try {
     // The same rules written by hand, in a project the tool never worked in.
-    const byHand = '/.branches\n/node_modules/.bin/branches\n/.claude/skills/branches\n/.agents/skills/branches\n'
+    const byHand = '/.branches\n/node_modules/@openagt/skill-branches\n/node_modules/.bin/branches\n/.claude/skills/branches\n/.agents/skills/branches\n'
     await writeFile(join(repo, '.git', 'info', 'exclude'), byHand)
     assert.deepEqual((await run(repo, 'cleanup')).out, { ok: true, removed: [], kept: [] })
     assert.equal(await excludeOf(repo), byHand)
diff --git a/packages/skill-branches/src/cleanup.ts b/packages/skill-branches/src/cleanup.ts
index 268b83164..d2bebe2de 100644
--- a/packages/skill-branches/src/cleanup.ts
+++ b/packages/skill-branches/src/cleanup.ts
@@ -3,7 +3,7 @@ import { basename, dirname, join } from 'node:path'
 import { BRANCHES_DIR, nodeGitRunner, repositoryCheckouts, unexcludeFromGit, type GitRunner } from '@openagt/agent-data'
 import { reconcileBranchLinks } from './branch-links.js'
 import { isAgentBranch } from './branch-names.js'
-import { COMMAND } from './command-link.js'
+import { COMMAND_LINKS } from './command-link.js'
 import { HARNESS_SKILL_DIRS, SKILL_NAME } from './skill-links.js'
 import { worktreeDirEntries } from './worktree.js'
 
@@ -70,7 +70,7 @@ export async function cleanup(repo: string, reclaimOne: (agentId: string) => Pro
     if (checkouts) {
       // A link lives in an agent's checkout: with none left in the repository, the rules hide nothing.
       if (!kept.some(entry => isAgentBranch(basename(entry.path))) && !checkouts.some(path => basename(dirname(path)) === BRANCHES_DIR && isAgentBranch(basename(path)))) {
-        for (const rule of [`/node_modules/.bin/${COMMAND}`, ...HARNESS_SKILL_DIRS.map(skills => `/${skills}/${SKILL_NAME}`)]) {
+        for (const rule of [...COMMAND_LINKS.map(link => `/${link}`), ...HARNESS_SKILL_DIRS.map(skills => `/${skills}/${SKILL_NAME}`)]) {
           await unexcludeFromGit(repo, rule, undefined, git).catch(() => {})
         }
       }
diff --git a/packages/skill-branches/src/command-link.test.ts b/packages/skill-branches/src/command-link.test.ts
index 819bfbfe0..29c9f15a7 100644
--- a/packages/skill-branches/src/command-link.test.ts
+++ b/packages/skill-branches/src/command-link.test.ts
@@ -3,7 +3,7 @@ import { test } from 'node:test'
 import { execFile } from 'node:child_process'
 import { promisify } from 'node:util'
 import { join } from 'node:path'
-import { mkdir, mkdtemp, realpath, rm, writeFile } from 'node:fs/promises'
+import { lstat, mkdir, mkdtemp, readFile, realpath, rm, writeFile } from 'node:fs/promises'
 import { tmpdir } from 'node:os'
 import { nodeGitRunner } from '@openagt/agent-data'
 import { CLI_BIN_DIR } from './bin-dir.js'
@@ -12,6 +12,7 @@ import { linkOwnCommand } from './command-link.js'
 
 const git = nodeGitRunner()
 const run = promisify(execFile)
+const exists = (path: string): Promise<boolean> => lstat(path).then(() => true, () => false)
 
 async function repoWithOneCommit(files: Record<string, string> = {}): Promise<string> {
   const repo = await realpath(await mkdtemp(join(tmpdir(), 'command-link-')))
@@ -33,9 +34,21 @@ test('a checkout in a project with nothing installed holds the command, hidden f
     // The command found in the checkout is this package's: it answers the checkout's own status.
     const { stdout } = await run(link, ['status'], { cwd: path })
     assert.equal(JSON.parse(stdout).path, path)
+    // The package is there too, so the skill's full name finds this copy: `npx` asks npm for nothing.
+    const pkg = join(path, 'node_modules', '@openagt', 'skill-branches')
+    assert.equal(await realpath(pkg), await realpath(join(CLI_BIN_DIR, '..')))
+    const manifest = JSON.parse(await readFile(join(pkg, 'package.json'), 'utf8'))
+    assert.equal(manifest.name, '@openagt/skill-branches')
+    // The range the skill's text names: a copy outside it would send `npx` to npm.
+    assert.match(manifest.version, /^0\.1\.\d+$/)
+    assert.match(await readFile(join(pkg, 'SKILL.md'), 'utf8'), /npx @openagt\/skill-branches@0\.1 status/)
+    // `npx` itself, kept off the network: with the full name it finds this copy and runs it.
+    const viaNpx = await run('npx', ['--offline', '--yes', '@openagt/skill-branches@0.1', 'status'], { cwd: path })
+    assert.equal(JSON.parse(viaNpx.stdout).path, path)
     // Linking again changes nothing.
     await linkOwnCommand(repo, path)
     assert.equal(await realpath(link), await realpath(join(CLI_BIN_DIR, 'branches')))
+    assert.equal(await realpath(pkg), await realpath(join(CLI_BIN_DIR, '..')))
   } finally {
     await rm(repo, { recursive: true, force: true })
   }
@@ -53,3 +66,49 @@ test("a project that installed its own copy keeps it: the checkout's command is
     await rm(repo, { recursive: true, force: true })
   }
 })
+
+test("a project that installed its own copy of the package keeps it: the checkout's package is the project's", async () => {
+  const repo = await repoWithOneCommit({ '.gitignore': 'node_modules/\n' })
+  try {
+    const own = join(repo, 'node_modules', '@openagt', 'skill-branches')
+    await mkdir(own, { recursive: true })
+    await writeFile(join(own, 'package.json'), '{"name":"@openagt/skill-branches","version":"9.9.9"}\n')
+    const { path } = await createCheckout(repo, { agentId: 'a3' })
+    const pkg = join(path, 'node_modules', '@openagt', 'skill-branches')
+    assert.equal(await realpath(pkg), await realpath(own))
+    // Linking again leaves the project's copy where it is.
+    await linkOwnCommand(repo, path)
+    assert.equal(await realpath(pkg), await realpath(own))
+  } finally {
+    await rm(repo, { recursive: true, force: true })
+  }
+})
+
+test('beside another tool that holds the command\'s name the package is not linked: the full name is left to npm', async () => {
+  const repo = await repoWithOneCommit({ '.gitignore': 'node_modules/\n' })
+  try {
+    await mkdir(join(repo, 'node_modules', '.bin'), { recursive: true })
+    await writeFile(join(repo, 'node_modules', '.bin', 'branches'), '#!/bin/sh\necho another tool\n', { mode: 0o755 })
+    const { path } = await createCheckout(repo, { agentId: 'a4' })
+    const { stdout } = await run(join(path, 'node_modules', '.bin', 'branches'), [], { cwd: path })
+    assert.equal(stdout.trim(), 'another tool')
+    // With the package linked, `npx @openagt/skill-branches@0.1` would run that other tool.
+    assert.equal(await exists(join(path, 'node_modules', '@openagt', 'skill-branches')), false)
+  } finally {
+    await rm(repo, { recursive: true, force: true })
+  }
+})
+
+test('a second checkout of a project with tools of its own gets the package too: the command the first one linked is this package\'s', async () => {
+  const repo = await repoWithOneCommit({ '.gitignore': 'node_modules/\n' })
+  try {
+    // The project's `.bin` is linked whole into a checkout, so the first checkout's command link lands in it.
+    await mkdir(join(repo, 'node_modules', '.bin'), { recursive: true })
+    await createCheckout(repo, { agentId: 'a5' })
+    const { path } = await createCheckout(repo, { agentId: 'a6' })
+    assert.equal(await realpath(join(path, 'node_modules', '.bin', 'branches')), await realpath(join(CLI_BIN_DIR, 'branches')))
+    assert.equal(await realpath(join(path, 'node_modules', '@openagt', 'skill-branches')), await realpath(join(CLI_BIN_DIR, '..')))
+  } finally {
+    await rm(repo, { recursive: true, force: true })
+  }
+})
diff --git a/packages/skill-branches/src/command-link.ts b/packages/skill-branches/src/command-link.ts
index 30ebd33c5..14f1aa8bf 100644
--- a/packages/skill-branches/src/command-link.ts
+++ b/packages/skill-branches/src/command-link.ts
@@ -1,36 +1,58 @@
-import { lstat, mkdir, symlink } from 'node:fs/promises'
-import { join } from 'node:path'
+import { lstat, mkdir, realpath, symlink } from 'node:fs/promises'
+import { dirname, join } from 'node:path'
 import { excludeFromGit, nodeGitRunner, type GitRunner } from '@openagt/agent-data'
 import { CLI_BIN_DIR } from './bin-dir.js'
 
 /**
- * This package's command, linked into a checkout that has none: `node_modules/.bin/branches`.
+ * This package's command, linked into a checkout that has none: its command at
+ * `node_modules/.bin/branches`, and the package itself at `node_modules/@openagt/skill-branches`.
  *
- * The skill tells the agent to run `npx branches`. In a project that depends on this package the
- * checkout already has the command, linked with the project's other tools. In a project with
- * nothing installed (an empty folder a dashboard added) it has none, and `npx` then downloads
- * whatever package holds the name `branches` on npm and runs it: a stranger's code, in the
- * person's project. With the command linked here `npx` finds it in the checkout and downloads
- * nothing.
+ * The skill tells the agent to run `npx @openagt/skill-branches@0.1`. `npx` looks for a copy of
+ * the package in the checkout, and asks npm for one otherwise; a copy it finds, it runs by the
+ * command's name from `node_modules/.bin`. In a project that depends on this package the checkout
+ * already has both, linked with the project's other tools. In a project with nothing installed (an
+ * empty folder a dashboard added) it has neither, so both are linked here: the agent then runs the
+ * very copy that made its checkout, with nothing downloaded and no network.
  *
- * Hidden from the project's git through the repository's exclude file, like the skill's link: the
- * link is the package's state, not the agent's work. Best-effort: a command already there (the
+ * The package is linked only beside this package's own command. Beside another tool that holds the
+ * name `branches` in the project, the full name would run that tool, so there it is left to npm.
+ *
+ * Hidden from the project's git through the repository's exclude file, like the skill's link: a
+ * link is the package's state, not the agent's work. Best-effort: an entry already there (the
  * project's own copy) is left alone, and a link that cannot be made is a worse run, not a failed
  * one.
  */
 
-/** The command's name, and where a checkout holds its tools. */
-export const COMMAND = 'branches'
-const BIN_DIR = 'node_modules/.bin'
+/** The command's name, where a checkout holds its tools, and where it holds this package. */
+const COMMAND = 'branches'
+const COMMAND_LINK = `node_modules/.bin/${COMMAND}`
+const PACKAGE_LINK = 'node_modules/@openagt/skill-branches'
+
+/** The command's script, and this package's directory, the one holding its `package.json`: beside `bin/`. */
+const COMMAND_FILE = join(CLI_BIN_DIR, COMMAND)
+const PACKAGE_DIR = dirname(CLI_BIN_DIR)
+
+/** The paths of the links, relative to a checkout: what the exclude file hides, and the rules a cleanup lifts. */
+export const COMMAND_LINKS: readonly string[] = [COMMAND_LINK, PACKAGE_LINK]
 
 export async function linkOwnCommand(repo: string, checkout: string, git: GitRunner = nodeGitRunner()): Promise<void> {
-  const link = join(checkout, BIN_DIR, COMMAND)
-  // lstat, not stat: a link that is there counts, whatever it points at.
-  if (await lstat(link).then(() => true, () => false)) return
-  await excludeFromGit(repo, `/${BIN_DIR}/${COMMAND}`, undefined, git).catch(() => {})
+  const command = join(checkout, COMMAND_LINK)
+  if (!(await entryExists(command))) await link(repo, checkout, COMMAND_LINK, COMMAND_FILE, 'file', git)
+  const ours = await realpath(command).then(async path => path === (await realpath(COMMAND_FILE)), () => false)
+  // 'junction' is the only directory-link type Windows grants without elevation; it is ignored on POSIX.
+  if (ours && !(await entryExists(join(checkout, PACKAGE_LINK)))) await link(repo, checkout, PACKAGE_LINK, PACKAGE_DIR, process.platform === 'win32' ? 'junction' : 'dir', git)
+}
+
+/** lstat, not stat: a link that is there counts, whatever it points at. */
+function entryExists(path: string): Promise<boolean> {
+  return lstat(path).then(() => true, () => false)
+}
+
+async function link(repo: string, checkout: string, path: string, target: string, type: 'file' | 'dir' | 'junction', git: GitRunner): Promise<void> {
+  await excludeFromGit(repo, `/${path}`, undefined, git).catch(() => {})
   try {
-    await mkdir(join(checkout, BIN_DIR), { recursive: true })
-    await symlink(join(CLI_BIN_DIR, COMMAND), link)
+    await mkdir(dirname(join(checkout, path)), { recursive: true })
+    await symlink(target, join(checkout, path), type)
   } catch {
     // A filesystem that refuses the link: the agent still starts.
   }
diff --git a/packages/skill-browser/DECISIONS.md b/packages/skill-browser/DECISIONS.md
index 194157c42..d3c505e4d 100644
--- a/packages/skill-browser/DECISIONS.md
+++ b/packages/skill-browser/DECISIONS.md
@@ -16,3 +16,8 @@ already made, and lists it in its pull request; for anything else it proposes an
   agent opened it, and can click and type in it. Picked over a Browser tab on the run page.
 - A run that stops to ask a question keeps its browser, and its live screen, for the
   answer. Picked over closing the browser at every end of a run.
+- The skill calls the command by its full name and a version range,
+  `npx @openagt/skill-browser@0.1`: the name is ours on npm, so no other package can run
+  under it, and nothing is installed in the project. Picked over `npx browser` with the
+  package as a dependency of the project, which ran whatever package holds that name on
+  npm where the install was missing, and which a project without Node could not have.
diff --git a/packages/skill-browser/SKILL.md b/packages/skill-browser/SKILL.md
index dfeb0d8dd..e299f7fa7 100644
--- a/packages/skill-browser/SKILL.md
+++ b/packages/skill-browser/SKILL.md
@@ -5,24 +5,24 @@ description: A real browser you drive from the shell, to see or act on a web pag
 
 # The browser
 
-A headless Chrome of your own, on an empty profile: nobody's logins are in it. Drive it with the `browser` command, a dependency of this repository (`@openagt/skill-browser`), run as `npx browser`. When that fails for a missing `node_modules`, install with the lockfile's package manager (`npm install` for `package-lock.json`) and run it again. It needs Chrome on the machine, or `CHROME_PATH` set to a Chrome or Chromium executable.
+A headless Chrome of your own, on an empty profile: nobody's logins are in it. Drive it with the `browser` command, always run by its full name: `npx @openagt/skill-browser@0.1`. It needs Chrome on the machine, or `CHROME_PATH` set to a Chrome or Chromium executable.
 
 ```
-npx browser open <address>       open the address, starting the browser if none is open
-npx browser read                 print the page again
-npx browser click <n>            click element n
-npx browser type <n> <text>      replace what element n holds with the text; on a select, pick that option;
-                                 on a date or time field, give the value as 2024-01-31, 13:45, 2024-01
-npx browser press <key>          Enter, Tab, Escape, Backspace, Space, ArrowUp, ArrowDown, ArrowLeft, ArrowRight
-npx browser screenshot [file]    save what the page shows as a PNG and print its path (a temporary file
-                                 when none is named; never name one inside the repository)
-npx browser eval <script>        run a JavaScript expression in the page and print its value, as JSON
-                                 (`document.title`, not `return document.title`; `await` works; an
-                                 element prints as `{}`, so ask for its properties)
-npx browser close                close the browser
+npx @openagt/skill-browser@0.1 open <address>       open the address, starting the browser if none is open
+npx @openagt/skill-browser@0.1 read                 print the page again
+npx @openagt/skill-browser@0.1 click <n>            click element n
+npx @openagt/skill-browser@0.1 type <n> <text>      replace what element n holds with the text; on a select, pick that option;
+                                                    on a date or time field, give the value as 2024-01-31, 13:45, 2024-01
+npx @openagt/skill-browser@0.1 press <key>          Enter, Tab, Escape, Backspace, Space, ArrowUp, ArrowDown, ArrowLeft, ArrowRight
+npx @openagt/skill-browser@0.1 screenshot [file]    save what the page shows as a PNG and print its path (a temporary file
+                                                    when none is named; never name one inside the repository)
+npx @openagt/skill-browser@0.1 eval <script>        run a JavaScript expression in the page and print its value, as JSON
+                                                    (`document.title`, not `return document.title`; `await` works; an
+                                                    element prints as `{}`, so ask for its properties)
+npx @openagt/skill-browser@0.1 close                close the browser
 ```
 
-Quote a `<text>` or `<script>` with spaces as one argument: `npx browser type 2 'Ada Lovelace'`.
+Quote a `<text>` or `<script>` with spaces as one argument: `npx @openagt/skill-browser@0.1 type 2 'Ada Lovelace'`.
 
 `open`, `read`, `click`, `type` and `press` print the page once it has loaded (or after 10 seconds, as it stands): its title, its address, its text (the first 10,000 characters), then its elements (links, buttons, fields; the first 300) numbered `[n]`. What is inside an iframe or a shadow root is not printed; reach it with `eval`. `click` and `type` take that number, from the last print: when the page changes, the numbers do too. The numbers are written on the page's elements as `data-browser-ref` attributes. An address without `http://` or `https://` gets `http://`; no other kind opens. A dialog the page opens (alert, confirm, prompt) is accepted at once, and the next print begins with a `Dialog, accepted:` line naming it.
 
diff --git a/packages/skill-browser/package.json b/packages/skill-browser/package.json
index 069bc1875..85d254b2e 100644
--- a/packages/skill-browser/package.json
+++ b/packages/skill-browser/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-browser",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "A browser for coding agents: a headless Chrome the agent opens, reads, clicks and types into with the browser command, shown live to a person watching the run.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-discord/DECISIONS.md b/packages/skill-discord/DECISIONS.md
index 85b2b11a3..b0532966d 100644
--- a/packages/skill-discord/DECISIONS.md
+++ b/packages/skill-discord/DECISIONS.md
@@ -16,3 +16,8 @@ already made, and lists it in its pull request; for anything else it proposes an
 - The webhook is set per machine by a person (`discord setup <webhook>`), outside the
   project; `DISCORD_WEBHOOK` in the environment wins. Picked over a file in the project:
   anyone holding the URL can post to the channel.
+- The skill calls the command by its full name and a version range,
+  `npx @openagt/skill-discord@0.1`: the name is ours on npm, so no other package can run
+  under it, and nothing is installed in the project. Picked over `npx discord` with the
+  package as a dependency of the project, which ran whatever package holds that name on
+  npm where the install was missing, and which a project without Node could not have.
diff --git a/packages/skill-discord/SKILL.md b/packages/skill-discord/SKILL.md
index ad63d0c5b..446babe4b 100644
--- a/packages/skill-discord/SKILL.md
+++ b/packages/skill-discord/SKILL.md
@@ -5,16 +5,16 @@ description: Post a message to the team's Discord channel from the shell, when a
 
 # Discord
 
-Post one message to a Discord channel with the `discord` command, a dependency of this repository (`@openagt/skill-discord`), run as `npx discord`. When that fails for a missing `node_modules`, install with the lockfile's package manager (`npm install` for `package-lock.json`) and run it again.
+Post one message to a Discord channel with the `discord` command, always run by its full name: `npx @openagt/skill-discord@0.1`.
 
 ```
-npx discord send "<message>"     post the message to this machine's webhook
-npx discord status               whether this machine has a webhook, and where it comes from
+npx @openagt/skill-discord@0.1 send "<message>"     post the message to this machine's webhook
+npx @openagt/skill-discord@0.1 status               whether this machine has a webhook, and where it comes from
 ```
 
 Quote the message as one argument. It is posted as a Discord message, so Discord's markdown formats it (`*`, `_`, backticks), up to 2,000 characters (a longer one is cut and says so); `@everyone` and other mentions in it do not ping anyone.
 
-The channel is the one whose webhook this machine was given, by a person: `npx discord setup <webhook>` saves it for this user on this machine, `npx discord setup --clear` forgets it, and `DISCORD_WEBHOOK` in the environment wins over the saved one. Never ask for the webhook, never print it, and never write it into the repository: anyone holding it can post to the channel.
+The channel is the one whose webhook this machine was given, by a person: `npx @openagt/skill-discord@0.1 setup <webhook>` saves it for this user on this machine, `npx @openagt/skill-discord@0.1 setup --clear` forgets it, and `DISCORD_WEBHOOK` in the environment wins over the saved one. Never ask for the webhook, never print it, and never write it into the repository: anyone holding it can post to the channel.
 
 `send`, `setup` and `status` print one JSON line on stdout. A refusal exits 1 with the reason on stderr: `no-webhook` (none on this machine: say so and go on, a person sets it), `not-posted` (Discord or the network refused it; the detail says which, never the URL), `empty`, and for `setup`, `invalid`. A wrong command line exits 2 with the usage on stderr.
 
@@ -23,5 +23,5 @@ The channel is the one whose webhook this machine was given, by a person: `npx d
 A tool that runs coding agents may run a line of the person's when a run ends, with the message in `$MESSAGE`. This is the line:
 
 ```
-npx discord send "$MESSAGE"
+npx @openagt/skill-discord@0.1 send "$MESSAGE"
 ```
diff --git a/packages/skill-discord/package.json b/packages/skill-discord/package.json
index ae1498533..032dbca15 100644
--- a/packages/skill-discord/package.json
+++ b/packages/skill-discord/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-discord",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "Discord as a skill: post one message to a Discord channel through its webhook, set once per machine.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-github/DECISIONS.md b/packages/skill-github/DECISIONS.md
index 0ce899e5a..a3da6fa87 100644
--- a/packages/skill-github/DECISIONS.md
+++ b/packages/skill-github/DECISIONS.md
@@ -17,14 +17,19 @@ already made, and lists it in its pull request; for anything else it proposes an
 - Pushing is not this package's: the branches package pushes, and the agent, OpenAgent
   and the scheduler compose push then open through the two declared commands. Picked over
   one `publish` that pushed and opened, which was one skill naming another.
+- The skill calls the command by its full name and a version range,
+  `npx @openagt/skill-github@0.1`: the name is ours on npm, so no other package can run
+  under it, and nothing is installed in the project. Picked over `npx github` with the
+  package as a dependency of the project, which ran whatever package holds that name on
+  npm where the install was missing, and which a project without Node could not have.
 
 ## Flow: open
 - The agent opens its pull request only when asked to publish, by its task or by the
-  person: `npx github open` with the title and body the agent wrote, and the merge armed
-  on green when whoever asked says the work may land on its own. Opening it when it
-  finishes was the earlier rule and was dropped: a pull request is the person's act.
-  Picked over whoever started the agent opening it, which needed a run process that knew
-  the agent's words: the agent knows them.
+  person: `npx @openagt/skill-github@0.1 open` with the title and body the agent wrote,
+  and the merge armed on green when whoever asked says the work may land on its own.
+  Opening it when it finishes was the earlier rule and was dropped: a pull request is
+  the person's act. Picked over whoever started the agent opening it, which needed a run
+  process that knew the agent's words: the agent knows them.
 - `open` opens no second request for a branch that has one open, and never opens a draft
   when the merge is armed.
 - The branch must be on the remote already; `open` neither pushes nor checks, GitHub's own
diff --git a/packages/skill-github/SKILL.md b/packages/skill-github/SKILL.md
index da4952bcd..7a5219f0a 100644
--- a/packages/skill-github/SKILL.md
+++ b/packages/skill-github/SKILL.md
@@ -9,14 +9,14 @@ The project's pull requests and issues are on GitHub. This skill is how you reac
 
 ## The command
 
-`github` is a dependency of this repository (`@openagt/skill-github`). If `node_modules` is missing, install with the lockfile's package manager (`npm install` for `package-lock.json`). Then run `npx github` inside your checkout. It prints JSON; a refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage.
+Run the `github` command inside your checkout, always by its full name: `npx @openagt/skill-github@0.1`. It prints JSON; a refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage.
 
 ## Your pull request
 
 Open a pull request only when your task or the person asks for one, or asks you to publish your work. Push your branch first (your branches skill says how), then:
 
 ```
-npx github open --title "<one line naming what the change does>" --body "<what changed, and why>"
+npx @openagt/skill-github@0.1 open --title "<one line naming what the change does>" --body "<what changed, and why>"
 ```
 
 It opens the pull request for the branch you are on and prints it in `request` (`number`, `url`). A branch that already has an open pull request gets no second one: that one is answered, with `existing` true. Add `--merge` when the work may land on its own: the pull request then merges once its checks pass, also where the repository does not allow auto-merge (`merge` in the answer says `auto-armed`, `merged` or `watching`). Add `--draft` instead for a pull request a person should look at first; with `--merge` too, `--draft` is dropped.
@@ -26,7 +26,7 @@ A pull request whose body has a line `Closes #<number>` closes that issue when i
 ## Reading pull requests and issues
 
 ```
-npx github requests [--branch <b>] [--state open|merged|all] [--since <iso>]
+npx @openagt/skill-github@0.1 requests [--branch <b>] [--state open|merged|all] [--since <iso>]
 ```
 
 The project's newest 50 pull requests, newest first, all states unless `--state`, only `<b>`'s with `--branch`; `--since` keeps those created since, or merged since with `--state merged`. Each has `number`, `url`, `state` (`open`, `merged`, `closed`), `title`, `draft`, `branch`, `head`, `createdAt`, and for a merged one `mergedAt` and `mergeCommit` (the commit it landed as).
@@ -36,7 +36,7 @@ For a pull request's discussion and diff, and for the project's issues, use `gh`
 ## Landing a pull request for a person
 
 ```
-npx github merge <number>
+npx @openagt/skill-github@0.1 merge <number>
 ```
 
 A draft is marked ready, then the merge is armed as `--merge` arms it: `outcome` says `auto-armed`, `merged` or `watching`; a request no longer open is refused as `not-open`. Only when whoever started you asked you to land it.
diff --git a/packages/skill-github/package.json b/packages/skill-github/package.json
index 5a41f7bbb..5c9a6707a 100644
--- a/packages/skill-github/package.json
+++ b/packages/skill-github/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-github",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "GitHub as a skill for coding agents: the project's pull requests and issues through gh, and the one command OpenAgent and the scheduler run for the git host: requests, open, merge, home.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-logs/DECISIONS.md b/packages/skill-logs/DECISIONS.md
index 2948bae2b..b7d011041 100644
--- a/packages/skill-logs/DECISIONS.md
+++ b/packages/skill-logs/DECISIONS.md
@@ -45,6 +45,11 @@ already made, and lists it in its pull request; for anything else it proposes an
 - The skill says when to look back: before planning or working a ticket, read the runs its
   claim names. Leaving that to the caller's prompts was the alternative and was not taken:
   outside the caller nobody would ever read the logs.
+- The skill calls the command by its full name and a version range,
+  `npx @openagt/skill-logs@0.1`: the name is ours on npm, so no other package can run
+  under it, and nothing is installed in the project. Picked over `npx logs` with the
+  package as a dependency of the project, which ran whatever package holds that name on
+  npm where the install was missing, and which a project without Node could not have.
 
 ## Flow: the command
 - `logs` lists newest first and prints the package's fields only, never `caller`, except
diff --git a/packages/skill-logs/SKILL.md b/packages/skill-logs/SKILL.md
index b8878184e..7648ce88e 100644
--- a/packages/skill-logs/SKILL.md
+++ b/packages/skill-logs/SKILL.md
@@ -7,21 +7,21 @@ description: The record of every run agents made on this project — what was as
 
 Every run an agent made on this project leaves a record on the branch `agent-data`, never on a code branch; your checkout does not contain it. A run is two files under `agents/<who>/`: the card, `<id>.json` — what was asked, the branch, the pull request, how it ended, what it cost — and the diary, `<id>.jsonl` — what the agent said along the way, its result.
 
-Read them with the `logs` command, a dependency of this repository (`@openagt/skill-logs`), run as `npx logs`. When that fails for a missing `node_modules`, install with the lockfile's package manager (`npm install` for `package-lock.json`) and run it again. You only read: the program that ran an agent records its run, at its end. The command's `delete` and `patch`, and its `--local` and `--full` flags, are for the dashboard that shows the runs; never use them. A refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage.
+Read them with the `logs` command, always run by its full name: `npx @openagt/skill-logs@0.1`. You only read: the program that ran an agent records its run, at its end. The command's `delete` and `patch`, and its `--local` and `--full` flags, are for the dashboard that shows the runs; never use them. A refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage.
 
 ## Read
 
 ```
-npx logs [--branch <name>] [--limit N]
-                                 the runs, newest first, as one JSON array of cards — the newest 20
-                                 unless --limit says otherwise; --branch keeps the runs on one branch
-npx logs show <id>               one run: its card, plus `diary`, the lines of what the agent
-                                 said, its result, how it ended, and what it cost
+npx @openagt/skill-logs@0.1 [--branch <name>] [--limit N]
+                                                    the runs, newest first, as one JSON array of cards — the newest 20
+                                                    unless --limit says otherwise; --branch keeps the runs on one branch
+npx @openagt/skill-logs@0.1 show <id>               one run: its card, plus `diary`, the lines of what the agent
+                                                    said, its result, how it ended, and what it cost
 ```
 
 ## Before you plan or work a ticket, read its earlier runs
 
-A ticket may have been worked before. Claiming it names who claimed it before you: a run's id, shaped like `2026-09-08T18-14-30-111Z`, read with `npx logs show <id>`, or else a branch, read with `npx logs --branch <name>`; no run on that branch means no record: read the branch itself. A `stopped` or `failed` run tells you what to avoid: read what its agent said before it ended. A `done` run with a `pr` means the work may already be there: read the pull request before doing it again.
+A ticket may have been worked before. Claiming it names who claimed it before you: a run's id, shaped like `2026-09-08T18-14-30-111Z`, read with `npx @openagt/skill-logs@0.1 show <id>`, or else a branch, read with `npx @openagt/skill-logs@0.1 --branch <name>`; no run on that branch means no record: read the branch itself. A `stopped` or `failed` run tells you what to avoid: read what its agent said before it ended. A `done` run with a `pr` means the work may already be there: read the pull request before doing it again.
 
 ## The card
 
diff --git a/packages/skill-logs/dashboard/index.tsx b/packages/skill-logs/dashboard/index.tsx
index 41ab62602..872680952 100644
--- a/packages/skill-logs/dashboard/index.tsx
+++ b/packages/skill-logs/dashboard/index.tsx
@@ -1,7 +1,7 @@
 // The logs' module for the dashboard: the package's `./dashboard` export. It adds one page, Logs,
 // that lists the recorded runs of every project that has this package. Its data is the `logs`
 // command's own output, run in each project by the dashboard: the module reads exactly what an
-// agent reads with `npx logs`.
+// agent reads with `npx @openagt/skill-logs@0.1`.
 import { ScrollText } from 'lucide-react'
 import { defineModule } from '@openagt/dashboard/module'
 import { LogsPage } from './LogsPage.js'
diff --git a/packages/skill-logs/package.json b/packages/skill-logs/package.json
index 7c712fcb5..2bd50141a 100644
--- a/packages/skill-logs/package.json
+++ b/packages/skill-logs/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-logs",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The agent logs for coding agents: the record of every run made on a project, its card and its diary, kept on a branch of the project's repository and read with the logs command.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-maintainability/package.json b/packages/skill-maintainability/package.json
index 0553e5f72..1778808bb 100644
--- a/packages/skill-maintainability/package.json
+++ b/packages/skill-maintainability/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-maintainability",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The maintainability command for coding agents: refactor a part of the code to make it as maintainable as possible. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-maintenance/package.json b/packages/skill-maintenance/package.json
index c3f4e78fd..bf759fd97 100644
--- a/packages/skill-maintenance/package.json
+++ b/packages/skill-maintenance/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-maintenance",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The maintenance command for coding agents: find the parts of the code that need refactoring and put their maintainability and security work on the agent queue. Queues only. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-market-research/package.json b/packages/skill-market-research/package.json
index d3edea045..e598d8be7 100644
--- a/packages/skill-market-research/package.json
+++ b/packages/skill-market-research/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-market-research",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The market-research command for coding agents: research the market of the project's product, and write a ticket for each opportunity no ticket covers yet. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-orchestration/DECISIONS.md b/packages/skill-orchestration/DECISIONS.md
index 4635edc6f..449845aca 100644
--- a/packages/skill-orchestration/DECISIONS.md
+++ b/packages/skill-orchestration/DECISIONS.md
@@ -16,6 +16,12 @@ already made, and lists it in its pull request; for anything else it proposes an
 - The words are main agent and subagent. Picked over coordinator and worker.
 - The package and its command are named `orchestration`. Picked over `subagents` and
   `agents`.
+- The skill calls the command by its full name and a version range,
+  `npx @openagt/skill-orchestration@0.1`: the name is ours on npm, so no other package
+  can run under it, and nothing is installed in the project. Picked over
+  `npx orchestration` with the package as a dependency of the project, which ran
+  whatever package holds that name on npm where the install was missing, and which a
+  project without Node could not have.
 
 ## A subagent
 - A subagent's branch starts from the main agent's branch, not from origin's default
diff --git a/packages/skill-orchestration/SKILL.md b/packages/skill-orchestration/SKILL.md
index 5b00d8c4b..47e3a7272 100644
--- a/packages/skill-orchestration/SKILL.md
+++ b/packages/skill-orchestration/SKILL.md
@@ -5,16 +5,16 @@ description: "Split your task across subagents: plan it, get the person's yes, s
 
 # Orchestration
 
-A subagent is another coding agent you start on one part of your task: it works alone, in its own checkout. Use the `orchestration` command, a dependency of this repository (`@openagt/skill-orchestration`), run as `npx orchestration`. When that fails for a missing `node_modules`, install with the lockfile's package manager (`npm install` for `package-lock.json`) and run it again.
+A subagent is another coding agent you start on one part of your task: it works alone, in its own checkout. Use the `orchestration` command, always run by its full name: `npx @openagt/skill-orchestration@0.1`.
 
 ```
-npx orchestration plan <file>    save the file as your plan; answers the `question` to ask the person
-npx orchestration start --level <simple|hard> "<task>"
-                                 start a subagent on the task; answers its id at once, without waiting for it
-npx orchestration list           your subagents, newest first, as one JSON array
-npx orchestration read <id>      one subagent: its `status`, and once it ended its `branch` and `result`, its last reply
-npx orchestration stop <id>      stop a subagent that is running
-npx orchestration land <id>      merge an ended subagent's branch into yours, then delete that branch
+npx @openagt/skill-orchestration@0.1 plan <file>    save the file as your plan; answers the `question` to ask the person
+npx @openagt/skill-orchestration@0.1 start --level <simple|hard> "<task>"
+                                                    start a subagent on the task; answers its id at once, without waiting for it
+npx @openagt/skill-orchestration@0.1 list           your subagents, newest first, as one JSON array
+npx @openagt/skill-orchestration@0.1 read <id>      one subagent: its `status`, and once it ended its `branch` and `result`, its last reply
+npx @openagt/skill-orchestration@0.1 stop <id>      stop a subagent that is running
+npx @openagt/skill-orchestration@0.1 land <id>      merge an ended subagent's branch into yours, then delete that branch
 ```
 
 A refusal exits 1 with a line on stderr saying why.
diff --git a/packages/skill-orchestration/package.json b/packages/skill-orchestration/package.json
index 097c3f708..4c4aef9df 100644
--- a/packages/skill-orchestration/package.json
+++ b/packages/skill-orchestration/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-orchestration",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "Orchestration as a skill: a main agent plans its task, starts subagents on the parts once the person approved the plan, each a run of its own on a branch started from the main agent's, and lists them, reads their results, stops them and lands their work with the orchestration command, and brings the Subagents section of the dashboard's Settings page.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-plan-tickets/SKILL.md b/packages/skill-plan-tickets/SKILL.md
index cd6f0fb74..629eb40d2 100644
--- a/packages/skill-plan-tickets/SKILL.md
+++ b/packages/skill-plan-tickets/SKILL.md
@@ -6,7 +6,7 @@ schedule:
   every: 6h
   waits-for: when a ticket that is not waiting, claimed, in review or queued has no plan, or an outdated one
   when: |-
-    npx tickets list | jq --argjson q "$(npx queue)" '[.[] | select(((.planned | not) or .outdated) and .pr == null and (.waiting | not) and (.locked | not) and ((.file | rtrimstr(".md")) as $s | $q | any(contains($s)) | not)) | .file]'
+    npx @openagt/skill-tickets@0.1 list | jq --argjson q "$(npx @openagt/skill-queue@0.1)" '[.[] | select(((.planned | not) or .outdated) and .pr == null and (.waiting | not) and (.locked | not) and ((.file | rtrimstr(".md")) as $s | $q | any(contains($s)) | not)) | .file]'
 ---
 
 Queue plans for the tickets that need one. Nobody will answer you: never ask, decide yourself. You only queue work, you never do it: write no plan yourself, the only thing you change is the queue.
diff --git a/packages/skill-plan-tickets/package.json b/packages/skill-plan-tickets/package.json
index 8194783d5..c63b41529 100644
--- a/packages/skill-plan-tickets/package.json
+++ b/packages/skill-plan-tickets/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-plan-tickets",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The plan-tickets command for coding agents: queue a plan for the open tickets that have none or an outdated one, unattended. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-plan/package.json b/packages/skill-plan/package.json
index 1777d3a4f..22efe296d 100644
--- a/packages/skill-plan/package.json
+++ b/packages/skill-plan/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-plan",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The plan command for coding agents: write a ticket for a task and, under it, a plan naming the ways to do it and the one to take, then stop. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-post-merge-cleanup/SKILL.md b/packages/skill-post-merge-cleanup/SKILL.md
index b7464c756..8df0f0abc 100644
--- a/packages/skill-post-merge-cleanup/SKILL.md
+++ b/packages/skill-post-merge-cleanup/SKILL.md
@@ -6,7 +6,7 @@ schedule:
   every: 1h
   waits-for: when a pull request merged since the last clean-up has no clean-up yet
   when: |-
-    gh pr list --state merged --limit 50 --json number,body --search "merged:>=$(npx logs --limit 200 | jq -r '[.[] | select(.intent == "/post-merge-cleanup" and .status == "done")][0].startedAt // (now - 86400 | todate)')" | jq '[.[] | select(.body | contains("Post-merge cleanup done.") | not) | .number]'
+    gh pr list --state merged --limit 50 --json number,body --search "merged:>=$(npx @openagt/skill-logs@0.1 --limit 200 | jq -r '[.[] | select(.intent == "/post-merge-cleanup" and .status == "done")][0].startedAt // (now - 86400 | todate)')" | jq '[.[] | select(.body | contains("Post-merge cleanup done.") | not) | .number]'
 ---
 
 Write what merged work decided and taught into the project's knowledge files. Nobody will answer you: never ask, decide yourself.
diff --git a/packages/skill-post-merge-cleanup/package.json b/packages/skill-post-merge-cleanup/package.json
index feb2c6b50..5a4d93a89 100644
--- a/packages/skill-post-merge-cleanup/package.json
+++ b/packages/skill-post-merge-cleanup/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-post-merge-cleanup",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The post-merge-cleanup command for coding agents: bring the project's knowledge files up to date from merged pull requests in a pull request a person reviews, or from an agent run's pull request before it merges. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-question/package.json b/packages/skill-question/package.json
index 74f49d326..9e1b1d7bc 100644
--- a/packages/skill-question/package.json
+++ b/packages/skill-question/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-question",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "How a coding agent asks the person to decide: end the reply with one await-choices block and wait for the answer. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-queue/DECISIONS.md b/packages/skill-queue/DECISIONS.md
index 8ec6efa6f..df325dabb 100644
--- a/packages/skill-queue/DECISIONS.md
+++ b/packages/skill-queue/DECISIONS.md
@@ -29,6 +29,11 @@ already made, and lists it in its pull request; for anything else it proposes an
   goes at the end of the file, in whatever section ends it.
 - Done means deleted, never checked off: a `- [x]` or `- [X]` line is not an open entry; a
   `- [ ]` line is, printed without its box and deleted whole.
+- The skill calls the command by its full name and a version range,
+  `npx @openagt/skill-queue@0.1`: the name is ours on npm, so no other package can run
+  under it, and nothing is installed in the project. Picked over `npx queue` with the
+  package as a dependency of the project, which ran whatever package holds that name on
+  npm where the install was missing, and which a project without Node could not have.
 
 ## Flow: the command
 - A read fetches origin once and reads everything from that copy (the library's queue
diff --git a/packages/skill-queue/SKILL.md b/packages/skill-queue/SKILL.md
index a3337a5fb..c77b51c15 100644
--- a/packages/skill-queue/SKILL.md
+++ b/packages/skill-queue/SKILL.md
@@ -7,22 +7,22 @@ description: Where the project's agent queue lives, how to read it and change it
 
 The agent queue (`TODO_AGENTS.md`) lives on the branch `agent-data`, never on a code branch; your checkout does not contain it. It lists every task agents will work on next, in the order they will be taken.
 
-Read and change it with the `queue` command, a dependency of this repository (`@openagt/skill-queue`), run as `npx queue`. When that fails for a missing `node_modules`, install with the lockfile's package manager (`npm install` for `package-lock.json`) and run it again. Every change it makes is one commit on the `agent-data` branch, pushed straight to the remote when the project shares its records. The command's `--local` and `--full` flags are for the dashboard that shows the queue; never use them. A refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage.
+Read and change it with the `queue` command, always run by its full name: `npx @openagt/skill-queue@0.1`. Every change it makes is one commit on the `agent-data` branch, pushed straight to the remote when the project shares its records. The command's `--local` and `--full` flags are for the dashboard that shows the queue; never use them. A refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage.
 
 ## Read
 
 ```
-npx queue                        the open entries, in order of work, as one JSON array
+npx @openagt/skill-queue@0.1                        the open entries, in order of work, as one JSON array
 ```
 
 ## Change
 
 ```
-npx queue add <text> [--priority N]
-                                 put an entry on the queue; --priority (0-10) places it at the end of
-                                 that section; without it, the entry goes at the end of the file
-npx queue done <entry>           remove an entry: one quoted argument, exactly as `npx queue`
-                                 printed it; done means deleted
+npx @openagt/skill-queue@0.1 add <text> [--priority N]
+                                                    put an entry on the queue; --priority (0-10) places it at the end of
+                                                    that section; without it, the entry goes at the end of the file
+npx @openagt/skill-queue@0.1 done <entry>           remove an entry: one quoted argument, exactly as `npx @openagt/skill-queue@0.1`
+                                                    printed it; done means deleted
 ```
 
 ## Format
@@ -44,4 +44,4 @@ npx queue done <entry>           remove an entry: one quoted argument, exactly a
 ...
 ```
 
-The queue lists *all* tasks AI will work on next, sorted by priority. Priority 10 is rarely used (e.g. critical production bugs) and is treated as the utmost priority. Within a priority, the first tasks have higher priority (they are the "next" tasks within that "priority queue"). A done entry is removed (`npx queue done`).
+The queue lists *all* tasks AI will work on next, sorted by priority. Priority 10 is rarely used (e.g. critical production bugs) and is treated as the utmost priority. Within a priority, the first tasks have higher priority (they are the "next" tasks within that "priority queue"). A done entry is removed (`npx @openagt/skill-queue@0.1 done`).
diff --git a/packages/skill-queue/dashboard/index.tsx b/packages/skill-queue/dashboard/index.tsx
index 339c3c803..4b41526d0 100644
--- a/packages/skill-queue/dashboard/index.tsx
+++ b/packages/skill-queue/dashboard/index.tsx
@@ -3,7 +3,7 @@
 // one Overview card, AI Queue, that lists them in full and starts agents on them; and one action
 // on the links dashboard pages show, "Add to queue". Its data is the `queue` command's own output,
 // run in each project by the dashboard: the module reads exactly what an agent reads with
-// `npx queue`, and writes exactly the line an agent writes with `npx queue add`.
+// `npx @openagt/skill-queue@0.1`, and writes exactly the line an agent writes with `npx @openagt/skill-queue@0.1 add`.
 import { ListTodo } from 'lucide-react'
 import { defineModule } from '@openagt/dashboard/module'
 import { QueuePage } from './QueuePage.js'
diff --git a/packages/skill-queue/package.json b/packages/skill-queue/package.json
index c71346e5f..f7dc2192a 100644
--- a/packages/skill-queue/package.json
+++ b/packages/skill-queue/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-queue",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The agent queue for coding agents: the priority-banded list of what agents work on next, kept on a branch of the project's repository and changed with the queue command.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-readability/package.json b/packages/skill-readability/package.json
index ad5256dac..53e6f7bed 100644
--- a/packages/skill-readability/package.json
+++ b/packages/skill-readability/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-readability",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The readability command for coding agents: refactor a part of the code to make it as easy as possible for humans to read, rating every file and function before and after. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-research/package.json b/packages/skill-research/package.json
index 46f1feaac..8e68a33c8 100644
--- a/packages/skill-research/package.json
+++ b/packages/skill-research/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-research",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The research command for coding agents: rate how obviously well a part of the code solves each problem it solves, and name the problems worth researching alternatives for. Changes nothing. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-security-audit/package.json b/packages/skill-security-audit/package.json
index 0bb9ce92a..f8d412b53 100644
--- a/packages/skill-security-audit/package.json
+++ b/packages/skill-security-audit/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-security-audit",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The security-audit command for coding agents: audit a part of the code for security issues, exhaustively, fixing each issue found. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-suggest-new-features/package.json b/packages/skill-suggest-new-features/package.json
index 6915a1b52..cc3917cce 100644
--- a/packages/skill-suggest-new-features/package.json
+++ b/packages/skill-suggest-new-features/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-suggest-new-features",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The suggest-new-features command for coding agents: think like a product manager and write a ticket for each net-new feature the product should have next. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-suggest-new-tickets/package.json b/packages/skill-suggest-new-tickets/package.json
index 915b02718..ec0a23282 100644
--- a/packages/skill-suggest-new-tickets/package.json
+++ b/packages/skill-suggest-new-tickets/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-suggest-new-tickets",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The suggest-new-tickets command for coding agents: suggest new tickets for the project, and write each one in the project's ticket format. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-suggest-tickets-to-work-on/package.json b/packages/skill-suggest-tickets-to-work-on/package.json
index 47fb0e6f6..1b20c0378 100644
--- a/packages/skill-suggest-tickets-to-work-on/package.json
+++ b/packages/skill-suggest-tickets-to-work-on/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-suggest-tickets-to-work-on",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The suggest-tickets-to-work-on command for coding agents: pick and rank the tickets worth working on next, each with the priority it should get on the agent queue. Changes nothing. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-tickets/DECISIONS.md b/packages/skill-tickets/DECISIONS.md
index 14f148ace..b36f0976e 100644
--- a/packages/skill-tickets/DECISIONS.md
+++ b/packages/skill-tickets/DECISIONS.md
@@ -46,6 +46,11 @@ already made, and lists it in its pull request; for anything else it proposes an
 - A ticket's row, the same fields in `list` and `show`: the title from its `# ` line, the
   summary from the first prose line after `## TLDR`, else after the title, scanning past
   headings, `Priority:` lowercased.
+- The skill calls the command by its full name and a version range,
+  `npx @openagt/skill-tickets@0.1`: the name is ours on npm, so no other package can run
+  under it, and nothing is installed in the project. Picked over `npx tickets` with the
+  package as a dependency of the project, which ran whatever package holds that name on
+  npm where the install was missing, and which a project without Node could not have.
 
 ## Flow: a claim
 - A claim is a committed file holding one line, `CLAIMED: <who>`, so agents on other
diff --git a/packages/skill-tickets/SKILL.md b/packages/skill-tickets/SKILL.md
index 395fef716..495844b36 100644
--- a/packages/skill-tickets/SKILL.md
+++ b/packages/skill-tickets/SKILL.md
@@ -7,48 +7,48 @@ description: Where the project's tickets live, how to read and change them, how
 
 The tickets (`tickets/<DATE>_<SLUG>.md`, with their `.plan.md` and `.lock.md` siblings) live on the branch `agent-data`, never on a code branch. A `tickets` link at the repository root, if present, is a possibly stale copy: never write there.
 
-Read and change them with the `tickets` command, a dependency of this repository (`@openagt/skill-tickets`), run as `npx tickets`. When that fails for a missing `node_modules`, install with the lockfile's package manager (`npm install` for `package-lock.json`) and run it again. Every change it makes is one commit on the `agent-data` branch, pushed straight to the remote when the project shares its records. Never pass `--local` or `--force`: they are a person's.
+Read and change them with the `tickets` command, always run by its full name: `npx @openagt/skill-tickets@0.1`. Every change it makes is one commit on the `agent-data` branch, pushed straight to the remote when the project shares its records. Never pass `--local` or `--force`: they are a person's.
 
 Every command prints one JSON document; a refusal is `{"ok":false,"reason":…}` with why on stderr, exit 1; a wrong command line prints the usage on stderr, nothing on stdout, exit 2. Every `<file>` below is a ticket's filename (`2042-01-01_some-ticket.md`) or the `tickets/…` path a queue entry links to; `put` also takes the ticket's `.plan.md` and `meta.json`.
 
 ## Read
 
 ```
-npx tickets list                 every open ticket, as one JSON array; a row: file, title, summary, date,
-                                 planned, and when set priority, topics, issue, pr (set: the ticket is in
-                                 review), waiting (what it waits on), effort, uncertainty, outdated (the
-                                 plan says so), locked, lockedBy
-npx tickets show <file>          one ticket: its text, its plan, who holds it
-npx tickets meta                 when the tickets last caught up with the issue tracker:
-                                 {"lastImportedAt": <ISO 8601>}, or {} when no import was recorded
+npx @openagt/skill-tickets@0.1 list                 every open ticket, as one JSON array; a row: file, title, summary, date,
+                                                    planned, and when set priority, topics, issue, pr (set: the ticket is in
+                                                    review), waiting (what it waits on), effort, uncertainty, outdated (the
+                                                    plan says so), locked, lockedBy
+npx @openagt/skill-tickets@0.1 show <file>          one ticket: its text, its plan, who holds it
+npx @openagt/skill-tickets@0.1 meta                 when the tickets last caught up with the issue tracker:
+                                                    {"lastImportedAt": <ISO 8601>}, or {} when no import was recorded
 ```
 
 ## Change
 
 ```
-npx tickets put <file>           write one whole file under tickets/ from stdin, creating it if new
-                                 (npx tickets put <file> < draft.md): a ticket, its plan, or meta.json
-                                 holding the object meta shows
-npx tickets close <file>         when the ticket is not wanted, when its work is done with no pull
-                                 request to merge, or for the tracker update once its pull request merged:
-                                 remove the ticket with its plan and claim; refused while someone else
-                                 holds it; its queue entry, if any, stays: `npx queue done` it
+npx @openagt/skill-tickets@0.1 put <file>           write one whole file under tickets/ from stdin, creating it if new
+                                                    (npx @openagt/skill-tickets@0.1 put <file> < draft.md): a ticket, its plan, or meta.json
+                                                    holding the object meta shows
+npx @openagt/skill-tickets@0.1 close <file>         when the ticket is not wanted, when its work is done with no pull
+                                                    request to merge, or for the tracker update once its pull request merged:
+                                                    remove the ticket with its plan and claim; refused while someone else
+                                                    holds it; its queue entry, if any, stays: `npx @openagt/skill-queue@0.1 done` it
 ```
 
 ## Claim before you plan or work a ticket
 
 ```
-npx tickets claim <file>         {"ok":true,"file":…,"holder":…,"earlier":[…]}: the ticket is yours;
-                                 earlier: who claimed it before you, newest first, each a run's id or
-                                 a branch; read what they did before you start
-                                 {"ok":false,"reason":"claimed","holder":…}: someone else's: pick another,
-                                 and never remove or overwrite their claim
-npx tickets release <file>       lift your own claim when the plan or the work is done, and before you
-                                 stop unless you closed the ticket: nothing lifts a claim on a timeout
-                                 {"ok":true,"file":…,"holder":…}: your claim is lifted
-                                 {"ok":false,"reason":"no-lock"}: nobody holds it: nothing to lift
-                                 {"ok":false,"reason":"not-holder","holder":…}: someone else holds it:
-                                 leave their claim
+npx @openagt/skill-tickets@0.1 claim <file>         {"ok":true,"file":…,"holder":…,"earlier":[…]}: the ticket is yours;
+                                                    earlier: who claimed it before you, newest first, each a run's id or
+                                                    a branch; read what they did before you start
+                                                    {"ok":false,"reason":"claimed","holder":…}: someone else's: pick another,
+                                                    and never remove or overwrite their claim
+npx @openagt/skill-tickets@0.1 release <file>       lift your own claim when the plan or the work is done, and before you
+                                                    stop unless you closed the ticket: nothing lifts a claim on a timeout
+                                                    {"ok":true,"file":…,"holder":…}: your claim is lifted
+                                                    {"ok":false,"reason":"no-lock"}: nobody holds it: nothing to lift
+                                                    {"ok":false,"reason":"not-holder","holder":…}: someone else holds it:
+                                                    leave their claim
 ```
 
 `put` ignores claims. You claim as `AGENT_ID` when it is set and not blank, else as your current branch: release from the branch you claimed on, or the claim stays until a person lifts it.
@@ -58,10 +58,10 @@ npx tickets release <file>       lift your own claim when the plan or the work i
 When the repository has the `queue` skill, a ticket goes on the agent queue as a link, its title as the label, at the ticket's own `Priority:` (5 when it has none):
 
 ```
-npx queue add '[<title>](tickets/<file>)' --priority <N>
+npx @openagt/skill-queue@0.1 add '[<title>](tickets/<file>)' --priority <N>
 ```
 
-Once the work is committed and its pull request is open: `npx queue done` the entry, its exact text, write the pull request into the ticket as its `PR:` line (`put` the whole ticket, the line added above the title), and release your claim. The ticket is in review. Do not close it: it closes when the pull request merges, through the update from the issue tracker, which reads the line `Closes tickets/<file>` in the pull request's body; add `Closes #<number>` when the ticket has an issue.
+Once the work is committed and its pull request is open: `npx @openagt/skill-queue@0.1 done` the entry, its exact text, write the pull request into the ticket as its `PR:` line (`put` the whole ticket, the line added above the title), and release your claim. The ticket is in review. Do not close it: it closes when the pull request merges, through the update from the issue tracker, which reads the line `Closes tickets/<file>` in the pull request's body; add `Closes #<number>` when the ticket has an issue.
 
 ## Formats
 
diff --git a/packages/skill-tickets/dashboard/index.tsx b/packages/skill-tickets/dashboard/index.tsx
index 2264dff54..b1f2019dc 100644
--- a/packages/skill-tickets/dashboard/index.tsx
+++ b/packages/skill-tickets/dashboard/index.tsx
@@ -2,8 +2,8 @@
 // Tickets, at `/tickets`: every project's backlog, one ticket's own page, and a ticket's plan; and
 // one Overview card, Hot tickets: what agents hold and what is flagged high priority. Its
 // data is the `tickets` command's own output, run in each project by the dashboard: the module
-// reads exactly what an agent reads with `npx tickets list`, and lifts a claim with the same
-// `npx tickets release`. What the page composes with other skills — a run started, a claim's
+// reads exactly what an agent reads with `npx @openagt/skill-tickets@0.1 list`, and lifts a claim with the same
+// `npx @openagt/skill-tickets@0.1 release`. What the page composes with other skills — a run started, a claim's
 // holder as a run, a plan's author, the actions other modules offer on a ticket as a link —
 // comes from the dashboard's own services, and names no other skill.
 import { Ticket } from 'lucide-react'
diff --git a/packages/skill-tickets/package.json b/packages/skill-tickets/package.json
index 8bb44136d..6cae22236 100644
--- a/packages/skill-tickets/package.json
+++ b/packages/skill-tickets/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-tickets",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "Tickets for coding agents: markdown tickets with their plans and claims, kept on a branch of the project's repository and changed with the tickets command.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-triage/SKILL.md b/packages/skill-triage/SKILL.md
index d9196b573..a1072b5d2 100644
--- a/packages/skill-triage/SKILL.md
+++ b/packages/skill-triage/SKILL.md
@@ -7,12 +7,12 @@ schedule:
     every: 6h
     waits-for: when a planned ticket is a quick win and is not waiting, claimed, in review or queued
     when: |-
-      npx tickets list | jq --argjson q "$(npx queue)" '[.[] | select(.planned and .pr == null and (.waiting | not) and (.locked | not) and (.outdated | not) and .effort != null and .uncertainty != null and .effort <= 2 and .uncertainty <= 2 and (.file as $f | $q | any(contains($f)) | not)) | .file]'
+      npx @openagt/skill-tickets@0.1 list | jq --argjson q "$(npx @openagt/skill-queue@0.1)" '[.[] | select(.planned and .pr == null and (.waiting | not) and (.locked | not) and (.outdated | not) and .effort != null and .uncertainty != null and .effort <= 2 and .uncertainty <= 2 and (.file as $f | $q | any(contains($f)) | not)) | .file]'
   - word: consensual
     every: 7d
     waits-for: when a planned ticket is consensual work and is not waiting, claimed, in review or queued
     when: |-
-      npx tickets list | jq --argjson q "$(npx queue)" '[.[] | select(.planned and .pr == null and (.waiting | not) and (.locked | not) and (.outdated | not) and .effort != null and .uncertainty != null and .uncertainty <= 3 and (.effort > 2 or .uncertainty > 2) and (.file as $f | $q | any(contains($f)) | not)) | .file]'
+      npx @openagt/skill-tickets@0.1 list | jq --argjson q "$(npx @openagt/skill-queue@0.1)" '[.[] | select(.planned and .pr == null and (.waiting | not) and (.locked | not) and (.outdated | not) and .effort != null and .uncertainty != null and .uncertainty <= 3 and (.effort > 2 or .uncertainty > 2) and (.file as $f | $q | any(contains($f)) | not)) | .file]'
 ---
 
 Choose work for the agent queue. Nobody will answer you: never ask, decide yourself. You only queue work, you never do it: the only thing you change is the queue. The word after the command is the mode: `quick`, `consensual`, or nothing for both.
diff --git a/packages/skill-triage/package.json b/packages/skill-triage/package.json
index e996b90a7..385d5d40b 100644
--- a/packages/skill-triage/package.json
+++ b/packages/skill-triage/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-triage",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The triage command for coding agents: put the tickets whose plan says they are ready on the project's agent queue, unattended; the quick wins, the consensual work, or both. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-update-tickets/SKILL.md b/packages/skill-update-tickets/SKILL.md
index 1620cf5a1..590e423bf 100644
--- a/packages/skill-update-tickets/SKILL.md
+++ b/packages/skill-update-tickets/SKILL.md
@@ -6,7 +6,7 @@ schedule:
   every: 15m
   waits-for: when an issue changed or a pull request that closes a ticket merged since the last import, or nothing was imported yet
   when: |-
-    { gh issue list --state all --limit 1 --json number --search "updated:>=$(npx tickets meta | jq -r .lastImportedAt)"; gh pr list --state merged --limit 100 --json number,body --search "merged:>=$(npx tickets meta | jq -r .lastImportedAt)" | jq '[.[] | select(.body | test("(?m)^Closes tickets/\\w")) | {number}]'; npx tickets meta | jq --argjson t "$(npx tickets list)" '[select(.lastImportedAt == null and ($t | length) == 0) | "first import"]'; } | jq -s add
+    { gh issue list --state all --limit 1 --json number --search "updated:>=$(npx @openagt/skill-tickets@0.1 meta | jq -r .lastImportedAt)"; gh pr list --state merged --limit 100 --json number,body --search "merged:>=$(npx @openagt/skill-tickets@0.1 meta | jq -r .lastImportedAt)" | jq '[.[] | select(.body | test("(?m)^Closes tickets/\\w")) | {number}]'; npx @openagt/skill-tickets@0.1 meta | jq --argjson t "$(npx @openagt/skill-tickets@0.1 list)" '[select(.lastImportedAt == null and ($t | length) == 0) | "first import"]'; } | jq -s add
 ---
 
 Bring the tickets up to date with the project's issue tracker and its merged pull requests. Nobody will answer you: never ask, decide yourself.
diff --git a/packages/skill-update-tickets/package.json b/packages/skill-update-tickets/package.json
index 050db4c52..e8e43d055 100644
--- a/packages/skill-update-tickets/package.json
+++ b/packages/skill-update-tickets/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-update-tickets",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The update-tickets command for coding agents: bring the project's tickets up to date with its issue tracker and its merged pull requests, unattended. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-ux/package.json b/packages/skill-ux/package.json
index 67051a836..bcba5f566 100644
--- a/packages/skill-ux/package.json
+++ b/packages/skill-ux/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-ux",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The ux command for coding agents: review every UI flow of a part of the product, rate its user experience, and improve the badly rated flows. A skill file only, no code.",
   "license": "MIT",
   "repository": {
diff --git a/packages/skill-work-queue/SKILL.md b/packages/skill-work-queue/SKILL.md
index c15acd86b..6c4da1190 100644
--- a/packages/skill-work-queue/SKILL.md
+++ b/packages/skill-work-queue/SKILL.md
@@ -5,7 +5,7 @@ disable-model-invocation: true
 schedule:
   waits-for: when the queue holds a task nobody has claimed
   when: |-
-    npx queue | jq --argjson t "$(npx tickets list)" '[.[] | . as $e | select($t | any(.[]; .locked and ((.file | rtrimstr(".md")) as $s | $e | contains($s))) | not)]'
+    npx @openagt/skill-queue@0.1 | jq --argjson t "$(npx @openagt/skill-tickets@0.1 list)" '[.[] | . as $e | select($t | any(.[]; .locked and ((.file | rtrimstr(".md")) as $s | $e | contains($s))) | not)]'
 ---
 
 Work one task off the project's agent queue. Nobody will answer you: never ask, decide yourself.
diff --git a/packages/skill-work-queue/package.json b/packages/skill-work-queue/package.json
index 21cc7700a..c4285bfb1 100644
--- a/packages/skill-work-queue/package.json
+++ b/packages/skill-work-queue/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@openagt/skill-work-queue",
-  "version": "0.0.2",
+  "version": "0.1.0",
   "description": "The work-queue command for coding agents: work one queued task off the project's agent queue, unattended. A skill file only, no code.",
   "license": "MIT",
   "repository": {