scribe

First-run bootstrap (do this before anything else)

Before running any command in this skill, check that scribe is installed and that this skill is registered locally. If either is missing, bootstrap them now.

Step 1 — check for the binary:

scribe --version

If the command succeeds, skip to Step 3. If it fails with "command not found" (or similar), run Step 2.

Step 2 — install scribe. Prefer install methods that land the binary on PATH so future sessions can call scribe directly. Pick the first option that fits the machine; stop on the first success:

# macOS Homebrew (preferred on macOS — installs to a PATH directory)
brew install Naoray/tap/scribe

# macOS Apple Silicon binary (installs to /usr/local/bin)
curl -L https://github.com/Naoray/scribe/releases/latest/download/scribe_darwin_arm64.tar.gz | tar xz && sudo mv scribe /usr/local/bin/

# macOS Intel binary
curl -L https://github.com/Naoray/scribe/releases/latest/download/scribe_darwin_amd64.tar.gz | tar xz && sudo mv scribe /usr/local/bin/

# Linux amd64 binary
curl -L https://github.com/Naoray/scribe/releases/latest/download/scribe_linux_amd64.tar.gz | tar xz && sudo mv scribe /usr/local/bin/

# Linux arm64 binary
curl -L https://github.com/Naoray/scribe/releases/latest/download/scribe_linux_arm64.tar.gz | tar xz && sudo mv scribe /usr/local/bin/

# Go toolchain — LAST RESORT: installs to $(go env GOBIN) or ~/go/bin, which is
# often not on PATH. Only use if none of the above work.
go install github.com/Naoray/scribe/cmd/scribe@latest

Windows (PowerShell): Run this instead — downloads to $env:USERPROFILE\bin and adds it to your user PATH (use scribe_windows_arm64.zip on ARM64 machines):

