My Plane

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

Security Scan

The skill's instructions largely match a Plane CLI integration, but there are inconsistencies in declared requirements and it asks you to download and run a third‑party binary with no checksum — proceed with caution.

Purpose & Capability

The SKILL.md clearly targets the Plane.so CLI and requires PLANE_API_KEY and PLANE_WORKSPACE, which are appropriate for the described functionality. However, the registry metadata shown above (no required bins/env) contradicts the SKILL.md metadata that declares a required 'plane' binary and two environment vars.

Instruction Scope

All runtime instructions are limited to installing/running the 'plane' CLI and exporting Plane-related environment variables and base URL. The skill does not instruct the agent to read unrelated files, transmit data to unexpected endpoints, or access other system credentials.

Install Mechanism

The install instructions ask the user (and metadata specifies) to download a single executable from a GitHub releases URL and place it in ~/.local/bin. While GitHub Releases is a common host, downloading and running a third‑party native binary without a checksum/signature is higher risk — the archive isn't extracted but arbitrary code will run on the machine.

Credentials

Requested environment variables (PLANE_API_KEY, PLANE_WORKSPACE, optional PLANE_BASE_URL) are proportional to a Plane CLI skill. Note the registry-level requirements were empty but SKILL.md metadata lists them — that inconsistency should be resolved before trusting the skill.

Persistence & Privilege

The skill does not request 'always: true' and does not declare any system config paths or privileges beyond installing a user-local binary. Autonomous invocation remains allowed by default (normal for skills).

What to consider before installing

This skill appears to be a straightforward wrapper around the Plane CLI and needs your Plane API key and workspace slug — which is expected. Two things to check before installing: (1) The SKILL.md metadata requires the 'plane' binary and PLANE_API_KEY/PLANE_WORKSPACE, but the registry summary shows no required env/bins — ask the publisher to reconcile that mismatch. (2) The install method downloads a native executable from a GitHub release with no checksum or signature; only install if you trust the GitHub repo/owner. Safer steps: inspect the repository source, verify release checksums or signatures, prefer official vendor-distributed packages, avoid running as root, and limit the API key scope or rotate it after use. If the author can provide a signed release or reproducible build instructions, that would increase confidence.

Plane Skill

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

Installation

Download the single executable file:

curl -L -o ~/.local/bin/plane https://github.com/HonLuk/my-plane/releases/latest/download/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"
# Optional: for self-hosted Plane (default: https://api.plane.so)
export PLANE_BASE_URL="https://api.plane.so"

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
plane issues list -p PROJECT_ID --state STATE_ID

# Get details
plane issues get -p PROJECT_ID ISSUE_ID
plane issues get-short PROJ-SEQ  # e.g., PROJ-123 (fastest way)

# 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

Pagination

All list commands support cursor-based pagination. Pagination info is displayed above results:

plane projects list
# Shows:
# Pagination: total: 50 | pages: 5 | showing: 10
# Next page: --cursor 10:1:0

# Use cursor to navigate
plane issues list -p PROJECT_ID --cursor "10:1:0"

# Control page size
plane issues list -p PROJECT_ID --per-page 20

Field Selection

# Return only specific fields
plane issues list -p PROJECT_ID --fields "id,name,state"

# Expand related objects
plane issues list -p PROJECT_ID --expand "assignees,state"

# Sort results
plane issues list -p PROJECT_ID --order-by "-created_at"

Getting Help

Every command has detailed help:

plane --help
plane issues --help
plane issues create --help

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"