Pp Calendly

Calendly — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the calendly-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 calendly --cli-only
   

2. Verify: calendly-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). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:

go install github.com/mvanhorn/printing-press-library/library/productivity/calendly/cmd/calendly-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.

Read-first Calendly API surface for scheduling, availability, event, invitee, and webhook inspection.

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

event-type-available-times — Manage event type available times

• calendly-pp-cli event-type-available-times — List available times for an event type.

event-type-memberships — Manage event type memberships

• calendly-pp-cli event-type-memberships — List event type memberships.

event-types — Manage event types

• calendly-pp-cli event-types get — Get an event type by UUID.
• calendly-pp-cli event-types list — List Calendly event types.

organization-memberships — Manage organization memberships

• calendly-pp-cli organization-memberships get — Get an organization membership by UUID.
• calendly-pp-cli organization-memberships list — List organization memberships.

organizations — Manage organizations

• calendly-pp-cli organizations <uuid> — Get a Calendly organization by UUID.

routing-forms — Manage routing forms

• calendly-pp-cli routing-forms get — Get a routing form by UUID.
• calendly-pp-cli routing-forms list — List routing forms.

scheduled-events — Manage scheduled events

• calendly-pp-cli scheduled-events get — Get a scheduled event by UUID.
• calendly-pp-cli scheduled-events list — List scheduled events.

user-busy-times — Manage user busy times

• calendly-pp-cli user-busy-times — List busy times for a user.

users — Manage users

• calendly-pp-cli users get — Get a Calendly user by UUID.
• calendly-pp-cli users get-current — Get the authenticated Calendly user.

webhook-subscriptions — Manage webhook subscriptions

• calendly-pp-cli webhook-subscriptions get — Get a webhook subscription by UUID.
• calendly-pp-cli webhook-subscriptions list — List webhook subscriptions.

Finding the right command

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

calendly-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 calendly-pp-cli auth setup for the URL and steps to obtain a token (add --launch to open the URL). Then store it:

calendly-pp-cli auth set-token YOUR_TOKEN_HERE

Or set CALENDLY_BEARER_AUTH as an environment variable.

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

  calendly-pp-cli event-type-available-times --event-type example-value --start-time 2026-01-15T09:00:00Z --end-time 2026-01-15T09:00:00Z --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 AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.

Agent Feedback

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

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

Entries are stored locally at ~/.local/share/github.com/mvanhorn/printing-press-library/library/productivity/calendly/feedback.jsonl. They are never POSTed unless CALENDLY_FEEDBACK_ENDPOINT is set AND either --send is passed or CALENDLY_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.

calendly-pp-cli profile save briefing --json
calendly-pp-cli --profile briefing event-type-available-times --event-type example-value --start-time 2026-01-15T09:00:00Z --end-time 2026-01-15T09:00:00Z
calendly-pp-cli profile list --json
calendly-pp-cli profile show briefing
calendly-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 calendly-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

1. Install the MCP server:

   go install github.com/mvanhorn/printing-press-library/library/productivity/calendly/cmd/calendly-pp-mcp@latest
   

2. Register with Claude Code:

   claude mcp add calendly-pp-mcp -- calendly-pp-mcp
   

3. Verify: claude mcp list

Direct Use

1. Check if installed: which calendly-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:

   calendly-pp-cli <command> [subcommand] [args] --agent
   

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