Ceibabelize — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the ceibabelize-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. Resolve in this order:

1. Prefer repo-local binary when available:

   • C:\Users\user1\Desktop\Belize-chat\ceibabelize\ceibabelize-pp-cli.exe

2. Else use ceibabelize-pp-cli from $PATH

3. If neither exists, install it:

   npx -y @mvanhorn/printing-press install ceibabelize --cli-only

If install lookup fails, use the repo-local binary path above instead of blocking.

Verify:

ceibabelize-pp-cli --version

Ensure $GOPATH/bin (or $HOME/go/bin) is on $PATH when using global installs.

If the npx install fails before this CLI has a public-library category, install Node or use the category-specific Go fallback after publish.

If --version reports "command not found" after install, the install step did not put the binary on $PATH. Do not proceed with skill commands until verification succeeds.

WordPress REST API for Ceiba Realty & Development — Belize real estate listings,
developments, and property media. The site serves property listings for buyers
and investors in mainland Belize across 6 districts.

When Not to Use This CLI

Do not activate this CLI for requests that require creating, updating, deleting, publishing, commenting, upvoting, inviting, ordering, sending messages, booking, purchasing, or changing remote state. This printed CLI exposes read-only commands for inspection, export, sync, and analysis.

Command Reference

Key flags worth knowing: --specs (scrapes HTML for price/beds/acres), --embed (embed images/terms), --search, --district, --featured-tags (31=Spotlight, 30=Sold), --list-category, --orderby, --download-dir, --size, --parent, --since, --resources, --follow, --interval, --limit, --type, --format, --output.

• featured-listing get-property <id> [--specs] [--embed] — Get listing details; --specs scrapes HTML for price/acre/beds/baths not in API
• featured-listing list-properties [--search] [--district] [--featured-tags] [--list-category] [--orderby] [--all] — List/filter listings
• featured-listing photos <id> [--download-dir] [--size] — List/download listing photos
• development get <id> / development list [--all] / development photos <id> [--download-dir] — Developments
• media get <id> / media list [--parent] — Media attachments
• district [--parent] — List districts/areas
• featured-tags / list-category — Listing status tags & categories
• search <query> [--type] [--limit] — Full-text search across synced data
• sync [--since] [--resources] [--full] [--concurrency] — Sync API to local SQLite
• tail [--resource] [--follow] [--interval] — Poll live changes
• analytics [--type] [--group-by] [--limit] — Query synced data
• export <resource> [--format] [--output] [--limit] — Export to JSONL/JSON
• import <resource> [--input] [--dry-run] — Import from JSONL
• workflow archive [--full] / workflow status — Compound workflows
• doctor [--fail-on] — Check CLI health
• profile save/list/show/delete/use — Named flag sets
• which "<query>" — Find command by capability
• api — Browse all API endpoints
• agent-context — Structured CLI description for agents
• feedback "message" / feedback list — Record local feedback

Finding the right command

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

ceibabelize-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

No authentication required.

Run ceibabelize-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:

  ceibabelize-pp-cli development list --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

• Read-only — do not use this CLI for create, update, delete, publish, comment, upvote, invite, order, send, or other mutating requests

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:

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

Entries are stored locally at ~/.ceibabelize-pp-cli/feedback.jsonl. They are never POSTed unless CEIBABELIZE_FEEDBACK_ENDPOINT is set AND either --send is passed or CEIBABELIZE_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:

Sink	Effect
stdout	Default; write to stdout only
file:<path>	Atomically write output to <path> (tmp + rename)
webhook:<url>	POST the output body to the URL (application/json or application/x-ndjson when --compact)

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.

ceibabelize-pp-cli profile save briefing --json
ceibabelize-pp-cli --profile briefing development list
ceibabelize-pp-cli profile list --json
ceibabelize-pp-cli profile show briefing
ceibabelize-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

Code	Meaning
0	Success
2	Usage error (wrong arguments)
3	Resource not found
5	API error (upstream issue)
7	Rate limited (wait and retry)
10	Config error

Argument Parsing

Parse $ARGUMENTS:

1. Empty, help, or --help → show ceibabelize-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 ceibabelize-pp-mcp -- ceibabelize-pp-mcp

Verify: claude mcp list

Direct Use

1. Resolve CLI path in this order:
   • C:\Users\user1\Desktop\Belize-chat\ceibabelize\ceibabelize-pp-cli.exe
   • which ceibabelize-pp-cli
     If neither exists, offer install (see Prerequisites).
2. Match the user query to the best command from the Unique Capabilities and Command Reference above.
3. Execute with the --agent flag:

   <resolved-cli-path> <command> [subcommand] [args] --agent

4. If ambiguous, drill into subcommand help: <resolved-cli-path> <command> --help.