powershell -Command "
  \$dest = \"\$env:USERPROFILE\bin\";
  New-Item -ItemType Directory -Force -Path \$dest | Out-Null;
  Invoke-WebRequest -Uri 'https://github.com/Naoray/scribe/releases/latest/download/scribe_windows_amd64.zip' -OutFile \"\$env:TEMP\scribe.zip\";
  Expand-Archive -Path \"\$env:TEMP\scribe.zip\" -DestinationPath \$dest -Force;
  \$current = [Environment]::GetEnvironmentVariable('PATH','User');
  if (\$current -notlike \"*\$dest*\") {
    [Environment]::SetEnvironmentVariable('PATH', \"\$dest;\$current\", 'User')
  }
"

After running, open a new terminal for PATH to take effect.

After install, verify scribe is reachable via PATH:

command -v scribe && scribe --version

If command -v scribe prints nothing but the binary exists (e.g. at ~/go/bin/scribe or $(go env GOBIN)/scribe), the install directory is not on PATH. Fix it before continuing:

1. Detect the install dir: GOBIN=$(go env GOBIN); [ -z "$GOBIN" ] && GOBIN="$(go env GOPATH)/bin"; echo "$GOBIN"
2. Append to the user's shell rc (~/.zshrc for zsh, ~/.bashrc for bash): export PATH="$GOBIN:$PATH"
3. Tell the user the line you added and which file, and that they need to open a new shell (or source the file) for it to take effect.
4. For the rest of this bootstrap, call scribe by absolute path ("$GOBIN"/scribe ...).

If all install options fail, stop and tell the user which one errored and why.

Step 3 — make sure this skill is registered locally so it survives future sessions:

scribe list --json

If the output already contains an entry with "name": "scribe", you're done — continue with the user's actual request.

If it does not, install this skill now. First trigger first-run so the Naoray/scribe built-in registry is wired up, then install:

scribe status --json
scribe add Naoray/scribe:scribe --no-interaction --json
scribe list --json

Confirm the final scribe list --json includes scribe. If anything in this bootstrap fails, report the failing command and its stderr verbatim — do not guess around it.

Once bootstrap succeeds, proceed with the user's request using the command reference below.

What scribe does

Scribe manages local coding-agent skills. It stores canonical copies in ~/.scribe/skills/ and links them into supported tool directories. Use it for installs, updates, removal, adoption of unmanaged local skills, and structured inspection.

Trigger phrases to commands

Non-negotiable rules

1. Always use --json for anything you plan to parse.
2. Prefer scribe browse --query ... --json for discovery and scribe browse --install ... --no-interaction --json for exact-name installs.
3. Prefer owner/repo:skill for deterministic installs via scribe add.
4. Use --no-interaction for direct installs and removals.
5. Use scribe adopt --dry-run --json before scribe adopt --no-interaction --json.
6. Do not hand-edit ~/.scribe/state.json.
7. Do not copy skill files directly into tool directories; use scribe adopt.
8. scribe sync reconciles the project loadout; it does not install an arbitrary new skill by query.
9. scribe list is local-first. Use scribe browse for registry discovery.
10. Some failures still return plain stderr plus non-zero exit, not a JSON error envelope.

JSON envelope (format_version=1)

Migrated commands wrap their output in a versioned envelope. Read payload from data, never from the top level:

{ "status": "ok", "format_version": "1", "data": { /* payload */ },
  "meta": { "duration_ms": 12, "command": "scribe sync", "scribe_version": "..." } }

status is "ok" on success, "partial_success" when data.summary.failed > 0 (exit code 10), or "error" (with non-zero exit). Use jq '.data.foo', not jq '.foo'.

Run scribe schema <command> --json before composing an unfamiliar call — returns JSON Schema 2020-12 for inputs and outputs.

Exit codes

0 ok · 2 usage · 3 not-found · 4 permission · 5 conflict · 6 network · 7 dependency · 8 validation · 9 user-canceled · 10 partial success.

Project file (.scribe.yaml)

If a project root has .scribe.yaml, it declares per-project intent — kits, snippets, mcp, mcp_servers, add, remove. Kits are first-class local skill bundles, and scribe kit create can scaffold them. Don't synthesize a project file without being asked.

Authoring kits and snippets

Use scribe kit create for new kits. Snippet creation has no CLI yet; when the user asks to create, edit, or remove a snippet, edit the Markdown file directly. Run scribe sync afterwards to apply.

Kit — bundle of skills, declared in ~/.scribe/kits/<name>.yaml

apiVersion: scribe/v1
kind: Kit
name: laravel-baseline
description: Default skill set for Laravel app work
skills:
  - init-laravel
  - tdd
  - code-review
mcp_servers:
  - mempalace

Required: name, skills. description, mcp_servers, apiVersion, kind, and source are optional.

Each entry under skills: is a skill name from scribe list --json. Verify the skills exist before writing the kit; a kit referencing an unknown skill will fail at sync time.

Prefer the CLI when creating a kit:

scribe kit create laravel-baseline --skills init-laravel,tdd,code-review --mcp-servers mempalace --description "Default skill set for Laravel app work"

Snippet — agent rules block, declared in ~/.scribe/snippets/<name>.md

---
name: commit-discipline
description: Commit-message rules and agent commit discipline
targets: [claude, codex, cursor]
---

Commit after each logical phase of work, not just at the end.
Use `[agent]` prefix on every commit message...

Required frontmatter: name, description, targets. targets is a YAML list of agent tool names — built-ins are claude, codex, cursor, gemini; any custom tool registered via scribe tools add works here too. Body is plain markdown — no variables, no conditionals.

Wiring a kit/snippet into a project

Edit <project-root>/.scribe.yaml to declare the project's intent:

kits:
  - laravel-baseline
snippets:
  - commit-discipline
mcp:
  - mempalace
add:
  - owner/repo:extra-skill
remove:
  - skill-this-project-doesnt-want

All keys are optional. Empty / missing file = no project intent. mcp and mcp_servers both declare project-local MCP server names; server definitions must already exist in .mcp.json.

After authoring, apply

scribe sync --json

Sync resolves declared kits, merges add / remove, projects skills into the project's .claude/skills/ and .agents/skills/ dirs (Codex reads .agents/skills/), scopes selected .mcp.json definitions into Claude, Codex, and Cursor project config, and writes snippet blocks into CLAUDE.md / AGENTS.md / GEMINI.md plus Cursor rules in .cursor/rules/<name>.mdc (markers preserved; content outside markers untouched). Scribe does not start MCP server processes.

If .scribe.yaml changes, or generated agent files no longer match it, run scribe sync --json before assuming the active agent loadout is current.

Codex budget

Codex caps total skill descriptions at 5440 bytes. Sync refuses at 100% (exit 5) and warns at 70%-100%. If a kit overflows, trim it or pass --force to the sync.

Anti-patterns

• Don't write .scribe.yaml without being asked. The project owner decides which kits/snippets the team adopts.
• Don't reference skills that aren't installed locally. Run scribe list --json first.
• Don't edit projected skill files under .claude/skills/<name>/ — they're symlinks. Edit the source skill or use scribe push (v1.0+) to push back to a registry.

JSON shapes

scribe list --json

Top level: array. Each item may include name, description, package, revision, content_hash, targets, managed, origin, and path. Fresh-home output is [].

scribe browse --json

Top level: object with registries. Each registry has registry and skills. Each remote skill may include name, status, version, loadout_ref, maintainer, and agents. Add --query <q> to filter, or --install <name> --no-interaction to install an exact match.

scribe add query --json

Top level: object with results. Each result may include name, registry, status, version, description, and author. This is search output, not install output.

scribe add owner/repo:skill --no-interaction --json

Top level: object with installed. Each installed item may include name, registry, status, and error. Observed statuses: installed, updated, already-installed, error.

scribe sync --json

Top level: object with registries and summary. Each registry has registry and skills. Each skill result may include name, action, status, version, and error. summary has installed, updated, skipped, and failed. Observed actions: installed, updated, skipped, error, package_installed, package_updated, denied. An optional top-level adoption object may appear.

scribe adopt --dry-run --json

Top level: object with dry_run, adopt, and conflicts. adopt entries may include name, local_path, targets, and hash. conflicts entries may include name, managed_hash, unmanaged_path, and unmanaged_hash.

scribe adopt --no-interaction --json

Top level: formatter envelope with registries, summary, and adoption. adoption may include skills, conflicts_deferred, adopted, failed, and skipped.

scribe remove skill --no-interaction --json

Top level: object with removed. Optional fields: managed_by, errors.

scribe explain skill --json

Top level: object with name and content. Optional fields: description, revision, targets, and path. This command only works for installed skills on disk.

scribe status --json

Top level: object with version, registries, and installed_count. Optional field: last_sync.

scribe doctor --json

Top level: object with issues. Optional fields: skill and fix. Each issue may include skill, tool, kind, status, and message.

Recommended flows

Install a known skill:

scribe add owner/repo:skill --no-interaction --json

Search, then install deterministically:

scribe browse --query query --json
scribe browse --install owner/repo:skill --no-interaction --json

Inspect local state:

scribe list --json
scribe status --json

Reconcile connected registries:

scribe sync --json

Audit and repair managed skill health:

scribe doctor --json
scribe doctor --fix
scribe doctor --skill recap --fix

scribe doctor audits managed skills and projection health. scribe doctor --fix applies safe metadata normalization and then repairs affected tool projections. scribe doctor v1 does not attempt to rewrite mixed package layouts for Codex; it focuses on canonical metadata health plus projection repair.

Adopt unmanaged local skills:

scribe adopt --dry-run --json
scribe adopt --no-interaction --json

Anti-patterns

• Bare scribe add in automation.
• Parsing styled terminal output instead of --json.
• Using scribe sync when you mean “install one skill”.
• Removing files by hand from tool directories.
• Editing ~/.scribe/state.json directly.
• Assuming every failure returns JSON.

Fallback rule

If you need a command not listed here, run:

scribe --help
scribe <subcommand> --help

Do not guess flags or JSON fields.