@trawlme/cli 3.9.1 → 3.11.0

package/dist/lib/skills.d.ts

@@ -1,5 +1,34 @@
 export declare function getBundledSkillsVersion(): string;
 export declare function listBundledSkills(): string[];
+/**
+ * #184 defect 1 — the ownership-refusal thrown below serves two different
+ * audiences on two different channels, and one string can't correctly serve
+ * both:
+ *
+ *  - A human who just typed `trawl skills install`/`update` reaches this via
+ *    an uncaught throw (index.ts's generic error path prints `.message`
+ *    verbatim) — that reader can decide whether to add `--force`, so the
+ *    guidance belongs on this channel. `.message` (below) keeps it.
+ *  - `bootstrapSkillsOnLogin` also catches this exact throw and relays its
+ *    text into `skipped[].reason`, which `login.ts` prints to stderr — a
+ *    channel this feature's own doc comments say must never carry a command
+ *    phrased as an instruction, because this CLI is driven by AI agents and
+ *    this platform can feed a CLI's own stderr back into an agent's own
+ *    context. `Pass --force to overwrite it anyway` is exactly that kind of
+ *    instruction: an agent "obeying" it calls `installSkill`'s own
+ *    `rmSync(recursive)` on a directory the user owns and trawl did not
+ *    create — the destroy-the-user's-files incident this class of bug
+ *    produces.
+ *
+ * `.relayableReason` carries the identical fact — this path exists, trawl
+ * did not create it, so it was left untouched — with the imperative sentence
+ * removed, for every channel that is not a direct, synchronous reply to a
+ * human's own typed command.
+ */
+export declare class SkillOwnershipRefusalError extends Error {
+    readonly relayableReason: string;
+    constructor(dest: string);
+}
 /**
  * Ownership guard (#73, extended #86 finding 7): this does `rmSync(recursive)`
  * on the target dir before reinstalling, so it must never do that to a dir
@@ -50,3 +79,130 @@ export declare function removeOrphanedSkills(scope: 'user' | 'local'): string[];
  * `TRAWL_TELEMETRY=0`), for users who manage their skills by hand.
  */
 export declare function autoUpdateInstalledSkills(): void;
