Pp Cf Domain

Cf Domain — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the cf-domain-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install cf-domain --cli-only
   

2. Verify: cf-domain-pp-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer):

go install github.com/mvanhorn/printing-press-library/library/cloud/cf-domain/cmd/cf-domain-pp-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

Command Reference

registrar — Manage registrar

• cf-domain-pp-cli registrar domain-check — Real-time domain availability and pricing check. Must be run immediately before registration.
• cf-domain-pp-cli registrar domain-register — Register a domain through Cloudflare Registrar using account default registrant/payment settings. Dangerous: caller...
• cf-domain-pp-cli registrar domain-search — Search Cloudflare Registrar for domain suggestions and availability hints. Use domain-check for live final pricing...

Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

cf-domain-pp-cli which "<capability in your own words>"

which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.

Auth Setup

Run cf-domain-pp-cli auth setup for the URL and steps to obtain a token (add --launch to open the URL). Then store it:

cf-domain-pp-cli auth set-token YOUR_TOKEN_HERE

Or set CLOUDFLARE_REGISTRAR_DOMAINS_BEARER_AUTH as an environment variable.

Run cf-domain-pp-cli doctor to verify setup.

Agent Mode

Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.

• Pipeable — JSON on stdout, errors on stderr

• Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:

  cf-domain-pp-cli registrar domain-check mock-value --domain-name example-resource --agent --select id,name,status
  

• Previewable — --dry-run shows the request without sending

• Offline-friendly — sync/search commands can use the local SQLite store when available

• Non-interactive — never prompts, every input is a flag

• Explicit retries — use --idempotent only when an already-existing create should count as success

Response envelope

Commands that read from the local store or the API wrap output in a provenance envelope:

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal — piped/agent consumers get pure JSON on stdout.

Agent Feedback

When you (or the agent) notice something off about this CLI, record it:

cf-domain-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
cf-domain-pp-cli feedback --stdin < notes.txt
cf-domain-pp-cli feedback list --json --limit 10

Entries are stored locally at ~/.cf-domain-pp-cli/feedback.jsonl. They are never POSTed unless CF_DOMAIN_FEEDBACK_ENDPOINT is set AND either --send is passed or CF_DOMAIN_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.

Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.

Output Delivery

Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:

Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.

Named Profiles

A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.

cf-domain-pp-cli profile save briefing --json
cf-domain-pp-cli --profile briefing registrar domain-check mock-value --domain-name example-resource
cf-domain-pp-cli profile list --json
cf-domain-pp-cli profile show briefing
cf-domain-pp-cli profile delete briefing --yes

Explicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.

Exit Codes

Argument Parsing

Parse $ARGUMENTS:

1. Empty, help, or --help → show cf-domain-pp-cli --help output
2. Starts with install → ends with mcp → MCP installation; otherwise → see Prerequisites above
3. Anything else → Direct Use (execute as CLI command with --agent)

MCP Server Installation

Install the MCP binary from this CLI's published public-library entry or pre-built release, then register it:

claude mcp add cf-domain-pp-mcp -- cf-domain-pp-mcp

Verify: claude mcp list

Direct Use

1. Check if installed: which cf-domain-pp-cli If not found, offer to install (see Prerequisites at the top of this skill).
2. Match the user query to the best command from the Unique Capabilities and Command Reference above.
3. Execute with the --agent flag:

   cf-domain-pp-cli <command> [subcommand] [args] --agent
   

4. If ambiguous, drill into subcommand help: cf-domain-pp-cli <command> --help.