Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
CLI tool for managing Planning Center Services data including plans, teams, songs, and scheduled people via the PCO Services API.
CLI tool for managing Planning Center Services data including plans, teams, songs, and scheduled people via the PCO Services API.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
CLI for the Planning Center Services API. Used for Shadow's church work (FBC Gulfport).
https://github.com/rubysworld/pco-cli
/Users/ruby/Projects/pco-cli/pco.ts
tsx /Users/ruby/Projects/pco-cli/pco.ts <command> Or create an alias: alias pco="tsx /Users/ruby/Projects/pco-cli/pco.ts"
Credentials stored in ~/.config/pco-cli/config.json # Check auth status pco auth status # Setup (interactive) pco auth setup # Logout pco auth logout
All list commands support: --json - Output as JSON (default) --table - Output as table --quiet - Output only IDs --limit <n> - Limit results (default: 25) --offset <n> - Offset results --all - Fetch all pages
pco org get # Get org info
pco service-types list # List all service types pco st list # Alias pco service-types get <id> # Get specific service type
# List plans (service-type required) pco plans list --service-type <id> pco plans list --service-type <id> --filter future pco plans list --service-type <id> --filter past # Get specific plan pco plans get <planId> --service-type <id> pco plans get <planId> --service-type <id> --include items,team_members Filters: future, past, after, before, no_dates
pco items list --service-type <id> --plan <planId> pco items get <itemId> --service-type <id> --plan <planId>
pco scheduled list --service-type <id> --plan <planId>
pco people list pco people list --search "John Doe" pco people get <id>
pco teams list --service-type <id> pco teams get <teamId> --service-type <id>
pco songs list pco songs list --search "Amazing Grace" pco songs get <id> pco songs arrangements <songId>
pco media list pco media get <id>
pco folders list pco folders get <id>
pco series list pco series get <id>
pco tag-groups list pco tag-groups tags <groupId>
pco email-templates list
pco attachment-types list
pco report-templates list
# Direct API access pco api GET /service_types pco api POST /endpoint --data '{"key": "value"}' pco api PATCH /endpoint --file data.json pco api DELETE /endpoint
# 1. Find service type ID pco st list --table # 2. Get future plans pco plans list --service-type <id> --filter future --limit 1 # 3. Get plan details with includes pco plans get <planId> --service-type <id> --include items,team_members
pco scheduled list --service-type <id> --plan <planId> --table
pco songs list --search "Great Are You Lord"
This is for PCO Services only (not People, Giving, etc.) API docs: https://developer.planning.center/docs/#/apps/services Context: Church work only โ don't mix with Buape stuff Updated: 2026-01-08
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.