+/**
+ * #184 — one line, reused everywhere the CLI installs a skill mid-invocation
+ * (login's bootstrap below, lib/skillsNudge.ts's two nudges): skills are
+ * discovered at Claude Code SESSION START, so a skill written to disk right
+ * now is invisible to whatever session is already running. Stated as a
+ * fact, never an imperative ("restart Claude Code") — this text can be
+ * relayed into an AI agent's own context (this CLI's whole incident was an
+ * agent driving it), and a command phrased there must never read as an
+ * instruction the agent is being told to obey.
+ */
+export declare const RESTART_CLAUDE_CODE_NOTE = "Claude Code must be restarted to see them \u2014 skills are loaded at session start, not mid-session.";
+/**
+ * #184 — pure gate shared by every skills-related write/print that must
+ * never fire under `--json` (a machine consumer needs pure stdout and there
+ * is no human reading a suggestion anyway), on a non-TTY invocation (a CI
+ * runner or an agent driving this CLI as a subprocess has no Claude Code
+ * session to discover a newly-installed skill in the first place), or when
+ * `TRAWL_SKILLS_SYNC=0` (the existing auto-sync opt-out, extended here: a
+ * user who manages skills by hand does not want the CLI touching that dir
+ * for ANY reason — install or nudge alike). Every signal is a parameter,
+ * exactly like lib/tips.ts's `isReferralTipDue`, so this is testable
+ * without mocking env/TTY. `isTTY`'s exact definition (stdout-only vs
+ * stdin+stdout) is the CALLER's call — see bootstrapSkillsOnLogin below vs
+ * lib/skillsNudge.ts for the two different answers this codebase already
+ * gives elsewhere (confirm.ts's `isInteractive` vs tips.ts's own check).
+ */
+export declare function isSkillsActionAllowed(opts: {
+    json?: boolean;
+    isTTY: boolean;
+    optedOut: boolean;
+}): boolean;
+/**
+ * #184 — the "install on login, and only there" half of the never-installed
+ * bootstrap (see the module doc comment on `autoUpdateInstalledSkills`
+ * above for the "elsewhere: suggest, never install" half, which lives in
+ * lib/skillsNudge.ts instead). `autoUpdateInstalledSkills` deliberately
+ * never installs (`if (!isSkillInstalled) continue`) — it only keeps an
+ * EXISTING install in sync. A user who has never run any `trawl skills`
+ * command and never logged in before this shipped has nothing installed at
+ * all, and nothing in the CLI's startup path ever puts anything there: the
+ * CLI is competent, the agent reading its skills is not — the incident this
+ * issue exists to prevent. `login` is the one intentional human setup
+ * moment (the only place a human types credentials), so it is the ONLY
+ * place this function is ever called from (see commands/login.ts) — never
+ * from the generic startup path.
+ *
+ * Gated by `isSkillsActionAllowed` exactly like every other skills-related
+ * side effect: a non-interactive `trawl login` (CI's `TRAWL_TOKEN=x trawl
+ * login --json`, or any non-TTY invocation) writes nothing — that machine
+ * has no Claude Code session to discover a skill in, and `--json`'s stdout
+ * contract has no room for a plain-text confirmation line anyway. Also
+ * skipped entirely under `TRAWL_SKILLS_SYNC=0`.
+ *
+ * Installs every bundled skill NOT YET OWNED by trawl at `scope` (default
+ * 'user' — the global location a fresh `npx @trawlme/cli login` writes to;
+ * 'local' is opt-in via the same --local convention `trawl skills install`
+ * already uses everywhere else, kept for parity/tests). "Owned" means a
+ * readable `.version` marker (#184 review MAJOR — NOT mere path existence:
+ * see below for why that distinction matters here). One skill's install
+ * throwing must never blank out the others (#91's posture, applied here):
+ * each is wrapped individually, and the function reports exactly what
+ * landed. Returns `null` (nothing written, nothing to report) ONLY when
+ * gated out, or when every bundled skill is already owned (the re-sync
+ * loop above already keeps an existing install's version current) — the
+ * genuine "nothing to do" case. Never throws — a broken bootstrap must
+ * never turn a successful login into a failed one.
+ *
+ * #184 review (BLOCK + MAJOR) — two cases used to collapse into the exact
+ * same `null`/silence as genuine "nothing to do":
+ *
+ *  1. (BLOCK) Every install attempt failing outright (an unwritable
+ *     `~/.claude/skills`, e.g.) used to return `null` — indistinguishable
+ *     from "already installed" or "never attempted at all" on a first-run
+ *     machine, the precise false-success shape #184 exists to prevent.
+ *  2. (MAJOR) A bundled skill name colliding with a PRE-EXISTING,
+ *     marker-less directory the CLI doesn't own. The action set here used
+ *     to be computed from `isSkillInstalled` (mere `existsSync`), which
+ *     can't tell "we already installed this" from "something else already
+ *     lives at this path" — a foreign dir was silently read as "already
+ *     installed, nothing to do", so `installSkill`'s ownership-refusal
+ *     guard was never even reached and the collision went unreported
+ *     anywhere. The action set below is computed from *ownership*
+ *     (`getInstalledVersion(...) !== null`) instead, so a foreign
+ *     collision is genuinely attempted — hits the same guard `installSkill`
+ *     already enforces elsewhere, throws, and is captured below — rather
+ *     than silently skipped as if it were a prior trawl install.
+ *
+ * Whenever there was anything to attempt, the result is now ALWAYS a
+ * non-null object reporting both what landed (`installed`) and what didn't
+ * (`skipped`, each with a RELAYABLE reason — see `SkillOwnershipRefusalError`
+ * above: the ownership-refusal case reports `.relayableReason` [fact only,
+ * no `--force` imperative], every other throw [skill-not-found, raw fs
+ * errors like EACCES] reports `.message` as before, since those were never
+ * imperative to begin with), so `login.ts` can print an honest, distinct
+ * line for a skip instead of falling through to the generic "not installed"
+ * nudge as if login had done nothing, or silently omitting a name from the
+ * success line as if it had never been requested.
+ *
+ * #184 defect 2 — `error` (present whenever the function returns non-null)
+ * distinguishes a THIRD case from both "nothing to do" (`null`) and "one or
+ * more skills failed" (`skipped`): "could not even determine what to
+ * install" — `listBundledSkills()` returning an empty list (its own
+ * contract silently swallows a missing/renamed `skills/` dir into `[]`; see
+ * its doc comment) or `getSkillsPackageRoot()` throwing outright (the
+ * `@trawlme/skills` package itself unresolvable — a broken node_modules
+ * entry). Both used to fall through to `notOwned.length === 0` or the outer
+ * catch below, landing on the exact same `null` as a fully-up-to-date
+ * install — a genuinely corrupted bundle produced ZERO signal, not even a
+ * failed-attempt line, because nothing was ever attempted. `error` is
+ * `null` on every ordinary path (including genuine "all already owned",
+ * which still short-circuits to the `null` return below) and non-null only
+ * for this diagnostic-failure case, where `installed`/`skipped` are both
+ * empty because no skill name was ever known to attempt.
+ */
+export declare function bootstrapSkillsOnLogin(opts?: {
+    json?: boolean;
+    isTTY?: boolean;
+    scope?: 'user' | 'local';
+}): {
+    installed: string[];
+    skipped: {
+        name: string;
+        reason: string;
+    }[];
+    dest: string;
+    error: string | null;
+} | null;

