agent-skillboard 0.2.16 → 0.2.18

package/CHANGELOG.md

@@ -2,6 +2,39 @@
 
 ## Unreleased
 
+## 0.2.18 — 2026-07-07
+
+### Changed
+
+- Deprecated `skillboard init` from the normal first-use path across README,
+  install docs, reference docs, CLI help, postinstall/setup guidance, and
+  generated agent guidance.
+- Reframed normal onboarding around global install/postinstall and agent-layer
+  `skillboard setup`, with `init` reserved for legacy project-local policy
+  workspaces.
+- Updated `doctor` help and recommendations so it no longer reads as an
+  `init` prerequisite for new users.
+
+### Fixed
+
+- Added regression coverage that prevents primary README/install/reference/help
+  surfaces from reintroducing `init` or bare project-bootstrap wording as the
+  normal setup flow.
+
+## 0.2.17 — 2026-07-07
+
+### Changed
+
+- Reworked the README opening and quick start so developers using multiple
+  agents, skill packs, plugins, MCP tools, or marketplaces can understand
+  SkillBoard's purpose and try the CLI with read-only `npm exec` commands before
+  installing it globally.
+
+### Fixed
+
+- Kept packaged npm smoke tests compatible with Node 20 release checks that run
+  inside an outer `npx -p node@20 -c ...` invocation.
+
 ## 0.2.16 — 2026-07-06
 
 ### Changed

package/README.md

@@ -2,6 +2,12 @@
 
 Keep AI-agent skills broadly available, then route overlaps consistently.
 
+If you use more than one coding agent, skill pack, plugin, MCP tool, or
+marketplace, SkillBoard answers the practical questions before you install
+anything or change workflow policy: which skills are usable now, which one
+should win when skills overlap, which external skills need review, and how
+Codex, Claude, OpenCode, and Hermes can follow the same policy.
+
 Ask your AI normal work requests: "write tests before implementation",
 "review this plan and point out weak assumptions", "help me refine this UX
 flow", or explicit control requests like "use the Codex test-first skill in
@@ -12,14 +18,15 @@ when similar skills overlap, and a short disclosure of what was used.
 
 The burden stays low:
 
-- No global install is required; use `npx --yes --package agent-skillboard`.
-- Most use is read-only: `brief`, `route`, `doctor`, and `guard use` answer
-  what can run now and which route fits the request.
+- No global install is required for a trial; use
+  `npm exec --yes --package agent-skillboard@latest -- skillboard`.
+- Most use is read-only: `brief`, `route`, and `guard use` answer what can run
+  now and which route fits the request; `doctor` checks local policy and source
+  health without writing changes.
 - Nothing changes until you approve a policy action.
-- Project cleanup is previewable with `skillboard uninstall --dry-run`; default
-  uninstall removes SkillBoard settings and generated project state while
-  preserving local skills. Add `--keep-settings` only when you want to keep
-  project policy and bridge guidance.
+- Agent-layer cleanup is previewable with
+  `skillboard uninstall --agent-layer --dry-run`; it removes only managed
+  SkillBoard guidance while preserving other agent skills.
 
 Status: public alpha. The current config schema is config schema v1; breaking
 changes may still happen before `1.0.0` and are documented in release notes.
@@ -59,12 +66,25 @@ Names you may see in setup and logs:
 - `agent-skillboard`: the npm package.
 - `skillboard`: the CLI binary.
 
