agentleFS
jonathanmalkinjonathanmalkin/jules/.claude/skills/plane/SKILL.md

plane

Skill65 starsChanged 7 months agoMITView on GitHub

Plane.so project management interface via direct API scripts. Use when user says 'plane', 'check plane', 'update plane', 'GP-42', 'plane status', 'sync to plane', 'look up task', or any Plane-related project management action.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All Plane operations use Python scripts calling the REST API via curl.

    line 13
  2. Distinctive:

    No MCP server dependency — works in interactive and batch contexts.

    line 14
  3. Very specific:

    All scripts require PLANE_API_KEY.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Plane.so Skill

Comprehensive interface to the Plane Cloud workspace ([your-workspace-slug], project Grand Plan).

Architecture: Direct API Scripts

All Plane operations use Python scripts calling the REST API via curl. No MCP server dependency — works in interactive and batch contexts.

OperationScript
List items, cycles, modulesplane_list.py items, plane_list.py cycles, plane_list.py modules
List items in a moduleplane_list.py module-items "Pending Review"
Filter by state/due dateplane_list.py items --state todo,in_progress --due-within 7
Create item (+ add to module)plane_create.py "Title" --module "Pending Review"
Get item by identifier (GP-42)plane_lookup.py GP-42
Search items by keywordplane_search.py "keyword"
Pull Plane status → markdownplane_pull.py [--apply]
Compare local vs Planeplane_compare.py [--diff-only] [--module slug]

Gap Script Usage

All scripts require PLANE_API_KEY. On Mac, inject at call time:

# Lookup by identifier
PLANE_API_KEY=$(op item get "Plane API" --vault "Dev Secrets" --fields label="API Key" --reveal) \
    python3 .claude/skills/plane/scripts/plane_lookup.py GP-42

# Search
PLANE_API_KEY=$(op item get "Plane API" --vault "Dev Secrets" --fields label="API Key" --reveal) \
    python3 .claude/skills/plane/scripts/plane_search.py "authentication" --state todo

# Push: markdown -> Plane (dry-run by default, --apply for live)
python3 .claude/skills/plane/scripts/plane_sync.py          # dry-run
python3 .claude/skills/plane/scripts/plane_sync.py --apply   # live changes

# Pull: Plane -> markdown (dry-run by default, --apply writes with backup)
PLANE_API_KEY=$(op item get "Plane API" --vault "Dev Secrets" --fields label="API Key" --reveal) \
    python3 .claude/skills/plane/scripts/plane_pull.py           # dry-run
PLANE_API_KEY=$(op item get "Plane API" --vault "Dev Secrets" --fields label="API Key" --reveal) \
    python3 .claude/skills/plane/scripts/plane_pull.py --apply   # live (backs up to .plane-pull-backup/)

# Compare: side-by-side diff (read-only)
PLANE_API_KEY=$(op item get "Plane API" --vault "Dev Secrets" --fields label="API Key" --reveal) \
    python3 .claude/skills/plane/scripts/plane_compare.py              # full table
PLANE_API_KEY=$(op item get "Plane API" --vault "Dev Secrets" --fields label="API Key" --reveal) \
    python3 .claude/skills/plane/scripts/plane_compare.py --diff-only  # only mismatches
PLANE_API_KEY=$(op item get "Plane API" --vault "Dev Secrets" --fields label="API Key" --reveal) \
    python3 .claude/skills/plane/scripts/plane_compare.py --module infrastructure  # filter by module

The sync script auto-injects credentials via op if PLANE_API_KEY is not set.

Workspace Defaults

See references/our-workspace.md for all IDs, states, modules, labels, and conventions.

  • Workspace: [your-workspace-slug]
  • Project: Grand Plan (UUID: 8238b353-5e87-4b72-b199-fec061be8b98)
  • Identifier prefix: GP
  • [Your Name]'s user ID: [YOUR_USER_ID]

API Patterns

See references/patterns.md for:

  • Why curl (not urllib): Plane returns 403 with Python HTTP clients
  • Rate limiting: 1.1s between calls
  • Cursor-based pagination
  • Issue title convention: Description [TASK-ID]

Container Scope

MCP server is Mac-only (interactive Claude Code sessions). It launches via start-plane-mcp.sh, which resolves the API key from 1Password using the OP_SERVICE_ACCOUNT_TOKEN (set in ~/.zshrc). Batch jobs use gap scripts with PLANE_API_KEY from macOS Keychain (security find-generic-password -s plane-api-key).

Reference Docs

  • references/our-workspace.md -- IDs, states, modules, labels
  • references/api-reference.md -- Condensed endpoint reference
  • references/mcp-tools.md -- MCP server tool catalog (populate after smoke test)
  • references/patterns.md -- Learned API patterns and gotchas

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.