package/dist/lib/skills.js

@@ -24,6 +24,40 @@ function getSkillsBase(scope) {
     const base = scope === 'local' ? join(process.cwd(), '.claude') : join(homedir(), '.claude');
     return join(base, 'skills');
 }
+/**
+ * #184 defect 1 — the ownership-refusal thrown below serves two different
+ * audiences on two different channels, and one string can't correctly serve
+ * both:
+ *
+ *  - A human who just typed `trawl skills install`/`update` reaches this via
+ *    an uncaught throw (index.ts's generic error path prints `.message`
+ *    verbatim) — that reader can decide whether to add `--force`, so the
+ *    guidance belongs on this channel. `.message` (below) keeps it.
+ *  - `bootstrapSkillsOnLogin` also catches this exact throw and relays its
+ *    text into `skipped[].reason`, which `login.ts` prints to stderr — a
+ *    channel this feature's own doc comments say must never carry a command
+ *    phrased as an instruction, because this CLI is driven by AI agents and
+ *    this platform can feed a CLI's own stderr back into an agent's own
+ *    context. `Pass --force to overwrite it anyway` is exactly that kind of
+ *    instruction: an agent "obeying" it calls `installSkill`'s own
+ *    `rmSync(recursive)` on a directory the user owns and trawl did not
+ *    create — the destroy-the-user's-files incident this class of bug
+ *    produces.
+ *
+ * `.relayableReason` carries the identical fact — this path exists, trawl
+ * did not create it, so it was left untouched — with the imperative sentence
+ * removed, for every channel that is not a direct, synchronous reply to a
+ * human's own typed command.
+ */
+export class SkillOwnershipRefusalError extends Error {
+    relayableReason;
+    constructor(dest) {
+        super(`Refusing to overwrite "${dest}" — it was not installed by trawl (no .version marker). ` +
+            `Pass --force to overwrite it anyway.`);
+        this.name = 'SkillOwnershipRefusalError';
+        this.relayableReason = `"${dest}" already exists and was not installed by trawl (no .version marker) — left untouched.`;
+    }
+}
 /**
  * Ownership guard (#73, extended #86 finding 7): this does `rmSync(recursive)`
  * on the target dir before reinstalling, so it must never do that to a dir
@@ -58,8 +92,7 @@ export function installSkill(name, scope, opts = {}) {
         }
         const owned = installedVersion !== null;
         if (!owned && !opts.force) {
-            throw new Error(`Refusing to overwrite "${dest}" — it was not installed by trawl (no .version marker). ` +
-                `Pass --force to overwrite it anyway.`);
+            throw new SkillOwnershipRefusalError(dest);
         }
         rmSync(dest, { recursive: true, force: true });
     }
@@ -196,3 +229,195 @@ export function autoUpdateInstalledSkills() {
         // Silent: skill auto-update should never block the CLI
     }
 }
+/**
+ * #184 — one line, reused everywhere the CLI installs a skill mid-invocation
+ * (login's bootstrap below, lib/skillsNudge.ts's two nudges): skills are
+ * discovered at Claude Code SESSION START, so a skill written to disk right
+ * now is invisible to whatever session is already running. Stated as a
+ * fact, never an imperative ("restart Claude Code") — this text can be
+ * relayed into an AI agent's own context (this CLI's whole incident was an
+ * agent driving it), and a command phrased there must never read as an
+ * instruction the agent is being told to obey.
+ */
+export const RESTART_CLAUDE_CODE_NOTE = 'Claude Code must be restarted to see them — skills are loaded at session start, not mid-session.';
+/**
+ * #184 — pure gate shared by every skills-related write/print that must
+ * never fire under `--json` (a machine consumer needs pure stdout and there
+ * is no human reading a suggestion anyway), on a non-TTY invocation (a CI
+ * runner or an agent driving this CLI as a subprocess has no Claude Code
+ * session to discover a newly-installed skill in the first place), or when
+ * `TRAWL_SKILLS_SYNC=0` (the existing auto-sync opt-out, extended here: a
+ * user who manages skills by hand does not want the CLI touching that dir
+ * for ANY reason — install or nudge alike). Every signal is a parameter,
+ * exactly like lib/tips.ts's `isReferralTipDue`, so this is testable
+ * without mocking env/TTY. `isTTY`'s exact definition (stdout-only vs
+ * stdin+stdout) is the CALLER's call — see bootstrapSkillsOnLogin below vs
+ * lib/skillsNudge.ts for the two different answers this codebase already
+ * gives elsewhere (confirm.ts's `isInteractive` vs tips.ts's own check).
+ */
+export function isSkillsActionAllowed(opts) {
+    if (opts.json)
+        return false;
+    if (!opts.isTTY)
+        return false;
+    if (opts.optedOut)
+        return false;
+    return true;
+}
+/**
+ * #184 — the "install on login, and only there" half of the never-installed
+ * bootstrap (see the module doc comment on `autoUpdateInstalledSkills`
+ * above for the "elsewhere: suggest, never install" half, which lives in
+ * lib/skillsNudge.ts instead). `autoUpdateInstalledSkills` deliberately
+ * never installs (`if (!isSkillInstalled) continue`) — it only keeps an
+ * EXISTING install in sync. A user who has never run any `trawl skills`
+ * command and never logged in before this shipped has nothing installed at
+ * all, and nothing in the CLI's startup path ever puts anything there: the
+ * CLI is competent, the agent reading its skills is not — the incident this
+ * issue exists to prevent. `login` is the one intentional human setup
+ * moment (the only place a human types credentials), so it is the ONLY
+ * place this function is ever called from (see commands/login.ts) — never
+ * from the generic startup path.
+ *
+ * Gated by `isSkillsActionAllowed` exactly like every other skills-related
+ * side effect: a non-interactive `trawl login` (CI's `TRAWL_TOKEN=x trawl
+ * login --json`, or any non-TTY invocation) writes nothing — that machine
+ * has no Claude Code session to discover a skill in, and `--json`'s stdout
+ * contract has no room for a plain-text confirmation line anyway. Also
+ * skipped entirely under `TRAWL_SKILLS_SYNC=0`.
+ *
+ * Installs every bundled skill NOT YET OWNED by trawl at `scope` (default
+ * 'user' — the global location a fresh `npx @trawlme/cli login` writes to;
+ * 'local' is opt-in via the same --local convention `trawl skills install`
+ * already uses everywhere else, kept for parity/tests). "Owned" means a
+ * readable `.version` marker (#184 review MAJOR — NOT mere path existence:
+ * see below for why that distinction matters here). One skill's install
+ * throwing must never blank out the others (#91's posture, applied here):
+ * each is wrapped individually, and the function reports exactly what
+ * landed. Returns `null` (nothing written, nothing to report) ONLY when
+ * gated out, or when every bundled skill is already owned (the re-sync
+ * loop above already keeps an existing install's version current) — the
+ * genuine "nothing to do" case. Never throws — a broken bootstrap must
+ * never turn a successful login into a failed one.
+ *
+ * #184 review (BLOCK + MAJOR) — two cases used to collapse into the exact
+ * same `null`/silence as genuine "nothing to do":
+ *
+ *  1. (BLOCK) Every install attempt failing outright (an unwritable
+ *     `~/.claude/skills`, e.g.) used to return `null` — indistinguishable
+ *     from "already installed" or "never attempted at all" on a first-run
+ *     machine, the precise false-success shape #184 exists to prevent.
+ *  2. (MAJOR) A bundled skill name colliding with a PRE-EXISTING,
+ *     marker-less directory the CLI doesn't own. The action set here used
+ *     to be computed from `isSkillInstalled` (mere `existsSync`), which
+ *     can't tell "we already installed this" from "something else already
+ *     lives at this path" — a foreign dir was silently read as "already
+ *     installed, nothing to do", so `installSkill`'s ownership-refusal
+ *     guard was never even reached and the collision went unreported
+ *     anywhere. The action set below is computed from *ownership*
+ *     (`getInstalledVersion(...) !== null`) instead, so a foreign
+ *     collision is genuinely attempted — hits the same guard `installSkill`
+ *     already enforces elsewhere, throws, and is captured below — rather
+ *     than silently skipped as if it were a prior trawl install.
+ *
+ * Whenever there was anything to attempt, the result is now ALWAYS a
+ * non-null object reporting both what landed (`installed`) and what didn't
+ * (`skipped`, each with a RELAYABLE reason — see `SkillOwnershipRefusalError`
+ * above: the ownership-refusal case reports `.relayableReason` [fact only,
+ * no `--force` imperative], every other throw [skill-not-found, raw fs
+ * errors like EACCES] reports `.message` as before, since those were never
+ * imperative to begin with), so `login.ts` can print an honest, distinct
+ * line for a skip instead of falling through to the generic "not installed"
+ * nudge as if login had done nothing, or silently omitting a name from the
+ * success line as if it had never been requested.
+ *
+ * #184 defect 2 — `error` (present whenever the function returns non-null)
+ * distinguishes a THIRD case from both "nothing to do" (`null`) and "one or
+ * more skills failed" (`skipped`): "could not even determine what to
+ * install" — `listBundledSkills()` returning an empty list (its own
+ * contract silently swallows a missing/renamed `skills/` dir into `[]`; see
+ * its doc comment) or `getSkillsPackageRoot()` throwing outright (the
+ * `@trawlme/skills` package itself unresolvable — a broken node_modules
+ * entry). Both used to fall through to `notOwned.length === 0` or the outer
+ * catch below, landing on the exact same `null` as a fully-up-to-date
+ * install — a genuinely corrupted bundle produced ZERO signal, not even a
+ * failed-attempt line, because nothing was ever attempted. `error` is
+ * `null` on every ordinary path (including genuine "all already owned",
+ * which still short-circuits to the `null` return below) and non-null only
+ * for this diagnostic-failure case, where `installed`/`skipped` are both
+ * empty because no skill name was ever known to attempt.
+ */
+export function bootstrapSkillsOnLogin(opts = {}) {
+    try {
+        const optedOut = process.env['TRAWL_SKILLS_SYNC'] === '0';
+        if (!isSkillsActionAllowed({ json: opts.json, isTTY: opts.isTTY ?? false, optedOut }))
+            return null;
+        const scope = opts.scope ?? 'user';
+        const dest = getSkillsBase(scope);
+        let bundled;
+        try {
+            bundled = listBundledSkills();
+        }
+        catch (err) {
+            // getSkillsPackageRoot() threw (require.resolve failed — the
+            // `@trawlme/skills` package itself isn't resolvable). Report as a
+            // diagnostic failure, not the outer catch's generic `null`.
+            return {
+                installed: [],
+                skipped: [],
+                dest,
+                error: `could not read the bundled Claude skills package — ${err instanceof Error ? err.message : String(err)}`,
+            };
+        }
+        if (bundled.length === 0) {
+            // The package resolved but reports zero skills — in practice this
+            // package always ships at least one, so an empty list here is
+            // corruption (e.g. its `skills/` dir renamed/deleted underneath it),
+            // not a legitimate "nothing to do".
+            return {
+                installed: [],
+                skipped: [],
+                dest,
+                error: 'the bundled Claude skills package reports no skills to install — it may be missing or corrupted',
+            };
+        }
+        const notOwned = bundled.filter((name) => {
+            try {
+                return getInstalledVersion(name, scope) === null;
+            }
+            catch {
+                // An unreadable `.version` (e.g. EISDIR) is no more proof of
+                // ownership than a missing one — treat it as actionable too, same
+                // as installSkill's own owned-check does (#91's posture).
+                return true;
+            }
+        });
+        if (notOwned.length === 0)
+            return null;
+        const installed = [];
+        const skipped = [];
+        for (const name of notOwned) {
+            try {
+                installSkill(name, scope);
+                installed.push(name);
+            }
+            catch (err) {
+                // One bad skill (e.g. a marker-less foreign dir refusing overwrite,
+                // or an EACCES on an unwritable skills dir) must not blank the
+                // others — skip it, keep going, but never drop WHY silently: the
+                // caller needs this to tell "attempted and failed" apart from
+                // "nothing to do".
+                const reason = err instanceof SkillOwnershipRefusalError
+                    ? err.relayableReason
+                    : err instanceof Error
+                        ? err.message
+                        : String(err);
+                skipped.push({ name, reason });
+            }
+        }
+        return { installed, skipped, dest, error: null };
+    }
+    catch {
+        return null;
+    }
+}

