cr-create

A workflow for reviewing GitBook documentation through its web API, with Slack notifications and reviewer feedback.

In plain words
What is it for?
Use it to update an existing GitBook page, create a new one, request review, retrieve comments, push fixes, and finish the review.
Why use it?
It lets an engineer create and update documentation change requests, collect review comments, revise content, and resolve the request from the coding environment.

Skill for Claude CodeCodex

Part of the gitbook plugin — 6 skills, 1 MCP server shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/gitbookio/gitbook-skills/cr-create
Any agent
npx skills add GitbookIO/gitbook-skills --skill cr-create
Clone the repo
git clone --depth 1 https://github.com/GitbookIO/gitbook-skills

Made for: Claude Code, Codex.

Or install gitbook, the plugin that ships this one along with the rest of its 6 skills, 1 MCP server.

Per session 169 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,915 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00169 $0.06915
Opus 5 $0.00084 $0.03458
Sonnet 5 $0.00034 $0.01383
Haiku 4.5 $0.00017 $0.00692

Measured 3d ago against content hash 6019621ed855, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cr-create scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

description: Drive an end-to-end GitBook docs review flow from Claude Code by calling the GitBook REST API directly with curl (no CLI) — create a change request, push content (update an existing page AND create a new pag
skills/cr-create/SKILL.md · 430 lines

How it starts

The opening of the file, as written. The whole thing — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitBook Review Flow (direct API)

Run a documentation review loop against a GitBook space entirely through the GitBook REST API (https://api.gitbook.com/v1, hit with curl), so an engineer never has to leave Claude Code (plus Slack) to propose docs changes and get them reviewed. This is the authoring-side companion to cr-review (the reviewer side over the same API). Every action here is a plain HTTP call — there is no CLI and no helper script.

The same actions serve three purposes with no separate code paths:

  • CR-creation demo — create a change request and push content (one existing page updated, one new page created).
  • Notify/review demo — request reviewers, drop a Slack link, pull comments, fix, re-push, resolve.
  • Real use — the identical actions against the user's own content.

Because the demo is just a scripted sequence of the real actions, it cannot show something that doesn't actually work. Keep it that way: never fake an output.

Auth and the gbapi helper

Every call is a Bearer-authenticated request to https://api.gitbook.com/v1. The token lives in GITBOOK_TOKEN in the repo-root .env (create one at https://app.gitbook.com/account/developer). Never print the token; never write it to a tracked file. If it's missing, prompt the user for it and write it to .env; don't invent one.

Define this shell helper once per session and use it for every call below. It loads the token from .env, sets the base URL and headers, and — critically for the "never fake output" rule — fails loudly on any non-2xx, printing the API's error body (curl --fail-with-body, curl ≥ 7.76 / stock on current macOS):

set -a; [ -f .env ] && . ./.env; set +a          # load GITBOOK_TOKEN (and SLACK_WEBHOOK_URL)
gbapi() {                                          # gbapi METHOD /path [extra curl args…]
  local method="$1" apipath="$2"; shift 2   # NB: not `path` — in zsh that is tied to $PATH
  curl -sS --fail-with-body -X "$method" \
    "https://api.gitbook.com/v1${apipath}" \
    -H "Authorization: Bearer ${GITBOOK_TOKEN}" \
    -H "Content-Type: application/json" "$@"
}

Read the full file on GitHub · 430 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 430 lines · 169 tokens per session scan A 6019621ed855

Subscribe to this mod's changes

cr-create is a skill published in the GitHub repository GitbookIO/gitbook-skills (9 stars, last pushed 14d ago), licensed MIT. It adds 169 tokens to every session and 6,915 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens