How do I install the Plane So CLI skill?

Run npx skillmds@latest add johnalbertini14-glitch/plane-so-cli in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Plane So CLI safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Plane So CLI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Plane So CLI free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Plane So CLI?

johnalbertini14-glitch (@johnalbertini14-glitch) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Plane So CLI by johnalbertini14-glitch

Name: Plane So CLI
Rating: 4.2 (5 reviews)
Author: johnalbertini14-glitch

Plane So CLI

Manage Plane.so projects and work items using a zero-dependency Python CLI. List projects, create/update/assign issues, add comments, search workspace. The plane-so-cli binary is bundled in scripts/.

File contents

Plane.so CLI Skill

Interact with Plane.so project management via a clean, auditable Python CLI.

Zero dependencies — uses only Python 3.8+ stdlib. The plane-so-cli executable is bundled in scripts/plane-so-cli and available on PATH after installation.

Setup

Set these environment variables:

export PLANE_API_KEY="your-api-key"
export PLANE_WORKSPACE="your-workspace-slug"

Get your API key: Plane > Profile Settings > Personal Access Tokens

Commands

User & Workspace

plane-so-cli me                        # Show current user
plane-so-cli projects list             # List all active projects
plane-so-cli members                   # List workspace members

Issues (Work Items)

plane-so-cli issues list -p PROJECT_ID
plane-so-cli issues list -p PROJECT_ID --state STATE_ID
plane-so-cli issues list -p PROJECT_ID --priority high
plane-so-cli issues list -p PROJECT_ID --assignee USER_ID
plane-so-cli issues get -p PROJECT_ID ISSUE_ID
plane-so-cli issues create -p PROJECT_ID --name "Fix bug" --priority high
plane-so-cli issues create -p PROJECT_ID --name "Task" --assignee USER_ID
plane-so-cli issues update -p PROJECT_ID ISSUE_ID --state STATE_ID
plane-so-cli issues update -p PROJECT_ID ISSUE_ID --priority medium
plane-so-cli issues assign -p PROJECT_ID ISSUE_ID USER_ID_1 USER_ID_2
plane-so-cli issues delete -p PROJECT_ID ISSUE_ID
plane-so-cli issues search "login bug"
plane-so-cli issues my

Comments, States & Labels

plane-so-cli comments list -p PROJECT_ID -i ISSUE_ID
plane-so-cli comments add -p PROJECT_ID -i ISSUE_ID "Comment text"
plane-so-cli states -p PROJECT_ID
plane-so-cli labels -p PROJECT_ID

Cycles & Modules

plane-so-cli cycles list -p PROJECT_ID
plane-so-cli cycles get -p PROJECT_ID CYCLE_ID
plane-so-cli modules list -p PROJECT_ID
plane-so-cli modules get -p PROJECT_ID MODULE_ID

Output Formats

Default is human-readable table. Use -f json for raw JSON:

plane-so-cli projects list -f json

Typical Workflow

plane-so-cli projects list — find project ID
plane-so-cli members — find member IDs for assignment
plane-so-cli states -p PROJECT_ID — see available states
plane-so-cli issues create -p PROJECT_ID --name "Task" --assignee USER_ID
plane-so-cli comments add -p PROJECT_ID -i ISSUE_ID "Started working"

Security & Privacy

This skill communicates only with the Plane.so API. The API host is hardcoded to api.plane.so and cannot be overridden.

Endpoint	Data sent	Purpose
`https://api.plane.so/api/v1/*`	API key (header), project/issue data (body)	All Plane.so operations

Your PLANE_API_KEY is sent as an X-API-Key header exclusively to https://api.plane.so
The API host is hardcoded — no environment variable can redirect requests to another domain
No data is cached, logged, or stored locally
No telemetry or analytics are collected
The full source code is auditable at github.com/luiseduardoaugusto/plane-so-cli and bundled in scripts/plane-so-cli

---name: plane-so-clidescription: Manage Plane.so projects and work items using a zero-dependency Python CLI. List projects, create/update/assign issues, add comments, search workspace. The plane-so-cli binary is bundled in scripts/.license: MIT--- # Plane.so CLI Skill Interact with [Plane.so](https://plane.so) project management via a clean, auditable Python CLI. **Zero dependencies** — uses only Python 3.8+ stdlib. The `plane-so-cli` executable is bundled in `scripts/plane-so-cli` and available on PATH after installation. ## Setup Set these environment variables: ```bash export PLANE_API_KEY="your-api-key" export PLANE_WORKSPACE="your-workspace-slug" ``` Get your API key: **Plane > Profile Settings > Personal Access Tokens** ## Commands ### User & Workspace ```bash plane-so-cli me # Show current user plane-so-cli projects list # List all active projects plane-so-cli members # List workspace members ``` ### Issues (Work Items) ```bash plane-so-cli issues list -p PROJECT_ID plane-so-cli issues list -p PROJECT_ID --state STATE_ID plane-so-cli issues list -p PROJECT_ID --priority high plane-so-cli issues list -p PROJECT_ID --assignee USER_ID plane-so-cli issues get -p PROJECT_ID ISSUE_ID plane-so-cli issues create -p PROJECT_ID --name "Fix bug" --priority high plane-so-cli issues create -p PROJECT_ID --name "Task" --assignee USER_ID plane-so-cli issues update -p PROJECT_ID ISSUE_ID --state STATE_ID plane-so-cli issues update -p PROJECT_ID ISSUE_ID --priority medium plane-so-cli issues assign -p PROJECT_ID ISSUE_ID USER_ID_1 USER_ID_2 plane-so-cli issues delete -p PROJECT_ID ISSUE_ID plane-so-cli issues search "login bug" plane-so-cli issues my ``` ### Comments, States & Labels ```bash plane-so-cli comments list -p PROJECT_ID -i ISSUE_ID plane-so-cli comments add -p PROJECT_ID -i ISSUE_ID "Comment text" plane-so-cli states -p PROJECT_ID plane-so-cli labels -p PROJECT_ID ``` ### Cycles & Modules ```bash plane-so-cli cycles list -p PROJECT_ID plane-so-cli cycles get -p PROJECT_ID CYCLE_ID plane-so-cli modules list -p PROJECT_ID plane-so-cli modules get -p PROJECT_ID MODULE_ID ``` ## Output Formats Default is human-readable table. Use `-f json` for raw JSON: ```bash plane-so-cli projects list -f json ``` ## Typical Workflow 1. `plane-so-cli projects list` — find project ID 2. `plane-so-cli members` — find member IDs for assignment 3. `plane-so-cli states -p PROJECT_ID` — see available states 4. `plane-so-cli issues create -p PROJECT_ID --name "Task" --assignee USER_ID` 5. `plane-so-cli comments add -p PROJECT_ID -i ISSUE_ID "Started working"` ## Security & Privacy This skill communicates **only** with the Plane.so API. The API host is hardcoded to `api.plane.so` and cannot be overridden. | Endpoint | Data sent | Purpose | |----------|-----------|---------| | `https://api.plane.so/api/v1/*` | API key (header), project/issue data (body) | All Plane.so operations | - Your `PLANE_API_KEY` is sent as an `X-API-Key` header exclusively to `https://api.plane.so` - The API host is hardcoded — no environment variable can redirect requests to another domain - No data is cached, logged, or stored locally - No telemetry or analytics are collected - The full source code is auditable at [github.com/luiseduardoaugusto/plane-so-cli](https://github.com/luiseduardoaugusto/plane-so-cli) and bundled in `scripts/plane-so-cli`

Frequently asked questions