From 2f1a475e13fb8342664aa4769a39b6a460c93f33 Mon Sep 17 00:00:00 2001 From: Suleiman Shahbari Date: Sat, 12 Sep 2026 21:01:37 +0300 Subject: [PATCH] Two SKILL.md sentences reworded: close once the work is done and published, not merged; install only when running the command fails for a missing node_modules Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01UMVVNvrAaovKrXTG2wKcqy --- packages/skill-logs/SKILL.md | 2 +- packages/skill-queue/SKILL.md | 2 +- packages/skill-tickets/SKILL.md | 8 ++++---- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/packages/skill-logs/SKILL.md b/packages/skill-logs/SKILL.md index 2dc94756b..8f4d43752 100644 --- a/packages/skill-logs/SKILL.md +++ b/packages/skill-logs/SKILL.md @@ -7,7 +7,7 @@ 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//`: the card, `.json` — what was asked, the ticket, the branch, the pull request, how it ended, what it cost — and the diary, `.jsonl` — what the agent said along the way, its result. -Read them with the `logs` command, a dependency of this repository (`@gemstack/skill-logs`). With no `node_modules`, install first with the lockfile's package manager (`npm install` for `package-lock.json`). Then run it as `npx logs`. The command only reads: the program that ran an agent records its run, at its end. A refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage. +Read them with the `logs` command, a dependency of this repository (`@gemstack/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. The command only reads: the program that ran an agent records its run, at its end. A refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage. ## Read diff --git a/packages/skill-queue/SKILL.md b/packages/skill-queue/SKILL.md index c171b3de8..48ef668c0 100644 --- a/packages/skill-queue/SKILL.md +++ b/packages/skill-queue/SKILL.md @@ -7,7 +7,7 @@ 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 (`@gemstack/skill-queue`). With no `node_modules`, install first with the lockfile's package manager (`npm install` for `package-lock.json`). Then run it as `npx queue`. Every change it makes is one commit pushed straight to the `agent-data` branch. 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, a dependency of this repository (`@gemstack/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 pushed straight to the `agent-data` branch. A refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage. ## Read diff --git a/packages/skill-tickets/SKILL.md b/packages/skill-tickets/SKILL.md index 6fd780e84..b45c41d49 100644 --- a/packages/skill-tickets/SKILL.md +++ b/packages/skill-tickets/SKILL.md @@ -7,7 +7,7 @@ description: Where the project's tickets live, how to read and change them, how The tickets (`tickets/_.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, shows a possibly stale copy; never write there. The command reads fresh. -Read and change them with the `tickets` command, a dependency of this repository (`@gemstack/skill-tickets`). With no `node_modules`, install first with the lockfile's package manager (`npm install` for `package-lock.json`). Then run it as `npx tickets`. Every change it makes is one commit pushed straight to the `agent-data` branch. A refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage. +Read and change them with the `tickets` command, a dependency of this repository (`@gemstack/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 pushed straight to the `agent-data` branch. A refusal exits 1 with a line on stderr; a wrong command line exits 2 with the usage. ## Read @@ -25,8 +25,8 @@ npx tickets show one ticket: its text, its plan, who holds it npx tickets put write one file under tickets/ from stdin, the whole file, creating it if new; empty stdin writes an empty file (npx tickets put < draft.md): a ticket or a plan -npx tickets close once the work is merged: remove the ticket with its plan and lock; - refused while someone else holds it; its queue entry, if any, +npx tickets close once the work is done and published: remove the ticket with its plan + and lock; refused while someone else holds it; its queue entry, if any, stays: `npx queue done` it ``` @@ -38,7 +38,7 @@ When the repository has the `queue` skill, a ticket goes on the agent queue as a npx queue add "[](tickets/<file>)" --priority <N> ``` -Once the work is merged, `npx tickets close <file>` and `npx queue done` the entry. +Once the work is done and published, `npx tickets close <file>` and `npx queue done` the entry. ## Claim before you plan or work a ticket