-Use SkillBoard when your agent setup has grown beyond one trusted skill folder
-and you want workflow-scoped control without turning skill governance into a
-manual checklist. If you are changing routing, brief, bridge, policy, or
-workflow UX, read [AI Skill Routing Goal](docs/ai-skill-routing-goal.md) first;
-it defines the non-blocking `observe → route → work → explain briefly → ask
-after → remember policy` loop that development should preserve.
+## Who This Is For
+
+Use SkillBoard if you use more than one coding agent, skill pack, plugin, MCP
+tool, or marketplace and want one answer to:
+
+- Which skills can this agent use right now?
+- Which skill should win when several match the same task?
+- Which external or plugin skills are reviewed, blocked, or waiting for approval?
+- How can Codex, Claude, OpenCode, and Hermes follow the same skill policy?
+
+If you use one agent with a few hand-written local skills, you probably do not
+need SkillBoard yet. SkillBoard is for setups that have grown beyond one trusted
+skill folder and need workflow-scoped control without turning skill governance
+into a manual checklist.
+
+If you are changing routing, brief, bridge, policy, or workflow UX, read
+[AI Skill Routing Goal](docs/ai-skill-routing-goal.md) first; it defines the
+non-blocking `observe → route → work → explain briefly → ask after → remember
+policy` loop that development should preserve.
 
 <p align="center">
   <img src="https://raw.githubusercontent.com/NyXXiR/skillboard/main/skillboard.png" alt="SkillBoard architecture diagram: sources, inventory scanner, SkillBoard model, policy engine, and user and agent surfaces." width="100%">
