skills/draft-cli/SKILL.md
Manage InnoSage Draft pages and hosted Secret Shares using the @innosage/draft-cli. Use this skill for `draft`, `draft page ...`, `draft secret ...`, and `draft auth ...`. Live page commands use the headless v2 daemon. Do not use this skill when "draft" is only a verb or when the task is a generic local-file writing task unrelated to Draft CLI.
npx skillsauth add innosage-llc/draft-skills draft-cliInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use draft for headless page-domain Draft operations and hosted Secret Share helpers.
draft start-server starts the only supported live-page runtime: headless v2.draft status --json is the readiness check for page commands.READY means the headless daemon is running and page read/write commands can proceed.For page commands such as draft page ls, draft page cat, draft page create,
draft page append, draft page replace, draft page patch, draft page annotate, and
draft page publish:
draft status --json
draft start-server
draft status --json
If the first status is already READY, proceed directly. If it reports DAEMON_OFFLINE, run
draft start-server, then re-check status.
Prefer explicit draft page ... commands:
draft page ls --json
draft page cat <page_id> --json
draft page create "Title" --json
draft page append <page_id> "More content" --json
draft page replace <page_id> --heading "Status" "Updated body" --json
draft page patch <page_id> --json < change.diff
draft page annotate <page_id> --anchor "exact text" --note "Reviewer note" --json
draft page comments <page_id> --json
draft page comment <comment_id> <page_id> --json
draft page publish <page_id> --json
Use draft page cat <id> when you want the page content in plain markdown for human review.
Use draft page cat <id> --format json only when you need raw structured document data for parsing or automation.
Top-level page aliases can still exist during compatibility windows, but agents should use the
draft page ... namespace.
Read-only behavior is the safe fallback. Do not run write/share commands unless the user explicitly asks for the exact action and target.
draft page create, draft page append, draft page replace, draft page patch, draft page annotatedraft page publish, draft secret createBefore returning a public or shareable URL, review the command output and confirm it is the requested artifact.
Secret Share commands are hosted/local-crypto helpers and do not require draft status or
draft start-server.
Configure the API key:
draft auth set-key <secret-share-api-key>
draft auth status --json
Create a Secret Share:
draft secret create --file docs/brief.md --expires 1h --json
Read a Secret Share:
draft secret open '<secret_url_or_id>' --password "$DRAFT_SECRET_PASSWORD" --json
Use --password for password-protected shares. Use DRAFT_SECRET_PASSWORD only when the runtime
already provides it.
DAEMON_OFFLINE: run draft start-server, then draft status --json.PAGE_NOT_FOUND: run draft page ls --json and retry with a valid page ID.PATCH_MISMATCH: reread with draft page cat <page_id>, regenerate the patch, and retry.draft auth set-key, --api-key, or DRAFT_SECRET_SHARE_API_KEY.tools
Retired compatibility alias for the former headless Draft page skill. Use `draft-cli` instead for all new `draft` and `draft page ...` work.
tools
Use the repo-local Draft CLI for development and testing with an isolated development port. Trigger this skill when working on `products/notion-editor/cli`, testing local Draft CLI changes, or avoiding collisions with an installed/global Draft CLI.
tools
Enforce a Human-in-the-Right-Loop (HITRL) lifecycle for remote agents. Use this skill when the user wants structured oversight over an agent task: plan approval before execution, evidence-logged execution, and result sign-off before closure. Trigger phrases: "work on this with my oversight", "check with me before you start", "use HITRL for this", "I want to review your plan first", "use draft-agent-loop". DO NOT use for tasks where the user simply asks to do something without requesting approval gates. Use draft-cli for raw Draft commands. This skill depends on the canonical draft-cli skill. It assumes headless page workflows, which fit remote OpenClaw-style isolated environments.
tools
Run the local-first authoring plus Draft review handoff loop for workspace markdown files. Use this skill when the user asks to write or revise a document and explicitly wants human review in Draft, or when the task is to apply Draft comments back to a local file. DO NOT use this skill for pure Draft command questions (use draft-cli) or generic writing tasks with no Draft review intent. Keep local workspace markdown as source of truth and use Draft GUI as the human review surface. Requires the draft-cli skill and @innosage/draft-cli (Node.js >= 18).