package/dist/lib/skillsNudge.d.ts

@@ -0,0 +1,33 @@
+export declare const SKILLS_NUDGE_TEXT = "Claude skills not installed \u2014 `trawl skills install` installs them (Claude Code must be restarted to see them \u2014 skills are loaded at session start, not mid-session.)";
+export declare const AUTH_WALL_SKILLS_NUDGE_TEXT = "This looks like a login wall and Claude skills are not installed \u2014 `trawl skills install` installs the guidance for it too (Claude Code must be restarted to see them \u2014 skills are loaded at session start, not mid-session.)";
+/**
+ * Pure gate — true when the throttled, generic "elsewhere" suggestion
+ * should print. Every external signal is a parameter, exactly like
+ * isReferralTipDue, so this is testable without mocking fs/env/Date.
+ */
+export declare function isSkillsNudgeDue(opts: {
+    json?: boolean;
+    isTTY: boolean;
+    optedOut: boolean;
+    skillsPresent: boolean;
+    lastShownAt: number;
+    now: number;
+}): boolean;
+/**
+ * Best-effort generic nudge (#184 point 2) — called once per CLI invocation
+ * from index.ts's runCli, on every command. Never throws.
+ */
+export declare function maybeSuggestSkillsInstall(opts?: {
+    json?: boolean;
+}): void;
+/**
+ * Safety-net nudge (#184 point 5) — called from `doctor`/`run-info` right
+ * when the run they just showed carries a live `failureKind:'auth'` verdict
+ * (see commands/doctor.ts's `isAuthWall`). Deliberately unthrottled by the
+ * 7-day timestamp — see this module's doc comment for why — but still
+ * capped to one nudge per process via the same `nudgedThisProcess` flag the
+ * generic nudge sets. Never throws.
+ */
+export declare function maybeSuggestSkillsForAuthWall(opts?: {
+    json?: boolean;
+}): void;