@@ -95,8 +115,17 @@ See [Tested Value Proof](#tested-value-proof) for the executable proof.
 
 ## 5-Minute Quick Start
 
-Install the CLI. On a normal global install, SkillBoard auto-connects the
-agent layer for detected Codex, Claude, OpenCode, and Hermes user skill roots:
+Try it without a global install. These read-only commands download the latest
+package for one run and do not create project files:
+
+```bash
+npm exec --yes --package agent-skillboard@latest -- skillboard --version
+npm exec --yes --package agent-skillboard@latest -- skillboard help brief
+```
+
+Install the CLI when you want SkillBoard connected to your agent layer. On a
+normal global install, SkillBoard auto-connects the agent layer for detected
+Codex, Claude, OpenCode, and Hermes user skill roots:
 
 AI/automation/operator details:
 
@@ -121,8 +150,7 @@ It does not create `skillboard.config.yaml`,
 No separate setup command is required after a normal global install or update:
 npm lifecycle scripts run agent-layer setup automatically, rerun the agent-home
 scan, refresh managed SkillBoard guidance files, and add newly detected
-supported agent roots. This setup does not run `skillboard init`; use `init`
-only inside a workspace where you want project-local policy files.
+supported agent roots. This setup is agent-layer only.
 
 Run `skillboard setup --agent codex,claude,opencode,hermes --yes` later only
 after adding another supported agent, enabling a new agent home, or installing
@@ -142,37 +170,6 @@ skill root. If the source contains agent-specific instructions, the agent asks
 before creating an adapted target-agent `SKILL.md` and installs that file with
 provenance.
 
-If you intentionally maintain local workspace policy files, use the explicit
-operator commands for that layer. `skillboard init` is needed only for a
-workspace where you want project-local policy, bridge guidance, and reports:
-
-```bash
-npx --yes --package agent-skillboard skillboard init
-npx --yes --package agent-skillboard skillboard doctor --summary
-npx --yes --package agent-skillboard skillboard brief --workflow <workflow-from-init>
-```
-
-Remove SkillBoard from a project when you are done:
-
-```bash
-npx --yes --package agent-skillboard skillboard uninstall --dir /path/to/your/project --dry-run
-npx --yes --package agent-skillboard skillboard uninstall --dir /path/to/your/project
-```
-
-Default project uninstall removes SkillBoard config, bridge guidance, and
-`.skillboard/` project state while preserving local `skills/*/SKILL.md` files.
-It reports what it removed or preserved.
-
-```bash
-npx --yes --package agent-skillboard skillboard uninstall --dir /path/to/your/project --keep-settings --dry-run
-npx --yes --package agent-skillboard skillboard uninstall --dir /path/to/your/project --keep-settings
-```
-
-Use `--keep-settings` only when you want to keep project SkillBoard policy and
-bridge guidance in place, for example while cleaning generated helper files.
-`--purge` remains accepted as an explicit spelling for the default clean
-project removal.
-
 Remove SkillBoard's managed agent-layer guidance before package removal when
 you want agent homes back to their pre-SkillBoard guidance state:
 
@@ -212,6 +209,35 @@ For action cards, use `skillboard apply-action <action-id> --yes --json`; raw
 `skillboard hook install ... --dry-run --json` previews are underlying manual
 operator detail, not the primary action-card flow.
 
+## Legacy Project Policy Mode
+
+Legacy project policy mode is for existing workspaces that still carry local
+SkillBoard policy files.
+
+`skillboard init` is deprecated project-local policy bootstrap and is not
+needed for normal use. Global install/postinstall and `skillboard setup`
+connect SkillBoard at the agent layer without creating `skillboard.config.yaml`,
+`.skillboard/`, `AGENTS.md`, or `CLAUDE.md` in projects. Agent-layer setup does
+not run `skillboard init`.
+
+The command remains for existing workspaces that intentionally maintain local
+policy files, bridge guidance, and reports. Use `skillboard help init` before
+using it in an existing workspace.
+
+Default legacy project uninstall removes SkillBoard config, bridge guidance,
+and `.skillboard/` project state while preserving local `skills/*/SKILL.md`
+files:
+
+```bash
+skillboard uninstall --dir /path/to/your/project --dry-run
+skillboard uninstall --dir /path/to/your/project
+```
+
+Use `--keep-settings` only when you want to keep legacy project policy and
+bridge guidance in place, for example while cleaning generated helper files.
+`--purge` remains accepted as an explicit spelling for the default clean
+project removal.
+
 ## What Works Today
 
 SkillBoard currently supports:
@@ -258,7 +284,7 @@ fixtures, and assertions.
 ## Where To Go Next
 
 - [AI skill routing goal](docs/ai-skill-routing-goal.md)
-- [Install and bootstrap](docs/install.md)
+- [Install and agent-layer setup](docs/install.md)
 - [First-time control flow](docs/user-flow.md)
 - [Capability routing](docs/routing.md)
 - [Command and config reference](docs/reference.md)

package/bin/postinstall.mjs

@@ -9,7 +9,7 @@ if (isTruthy(process.env.SKILLBOARD_SKIP_POSTINSTALL)) {
 process.stderr.write(`${[
   "SkillBoard installed or updated.",
   "It can refresh user-agent guidance on global installs, but it does not initialize projects.",
-  "Run skillboard init only inside a workspace where you want project-local policy files.",
+  "skillboard init is deprecated project-local policy bootstrap and is not needed for normal use.",
   ""
 ].join("\n")}\n`);
 
@@ -20,7 +20,7 @@ if (!shouldAutoSetup(process.env)) {
     "  skillboard setup",
     "",
     "Setup only writes user agent skill files. It does not create skillboard.config.yaml or .skillboard/.",
-    "Run skillboard init later only for a project that needs local SkillBoard policy.",
+    "skillboard init is deprecated project-local policy bootstrap and is not needed for normal use.",
     ""
   ].join("\n")}`);
   process.exit(0);

package/docs/install.md

@@ -1,4 +1,4 @@
-# Install And Bootstrap
+# Install And Agent-Layer Setup
 
 SkillBoard sits one layer above skill installers, plugin marketplaces, harness
 bundles, and local skill repositories.
@@ -20,8 +20,8 @@ CLI available and the postinstall step runs agent-layer setup for detected
 Codex, Claude, OpenCode, and Hermes user skill roots. The setup is best-effort:
 it never fails the package install, does not edit agent config files, and does
 not create project policy files. It does not run `skillboard init`; run `init`
-only inside a workspace where you want local SkillBoard policy, bridge guidance,
-and reports.
+only when maintaining an existing workspace that intentionally keeps local
+SkillBoard policy, bridge guidance, and reports.
 
 The published CLI supports Node.js 14.21 or newer. Node 12 and older are not
 supported without a transpiled bundle because the source uses modern ESM and
@@ -78,34 +78,16 @@ SkillBoard reports `needs-adaptation`, the agent explains why, asks before
 changing the skill body for the target runtime, then installs the approved
 adapted file with `--adapted-file <path> --yes`.
 
-Use no-prompt npx package execution only when you intentionally want to create
-or inspect local workspace policy files without keeping a global SkillBoard
-binary installed:
+Use no-prompt package execution when you want read-only help without keeping a
+global SkillBoard binary installed:
 
 ```bash
-npx --yes --package agent-skillboard skillboard init
-npx --yes --package agent-skillboard skillboard doctor --summary
-npx --yes --package agent-skillboard skillboard brief --workflow <workflow-from-init>
+npm exec --yes --package agent-skillboard -- skillboard --version
+npm exec --yes --package agent-skillboard -- skillboard help brief
 ```
 
-Local workspace policy files can be stricter than the first agent-layer setup.
-When you intentionally run `init`, it imports trusted local skills as
-manual-only and keeps runtime/plugin skills quarantined until their source is
-reviewed. The brief presents unreviewed runtime sources as one-time review
-decisions rather than default block recommendations; after review, individual
-quarantined skills can be activated as manual-only workflow skills. When `init`
-creates or discovers workflows, use one of the workflow names it prints for the
-first brief. If `init` does not print a workflow, run the unscoped `brief`
-command it prints instead. The explicit package/binary spelling avoids an extra
-npx install prompt and keeps the executable name clear.
-
-The equivalent `npm exec` spelling is also no-prompt and works well in scripts:
-
-```bash
-npm exec --yes --package agent-skillboard -- skillboard init
-npm exec --yes --package agent-skillboard -- skillboard doctor --summary
-npm exec --yes --package agent-skillboard -- skillboard brief --workflow <workflow-from-init>
-```
+The explicit package/binary spelling avoids an extra install prompt and keeps
+the executable name clear.
 
 For repeated local use, install the CLI globally:
 
@@ -119,6 +101,21 @@ skillboard setup --agent codex,claude,opencode,hermes --yes
 The executable remains `skillboard` even though the npm package name is
 `agent-skillboard`.
 
+## Deprecated Project Policy Mode
+
+`skillboard init` is deprecated project-local policy bootstrap and is not
+needed for normal use. Package install, postinstall, and `skillboard setup`
+connect SkillBoard at the agent layer without creating project files.
+
+The command remains available for existing workspaces that intentionally keep
+local `skillboard.config.yaml`, `.skillboard/`, `AGENTS.md`, or `CLAUDE.md`
+policy files. If you maintain one of those workspaces, inspect `skillboard help
+init`, then run `skillboard init` from that workspace or pass `--dir`.
+
+```bash
+npm exec --yes --package agent-skillboard -- skillboard help init
+```
+
 ## Run Unreleased Builds From GitHub
 
 Use GitHub npx only when you intentionally want the current repository state
@@ -127,17 +124,15 @@ before the next npm release:
 AI/automation/operator details:
 
 ```bash
-npx --yes --package github:NyXXiR/skillboard skillboard init
-npx --yes --package github:NyXXiR/skillboard skillboard doctor --summary
-npx --yes --package github:NyXXiR/skillboard skillboard brief --workflow <workflow-from-init>
+npx --yes --package github:NyXXiR/skillboard skillboard --version
+npx --yes --package github:NyXXiR/skillboard skillboard help
 ```
 
 The equivalent `npm exec` spelling is explicit about the package and binary:
 
 ```bash
-npm exec --yes --package github:NyXXiR/skillboard -- skillboard init
-npm exec --yes --package github:NyXXiR/skillboard -- skillboard doctor --summary
-npm exec --yes --package github:NyXXiR/skillboard -- skillboard brief --workflow <workflow-from-init>
+npm exec --yes --package github:NyXXiR/skillboard -- skillboard --version
+npm exec --yes --package github:NyXXiR/skillboard -- skillboard help
 ```
 
 ## Install From A Clone
@@ -150,16 +145,16 @@ AI/automation/operator details:
 git clone https://github.com/NyXXiR/skillboard.git
 cd skillboard
 npm install
-node bin/skillboard.mjs init --dir /path/to/your/project
-node bin/skillboard.mjs doctor --dir /path/to/your/project --summary
-node bin/skillboard.mjs brief --dir /path/to/your/project --workflow <workflow-from-init>
+node bin/skillboard.mjs --version
+node bin/skillboard.mjs help
 ```
 
-## What init Does
+## What Deprecated init Does
 
-`skillboard init` is the optional local policy-file generation step. npm
-installation and `skillboard setup` do not modify a project, but init creates
-local files for teams that intentionally keep workflow policy in a workspace.
+`skillboard init` is the legacy local policy-file generation step. npm
+installation and `skillboard setup` do not modify a project, but init still
+creates local files for teams that intentionally keep workflow policy in an
+existing workspace.
 
 Created project files:
 
@@ -190,8 +185,8 @@ extensions without flattening them into loose skills. After the owning source is
 reviewed, action cards can activate a quarantined runtime skill into a workflow
 as `manual-only`; automatic preference should still be remembered later through
 the normal ask-after-use policy loop. Use `--no-scan-installed` for a
-scaffold-only bootstrap, or `--scan-root <dir>[,<dir>]` to add server-specific
-skill roots during bootstrap.
+scaffold-only initialization, or `--scan-root <dir>[,<dir>]` to add
+server-specific skill roots during initialization.
 
 After init, run:
 

package/docs/reference.md

@@ -3,7 +3,7 @@
 This is the operator reference for users who already understand the basic
 SkillBoard flow and need exact command, config, and lifecycle details.
 
-For installation and bootstrap commands, start with [install.md](install.md).
+For installation and agent-layer setup commands, start with [install.md](install.md).
 For a guided first workflow, use [user-flow.md](user-flow.md).
 
 ## Command Forms
@@ -16,12 +16,8 @@ The npm package is `agent-skillboard`; the executable remains `skillboard`.
 For CI or scripts, the explicit package form avoids binary-name ambiguity:
 
 ```bash
-npx --yes --package agent-skillboard skillboard init
-npx --yes --package agent-skillboard skillboard doctor --summary
-npx --yes --package agent-skillboard skillboard brief --workflow <workflow-from-init>
-npm exec --yes --package agent-skillboard -- skillboard init
-npm exec --yes --package agent-skillboard -- skillboard doctor --summary
-npm exec --yes --package agent-skillboard -- skillboard brief --workflow <workflow-from-init>
+npm exec --yes --package agent-skillboard -- skillboard --version
+npm exec --yes --package agent-skillboard -- skillboard help brief
 ```
 
 After a global install, postinstall auto-runs agent-layer setup for detected
@@ -31,16 +27,12 @@ guidance. This is agent-layer integration; it does not initialize, attach, or
 manage individual projects. To remove only managed agent-layer guidance, run
 `skillboard uninstall --agent-layer` before package removal.
 
-If `init` does not print a workflow, run the unscoped `brief` command it prints
-instead.
-
 Unreleased GitHub builds are available when intentionally testing repository
 state before the next npm release:
 
 ```bash
-npx --yes --package github:NyXXiR/skillboard skillboard init
-npx --yes --package github:NyXXiR/skillboard skillboard doctor --summary
-npx --yes --package github:NyXXiR/skillboard skillboard brief --workflow <workflow-from-init>
+npx --yes --package github:NyXXiR/skillboard skillboard --version
+npx --yes --package github:NyXXiR/skillboard skillboard help
 ```
 
 From a source clone:
@@ -50,9 +42,8 @@ git clone https://github.com/NyXXiR/skillboard.git
 cd skillboard
 npm install
 npm test
-node bin/skillboard.mjs init --dir /path/to/your/project
-node bin/skillboard.mjs doctor --dir /path/to/your/project --summary
-node bin/skillboard.mjs brief --dir /path/to/your/project --workflow <workflow-from-init>
+node bin/skillboard.mjs --version
+node bin/skillboard.mjs help
 ```
 
 ## Commands
@@ -60,7 +51,6 @@ node bin/skillboard.mjs brief --dir /path/to/your/project --workflow <workflow-f
 ```bash
 skillboard setup [--yes] [--agent codex[,claude,opencode,hermes]]
 skillboard import-skill --from <agent> --to <agent> --skill <id-or-dir> [--target-skill <id-or-dir>] [--adapted-file <path>] [--dry-run] [--yes] [--replace] [--json]
-skillboard init [--dir <path>] [--scan-root <dir>[,<dir>]] [--no-scan-installed]
 skillboard uninstall [--dir <path>] [--dry-run] [--keep-settings] [--purge] [--remove-config|--reset-config] [--remove-reports] [--remove-hooks] [--keep-empty-dirs] [--agent-layer] [--agent codex[,claude,opencode,hermes]]
 skillboard inventory refresh [--dir <path>] [--config <path>] [--scan-root <dir>[,<dir>]] [--dry-run] [--json]
 skillboard inventory detect --unit <id> --config <path> [--install-output <path>] [--config-file a,b] [--source <value>] [--kind <kind>] [--scope <scope>] [--dry-run] [--json]
@@ -136,6 +126,24 @@ This is separate from `variant` commands. `import-skill` installs a target-agent
 user skill file; `variant` records project-local policy relationships,
 snapshots, and workflow preferences.
 
+## Deprecated Project Policy Mode
+
+`skillboard init` is deprecated project-local policy bootstrap and is not
+needed for normal use. Package install, postinstall, and `skillboard setup`
+connect SkillBoard at the agent layer without initializing, attaching, or
+managing individual projects.
+
+```bash
+skillboard init [--dir <path>] [--scan-root <dir>[,<dir>]] [--no-scan-installed]
+skillboard help init
+```
+
+The command remains available for existing workspaces that intentionally keep
+local `skillboard.config.yaml`, `.skillboard/`, `AGENTS.md`, or `CLAUDE.md`
+policy files. If `init` creates or discovers workflows, use one of the workflow
+names it prints for the first `brief`. If it does not print a workflow, run the
+unscoped `brief` command it prints instead.
+
 ## Capability Routing
 
 For the normal AI-mediated flow, prefer `brief --intent`: it returns the current
@@ -396,7 +404,8 @@ for the full lifecycle guide.
 
 ## Related Runbooks
 
-- [install.md](install.md): install, init, doctor, bridge, refresh, and uninstall.
+- [install.md](install.md): install, agent-layer setup, legacy policy mode,
+  doctor, refresh, and uninstall.
 - [user-flow.md](user-flow.md): first-time skill governance workflow.
 - [policy-model.md](policy-model.md): policy states, invocation modes, and install units.
 - [capabilities.md](capabilities.md): capability catalog and workflow resolution.

package/docs/user-flow.md

@@ -38,29 +38,21 @@ SkillBoard non-blocking: observe the request, route to the current best skill,
 work normally, explain briefly, ask after use only when a policy preference would
 help, and remember that usage policy without rewriting skill bodies.
 
-## 1. Bootstrap The Control Plane
+## 1. Start From Agent-Layer Setup
 
 AI/automation/operator details:
 
 ```bash
-skillboard init
-skillboard doctor
+skillboard setup --agent codex,claude,opencode,hermes --yes
 ```
 
-`init` creates the config, local `skills/` directory, report directories, and
-agent bridge blocks. It also scans known local agent skill locations and records
-discovered skills as managed entries. Trusted user-local skills, including
-Hermes profile skills under `.hermes/profiles/*/skills`, are immediately
-attached to a generated manual workflow as `status: active` with
-`invocation: manual-only` when the project has no workflows yet, so existing
-manual skills keep working through `can-use` and guard checks without creating
-legacy-state warning noise. Runtime-supplied or external skills are quarantined
-until an explicit source and workflow decision exists. Reviewable items should
-appear as "Needs your decision"; only provenance failures, explicit user blocks,
-disabled sources, or other hard policy failures should remain "Blocked for
-safety". Use
-`skillboard doctor --strict` when review-needed safe-mode warnings should fail
-automation.
+Package install and `skillboard setup` write user-agent guidance only. They do
+not create `skillboard.config.yaml`, `.skillboard/`, `AGENTS.md`, or
+`CLAUDE.md` in projects. `skillboard init` is deprecated project-local policy
+bootstrap and is not needed for normal use; use it only when maintaining an
+existing workspace that intentionally keeps local SkillBoard policy files. Use
+`skillboard doctor --strict` only for an existing policy workspace when
+review-needed safe-mode warnings should fail automation.
 
 When the user asks the agent what it can use, the agent should read the current
 brief with `skillboard brief --json` first and answer from the brief rather than

package/docs/versioning.md

@@ -8,7 +8,7 @@ source profiles, and the generated lockfile.
 
 ## Status
 
-Current package version: `0.2.7`
+Current package version: `0.2.18`
 
 Current config schema version:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-skillboard",
-  "version": "0.2.16",
+  "version": "0.2.18",
   "description": "Keep agent skills broadly available while routing overlaps consistently.",
   "keywords": [
     "ai-agent",

package/src/agent-integration-cli.mjs

@@ -35,7 +35,7 @@ export async function runSetupCommand(options, stdout, runtime = defaultRuntime(
   writeList(stdout, "Preserved", result.preserved);
   stdout.write("Next:\n");
   stdout.write("- Restart or refresh agents that cache user skills.\n");
-  stdout.write("- No project was initialized; run skillboard init only inside a workspace that needs local SkillBoard policy.\n");
+  stdout.write("- No project was initialized; skillboard init is deprecated project-local policy bootstrap and is not needed for normal use.\n");
   stdout.write('- Ask the agent in a workspace: "Review this plan and point out weak assumptions."\n');
   stdout.write("- SkillBoard will step in when skills overlap, routing is ambiguous, or you ask for a skill decision.\n");
   return 0;
@@ -76,7 +76,7 @@ function writeList(stdout, label, values) {
 function writeSetupConfirmation(stdout, targets, command) {
   stdout.write("SkillBoard setup installs agent-layer integration, not project files.\n");
   stdout.write("It writes a SkillBoard guidance skill into detected user agent skill roots so agents can resolve skill priority when choices overlap.\n");
-  stdout.write("It does not create skillboard.config.yaml or .skillboard/; run skillboard init later only for a project that needs local policy.\n");
+  stdout.write("It does not create skillboard.config.yaml or .skillboard/; skillboard init is deprecated project-local policy bootstrap and is not needed for normal use.\n");
   stdout.write("Targets:\n");
   for (const target of targets) {
     stdout.write(`- ${target.agent}: ${target.skillPath}\n`);

package/src/agent-integration-content.mjs

@@ -16,7 +16,7 @@ Use this skill to let SkillBoard guide skill selection above individual projects
 - SkillBoard is the user-level control plane for skill priority, overlap resolution, and workflow-aware routing.
 - Project management belongs to the agent or workspace layer. Do not initialize, attach, rewrite, or manage a project just because SkillBoard is installed.
 - Package install and \`skillboard setup\` install user-agent guidance only.
-- \`skillboard init\` is a separate project command. Use it only when the user wants project-local policy files such as \`skillboard.config.yaml\`, \`.skillboard/\`, \`AGENTS.md\`, or \`CLAUDE.md\`.
+- \`skillboard init\` is deprecated project-local policy bootstrap. It is not needed for normal use; use it only when maintaining an existing workspace that intentionally keeps local policy files such as \`skillboard.config.yaml\`, \`.skillboard/\`, \`AGENTS.md\`, or \`CLAUDE.md\`.
 
 ## Default Behavior