Plane.so

Manage Plane.so projects and work items using the `plane` CLI. List projects, create/update/search issues, manage cycles and modules, add comments, and assign members.

Security Scan

The skill's stated purpose (manage Plane.so via a CLI) matches the instructions, but inconsistencies in the registry metadata and an instruction to download/execute a raw script raise caution before installing.

Purpose & Capability

The skill is described as a Plane.so CLI integrator and the SKILL.md requests the plane CLI plus PLANE_API_KEY and PLANE_WORKSPACE — these are appropriate and expected for the stated purpose. However, the registry-level metadata (provided with the skill) lists no required binaries or env vars while the SKILL.md metadata declares both — this inconsistency is unexplained and could be a packaging error.

Instruction Scope

Runtime instructions are limited to installing the plane CLI, setting PLANE_API_KEY and PLANE_WORKSPACE, and running plane commands (listing projects/issues, creating/updating issues, comments, cycles, etc.). The SKILL.md does not instruct reading unrelated files, harvesting other environment variables, or sending data to unexpected external endpoints.

Install Mechanism

The SKILL.md (and its embedded metadata) instructs downloading a script from raw.githubusercontent.com and placing it in ~/.local/bin which will be executed. Downloading and executing arbitrary scripts from a GitHub user repository is common but carries risk — the script can contain arbitrary code. The host (raw.githubusercontent.com) is a normal release host, but you should inspect the script and prefer an official published release if available.

Credentials

The only required env vars in the SKILL.md are PLANE_API_KEY and PLANE_WORKSPACE, which are proportional to the functionality. However the registry metadata (earlier in the bundle) lists no required env vars — that mismatch between declared requirements and the SKILL.md should be resolved by the publisher.

Persistence & Privilege

The skill does not request always: true and does not claim system-wide privileges. Installation writes a CLI into the user's ~/.local/bin (user-level) which is normal for CLI tools. Autonomous invocation of the skill by the agent is allowed (platform default) but not an additional privilege in this bundle.

What to consider before installing

This skill appears to do what it says (manage Plane.so via the plane CLI), but take these precautions before installing: 1) Confirm the publisher/repo (https://github.com/JinkoLLC/plane-skill) is trustworthy and review the script at the raw URL — downloading and executing it will run arbitrary code on your machine. 2) Prefer an official release or package for the plane CLI if one exists instead of a raw script. 3) Provide PLANE_API_KEY with the minimum necessary permissions and keep it secret. 4) Ask the publisher to fix the registry metadata mismatch (it should declare the required binary and env vars) so the package manifest is consistent. 5) If you must install, inspect the downloaded file contents and consider running it in a safe environment first (e.g., container or VM).

Plane Skill

Interact with Plane.so project management via the plane CLI.

Installation

Download the CLI script and make it executable:

curl -o ~/.local/bin/plane https://raw.githubusercontent.com/JinkoLLC/plane-skill/main/scripts/plane
chmod +x ~/.local/bin/plane

Make sure ~/.local/bin is in your PATH.

Setup

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

Get your API key from: Plane → Profile Settings → Personal Access Tokens

The workspace slug is the URL path segment (e.g., for https://app.plane.so/my-team/ the slug is my-team).

Commands

Current User

plane me                      # Show authenticated user info

Workspace Members

plane members                 # List all workspace members (name, email, role, ID)

Projects

plane projects list                                      # List all projects
plane projects get PROJECT_ID                            # Get project details
plane projects create --name "My Project" --identifier "PROJ"  # Create project

Work Items (Issues)

# List work items
plane issues list -p PROJECT_ID
plane issues list -p PROJECT_ID --priority high --assignee USER_ID

# Get details
plane issues get -p PROJECT_ID ISSUE_ID

# Create
plane issues create -p PROJECT_ID --name "Fix login bug" --priority high
plane issues create -p PROJECT_ID --name "Feature" --assignee USER_ID --label LABEL_ID

# Update
plane issues update -p PROJECT_ID ISSUE_ID --state STATE_ID --priority medium

# Assign to members
plane issues assign -p PROJECT_ID ISSUE_ID USER_ID_1 USER_ID_2

# Delete
plane issues delete -p PROJECT_ID ISSUE_ID

# Search across workspace
plane issues search "login bug"

Comments

plane comments list -p PROJECT_ID -i ISSUE_ID            # List comments on a work item
plane comments list -p PROJECT_ID -i ISSUE_ID --all      # Show all activity (not just comments)
plane comments add -p PROJECT_ID -i ISSUE_ID "Looks good, merging now"  # Add a comment

Cycles (Sprints)

plane cycles list -p PROJECT_ID
plane cycles get -p PROJECT_ID CYCLE_ID
plane cycles create -p PROJECT_ID --name "Sprint 1" --start 2026-01-27 --end 2026-02-10

Modules

plane modules list -p PROJECT_ID
plane modules get -p PROJECT_ID MODULE_ID
plane modules create -p PROJECT_ID --name "Auth Module" --description "Authentication features"

States & Labels

plane states -p PROJECT_ID    # List workflow states (useful for getting state IDs)
plane labels -p PROJECT_ID    # List labels (useful for getting label IDs)

Output Formats

Default output is a formatted table. Add -f json for raw JSON:

plane projects list -f json
plane issues list -p PROJECT_ID -f json

Typical Workflow

1. plane projects list — find your project ID
2. plane states -p PROJECT_ID — see available states
3. plane members — find member IDs for assignment
4. plane issues create -p PROJECT_ID --name "Task" --priority high --assignee USER_ID
5. plane comments add -p PROJECT_ID -i ISSUE_ID "Started working on this"