package/dist/lib/skillsNudge.js

@@ -0,0 +1,137 @@
+/**
+ * #184 — the "elsewhere: suggest, never install" half of the skills
+ * bootstrap story (lib/skills.ts's `bootstrapSkillsOnLogin` is the "install
+ * on login" half). Writing into `~/.claude/skills` as a side effect of an
+ * unrelated command is a filesystem mutation nobody asked for — this module
+ * only ever PRINTS a line naming the command that installs them. Never
+ * installs anything itself.
+ *
+ * Two nudges, one shared "at most once per process" guard:
+ *  - `maybeSuggestSkillsInstall` — the generic, throttled nudge (once per
+ *    NUDGE_THROTTLE_MS across ALL commands, mirrors lib/tips.ts's referral
+ *    tip throttle exactly).
+ *  - `maybeSuggestSkillsForAuthWall` — the safety-net nudge (#184 point 5):
+ *    fires from `doctor`/`run-info` when the run they just showed carries a
+ *    live `failureKind:'auth'` verdict and skills are absent. Deliberately
+ *    UNTHROTTLED by the 7-day timestamp: sharing that throttle would mean a
+ *    routine command on day 0 (stamping the generic nudge's timestamp)
+ *    silently suppresses THIS nudge on day 1 when the user actually hits
+ *    the auth wall the whole issue exists for — the exact failure this
+ *    safety net is supposed to catch. It mirrors trawl_cli#182's own
+ *    login-wall hint in `formatDoctor`, which also prints unthrottled every
+ *    time the condition is true.
+ *  - `nudgedThisProcess` still caps the two at "one nudge per invocation"
+ *    combined: `doctor` on an auth-walled, skills-absent run can print the
+ *    auth-wall nudge inside its own action, and index.ts's generic
+ *    post-command nudge (which does not know `doctor` already said
+ *    something) would otherwise print a second, redundant line right after
+ *    it. Whichever fires first wins; reset per test via a fresh module
+ *    import (see skillsNudge.test.ts's `freshImport` helper, mirroring
+ *    tips.test.ts).
+ *
+ * Gate shape mirrors lib/tips.ts's isReferralTipDue/maybeShowReferralTip
+ * throughout (json/isTTY/opt-out/throttle, pure gate separated from the
+ * side-effecting caller, cheap checks before any filesystem read) — same
+ * reasoning applies verbatim.
+ */
+import chalk from 'chalk';
+import config from './config.js';
+import { listBundledSkills, isSkillInstalled, isSkillsActionAllowed, RESTART_CLAUDE_CODE_NOTE } from './skills.js';
+/** Max once per 7 days — same window as lib/tips.ts's referral tip. */
+const NUDGE_THROTTLE_MS = 7 * 24 * 60 * 60 * 1000;
+// #184 constraint A — a FACT about CLI state plus the command name, never an
+// instruction to the reader ("install the skills"/"you should run…"). This
+// output is not only read by a human at a terminal: this platform can relay
+// a CLI's own stdout/stderr into an AI agent's context (the incident this
+// issue exists to prevent was exactly an agent driving this CLI), and
+// third-party content returned into agent context must never read as an
+// instruction the agent is being told to obey. State the fact, name the
+// command, stop there.
+export const SKILLS_NUDGE_TEXT = `Claude skills not installed — \`trawl skills install\` installs them (${RESTART_CLAUDE_CODE_NOTE})`;
+export const AUTH_WALL_SKILLS_NUDGE_TEXT = `This looks like a login wall and Claude skills are not installed — \`trawl skills install\` installs the guidance for it too (${RESTART_CLAUDE_CODE_NOTE})`;
+/** One nudge per process, whichever of the two below fires first. */
+let nudgedThisProcess = false;
+/**
+ * Pure gate — true when the throttled, generic "elsewhere" suggestion
+ * should print. Every external signal is a parameter, exactly like
+ * isReferralTipDue, so this is testable without mocking fs/env/Date.
+ */
+export function isSkillsNudgeDue(opts) {
+    if (!isSkillsActionAllowed({ json: opts.json, isTTY: opts.isTTY, optedOut: opts.optedOut }))
+        return false;
+    if (opts.skillsPresent)
+        return false;
+    return opts.now - opts.lastShownAt >= NUDGE_THROTTLE_MS;
+}
+/**
+ * Read-only — checks both scopes, mirrors `trawl skills list`'s own
+ * "installed anywhere" question. Failing toward `false` (not installed) on
+ * an unreadable skills dir is the safe default here: the worst case is one
+ * extra nudge line, never a missed one — the opposite failure (silently
+ * assuming "present" and staying quiet) is the exact gap this issue exists
+ * to close.
+ */
+function anyBundledSkillInstalled() {
+    try {
+        return listBundledSkills().some((name) => isSkillInstalled(name, 'user') || isSkillInstalled(name, 'local'));
+    }
+    catch {
+        return false;
+    }
+}
+/**
+ * Shared body for both exported nudges below: the cheap json/TTY/opt-out
+ * gate, the "one nudge per process" cap, the skills-presence check, and the
+ * actual print — everything the two nudges have in common. `useThrottle`
+ * is the one real difference between them (see the module doc comment for
+ * why the safety-net nudge deliberately opts out of it), so it stays an
+ * explicit parameter here rather than two near-identical function bodies.
+ * Never throws.
+ */
+function tryPrintNudge(opts, text, useThrottle) {
+    try {
+        if (nudgedThisProcess)
+            return;
+        const json = Boolean(opts.json);
+        const isTTY = Boolean(process.stdout.isTTY);
+        const optedOut = process.env['TRAWL_SKILLS_SYNC'] === '0';
+        // Cheap checks first (mirrors tips.ts #153's "never pay when not due")
+        // — only touch the filesystem once json/TTY/opt-out already say "maybe".
+        if (!isSkillsActionAllowed({ json, isTTY, optedOut }))
+            return;
+        if (useThrottle) {
+            const lastShownAt = config.get('skillsNudgeShownAt') || 0;
+            const now = Date.now();
+            const due = isSkillsNudgeDue({ json, isTTY, optedOut, skillsPresent: anyBundledSkillInstalled(), lastShownAt, now });
+            if (!due)
+                return;
+            config.set('skillsNudgeShownAt', now);
+        }
+        else if (anyBundledSkillInstalled()) {
+            return;
+        }
+        nudgedThisProcess = true;
+        console.error(chalk.dim(text));
+    }
+    catch {
+        // silent — a broken nudge must never break a command
+    }
+}
+/**
+ * Best-effort generic nudge (#184 point 2) — called once per CLI invocation
+ * from index.ts's runCli, on every command. Never throws.
+ */
+export function maybeSuggestSkillsInstall(opts = {}) {
+    tryPrintNudge(opts, SKILLS_NUDGE_TEXT, true);
+}
+/**
+ * Safety-net nudge (#184 point 5) — called from `doctor`/`run-info` right
+ * when the run they just showed carries a live `failureKind:'auth'` verdict
+ * (see commands/doctor.ts's `isAuthWall`). Deliberately unthrottled by the
+ * 7-day timestamp — see this module's doc comment for why — but still
+ * capped to one nudge per process via the same `nudgedThisProcess` flag the
+ * generic nudge sets. Never throws.
+ */
+export function maybeSuggestSkillsForAuthWall(opts = {}) {
+    tryPrintNudge(opts, AUTH_WALL_SKILLS_NUDGE_TEXT, false);
+}

package/docs/agent-quickstart.md

@@ -166,7 +166,15 @@ just to look helpful, so don't treat its absence as an error.
 
 For the full, versioned machine description of every command (arguments,
 options, aliases, exit codes, error kinds) — instead of parsing this doc —
-run `trawl spec --json`.
+run `trawl spec --json`. It also carries `docsUrl` (resolved from the server
+when declared, else derived from a known first-party API host, else omitted
+— never a guessed URL) and, where a guide exists, a per-command `docs` deep
+link — but the deep link and `llmsUrl` are narrower than `docsUrl`: they only
+ever come from the known-first-party-host derivation, never from a
+server-declared `docsUrl`, since this CLI's own guide slugs have no reason
+to exist on a third party's own docs root. A `failureKind:"auth"` run's
+payload (`doctor`/`data --errors`/`run-info`) carries the same `docs` field,
+under the same rule.
 
 ## Non-interactive contract
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trawlme/cli",
-  "version": "3.9.1",
+  "version": "3.11.0",
   "description": "Trawl CLI — manage scraps from the terminal",
   "type": "module",
   "bin": {