← Back to Skills Marketplace
PCO CLI - Planning Center Services
by
rubyrunsstuff
· GitHub ↗
· v1.0.0
1777
Downloads
1
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install pco
Description
CLI tool for managing Planning Center Services data including plans, teams, songs, and scheduled people via the PCO Services API.
Usage Guidance
This skill is an instruction-only doc for running a local PCO CLI — it does not provide the CLI or an install method. Before installing or enabling it: (1) confirm you (or the agent environment) actually have the referenced repository and tsx available at the specified path; (2) locate ~/.config/pco-cli/config.json and verify what credentials it contains — the agent's following these instructions could read that file; (3) prefer a skill that declares required credentials (or includes an install) so you know what is needed and what will be accessed; (4) if you don't have the repo or don't want an agent to access local credential files, do not enable this skill. If you want this functionality, ask the skill author to include an install spec, document required env vars, or avoid hard-coded local paths.
Capability Analysis
Type: OpenClaw Skill
Name: pco
Version: 1.0.0
The skill bundle provides a CLI for the Planning Center Services API, running a local TypeScript script (`pco.ts`) using `tsx`. The `SKILL.md` documentation outlines standard API interactions, including authentication setup and a 'Raw API' command for direct API access. There is no evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection attempts against the agent. All instructions are aligned with the stated purpose of interacting with the Planning Center API.
Capability Assessment
Purpose & Capability
The SKILL.md documents a PCO CLI (commands, auth flow, repo URL) which is coherent with the name, but the skill bundle contains no code or install spec. It assumes a local repository path (/Users/ruby/Projects/pco-cli/pco.ts) and that 'tsx' is available. A user installing this skill would not get a runnable CLI from the skill itself — the skill only documents how to run a locally present tool. That mismatch (claims to provide CLI usage but doesn't include or install the tool) is a coherence problem.
Instruction Scope
Instructions explicitly reference absolute local paths and a local config file (~/.config/pco-cli/config.json) and show commands (pco auth status, pco auth setup) that will read or write local credential files. The SKILL.md therefore instructs actions that touch user-local files and credentials, but the skill metadata does not declare those files or any required credentials. This could cause an agent to access secrets on disk if it follows these instructions.
Install Mechanism
There is no install specification (instruction-only). That is low-risk from an automatic-install perspective, but it also explains why the SKILL.md points at an external local repo rather than providing an install — which is a usability/coherence issue rather than an installation risk.
Credentials
The skill declares no required environment variables or primary credential, yet the instructions refer to credentials stored in ~/.config/pco-cli/config.json and an interactive 'pco auth setup' flow. Requesting no declared credentials while instructing access to a local credential store is proportionally odd and should be clarified: a legitimate PCO CLI needs API credentials (Planning Center access token/secret), but the skill does not state where they come from or whether the agent should access them.
Persistence & Privilege
The skill does not request always: true and has no install actions that would persist or modify other skills or system-wide settings. There is no evidence it demands elevated persistence or cross-skill configuration changes.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install pco - After installation, invoke the skill by name or use
/pco - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of pco CLI for Planning Center Services:
- Provides command-line access to Planning Center Services API.
- Supports authentication, multiple resource commands (plans, service types, items, teams, people, songs, media, and more).
- Global options for output formatting (JSON, table, quiet), pagination, and result limits.
- Includes direct raw API access and common workflows for church service planning.
- Designed for use with FBC Gulfport’s church operations.
Metadata
Frequently Asked Questions
What is PCO CLI - Planning Center Services?
CLI tool for managing Planning Center Services data including plans, teams, songs, and scheduled people via the PCO Services API. It is an AI Agent Skill for Claude Code / OpenClaw, with 1777 downloads so far.
How do I install PCO CLI - Planning Center Services?
Run "/install pco" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is PCO CLI - Planning Center Services free?
Yes, PCO CLI - Planning Center Services is completely free (open-source). You can download, install and use it at no cost.
Which platforms does PCO CLI - Planning Center Services support?
PCO CLI - Planning Center Services is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created PCO CLI - Planning Center Services?
It is built and maintained by rubyrunsstuff (@rubyrunsstuff); the current version is v1.0.0.
More Skills