New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Plane

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Plane is a team behavior observatory — synthesize Plane API data into observations about how teams actually behave under pressure, not just ticket state.

MITAuto-check passedAgent Workflows

Install Plane

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill plane -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace plane --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/plane .claude/skills/plane && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
plane
GitHub stars
2.8k
Token cost
~1.9k tokens
SKILL.md length
818 words
Files
6 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Plane is a team behavior observatory — synthesize Plane API data into observations about how teams actually behave under pressure, not just ticket state.

  • Works in 4 steps: Resolve target project → Route to compound command → Execute via plane-analyst agent → …
  • Investigating why is this teams plan diverging from reality
  • SKILL.md covers Overview, Prerequisites, Authentication and Instructions, plus 4 more sections
  • Needs PLANE_API_KEY

What it does

Plane is an agent skill from jeremylongshore/tons-of-skills-marketplace. Plane is a team behavior observatory — synthesize Plane API data into observations about how teams actually behave under pressure, not just ticket state. Five compound commands surface cycle velocity vs. plan, stale-ticket ownership churn, reviewer gate strength, stated-vs-actual priority drift, and cross-project workload concentration. Reads from the live mcpplane MCP server when present; documentation-only otherwise. Use when investigating "why is this team's plan diverging from reality", auditing cycle health…

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `agents/plane-analyst.md`, `agents/plane-expert.md` and `references/api-surface.md`). Compatibility notes: Designed for Claude Code; requires mcpplane MCP server configured (PLANEAPIKEY, PLANEWORKSPACESLUG, PLANEAPIHOSTURL env vars)

It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Investigating why is this teams plan diverging from reality
  • Auditing cycle health
  • Finding orphan tickets
  • Identifying review bottlenecks

Example prompts

  • “why is this team”
  • “/plane-cycle-velocity”
  • “/plane-stale-tickets”
  • “/plane”

Requirements

  • A credential in PLANE_API_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code; requires mcp__plane MCP server configured (PLANE_API_KEY, PLANE_WORKSPACE_SLUG, PLANE_API_HOST_URL env vars)
  • Pre-approved tools (allowed-tools): Read, Bash(jq:*), Bash(date:*), AskUserQuestion

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Resolve target project
  2. Route to compound command
  3. Execute via plane-analyst agent
  4. Interpret the signal

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash(jq:*)
    • Bash(date:*)
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.plane.so

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • PLANE_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code; requires mcp__plane MCP server configured (PLANE_API_KEY, PLANE_WORKSPACE_SLUG, PLANE_API_HOST_URL env vars)

    From compatibility in the SKILL.md frontmatter.

Context cost

Plane loads about 1.9k tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 209 tokens; SKILL.md has 818 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~209
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 818 words, ~1,932 tokens.

Download SKILL.mdSave it as .claude/skills/plane/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
plane
description
Plane is a team behavior observatory — synthesize Plane API data into observations about how teams actually behave under pressure, not just ticket state. Five compound commands surface cycle velocity vs. plan, stale-ticket ownership churn, reviewer gate strength, stated-vs-actual priority drift, and cross-project workload concentration. Reads from the live mcp__plane MCP server when present; documentation-only otherwise. Use when investigating "why is this team's plan diverging from reality", auditing cycle health, finding orphan tickets, identifying review bottlenecks, or onboarding to a new project. Trigger with "/plane-cycle-velocity", "/plane-stale-tickets", "/plane-reviewer-gate-strength", "/plane-priority-drift", "/plane-cross-project-load", "audit Plane cycle", "team behavior plane", "how is my team behaving".
allowed-tools
Read, Bash(jq:*), Bash(date:*), AskUserQuestion
compatibility
Designed for Claude Code; requires mcp__plane MCP server configured (PLANE_API_KEY, PLANE_WORKSPACE_SLUG, PLANE_API_HOST_URL env vars)
version
0.3.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
plane, project-management, team-behavior, observability, productivity
model
inherit

Plane — Team Behavior Observatory

A behavioral observation layer on top of Plane's project-tracking API. This skill does not wrap Plane CRUD — mcp__plane already does that and you should call it directly for ticket entry, status changes, etc.

Instead, this skill answers behavioral questions about how a team is actually performing under pressure: cycle velocity vs. plan, ownership churn, reviewer gate strength, priority drift, and cross-project load. Each question is answered by a compound command that synthesizes data across multiple Plane endpoints — observations no single endpoint exposes.

Overview

The NOI (references/noi.md) is the design anchor: Plane is a team behavior observatory. Five compound commands derive from that framing:

  1. /plane-cycle-velocity — does cycle close-out match cycle planning?
  2. /plane-stale-tickets — which In Progress tickets are quietly failing under shared ownership?
  3. /plane-reviewer-gate-strength — which reviewers gate-keep harder than the spec demands?
  4. /plane-priority-drift — does the team plan high-priority work but ship low-priority work?
  5. /plane-cross-project-load — which engineers are spread across too many active projects?

None of these are answerable from any single Plane API call. Each requires cross-endpoint synthesis. That synthesis is the value.

Prerequisites

  • mcp__plane MCP server installed and configured (env vars PLANE_API_KEY, PLANE_WORKSPACE_SLUG, PLANE_API_HOST_URL)
  • A Plane workspace with at least one project, cycle, and active issues (otherwise the commands return informative empty states)

Authentication

This skill does not handle credentials directly. Auth is delegated to the MCP server. See references/api-surface.md for the env-var setup; if mcp__plane returns an auth error, the skill surfaces the error verbatim and instructs the user to verify their token.

Instructions

Mode detection

Determine user intent from their prompt:

  • Compound query mode (default): user asks about cycle health, team behavior, stale tickets, reviewer patterns, priority drift, or workload distribution → route to plane-analyst agent (see agents/plane-analyst.md) which orchestrates the compound commands.
  • API help mode: user asks "how do I query X in Plane" or "what endpoint does Y" → route to plane-expert agent (see agents/plane-expert.md) which answers from references/api-surface.md without firing live API calls.
  • Skill metadata: user asks "what does this skill do" / "explain plane skill" → return the Overview above + the 5 commands.

If unclear, use AskUserQuestion:

Are you asking about (a) team behavior / cycle health / patterns, or (b) how to use a specific Plane API endpoint?

Step 1: Resolve target project

Most compound commands operate on a specific project. Extract the project slug or readable identifier (e.g., BRAVES, OPS) from the user's prompt.

If absent, list available projects via mcp__plane__get_projects and ask which one. Cache the chosen project for the rest of the conversation.

Step 2: Route to compound command

Match user intent to one of the five commands:

User asks about...Command
cycle velocity, sprint completion, overrun/plane-cycle-velocity
stale tickets, orphan work, ownership churn/plane-stale-tickets
reviewer bottlenecks, blocked PRs, gate-keeping/plane-reviewer-gate-strength
priority drift, planning vs. reality, P1 vs. P3/plane-priority-drift
workload distribution, project sprawl, focus/plane-cross-project-load

Read references/compound-commands.md for the exact endpoint sequence and output format per command.

Show full SKILL.md (338 more words)Show less
Step 3: Execute via plane-analyst agent

Invoke the analyst agent (agents/plane-analyst.md) with the chosen command + project. The agent:

  1. Calls the relevant mcp__plane__* tools in sequence
  2. Performs the JOIN logic
  3. Computes the behavioral score per the command's formula
  4. Renders the output table per the format in compound-commands.md
  5. Adds a "Behavioral signal" interpretation paragraph

If mcp__plane is unavailable, the agent emits a documentation-only response: shows what the command WOULD return, plus the install hint.

Step 4: Interpret the signal

The output is observations, not prescriptions. The skill says "this team plans P1s and ships P3s — the planning conversation is theater." It does NOT say "fire the planner." Interpretation belongs to the human reading the report.

Output

Each compound command produces:

  • A table of metrics specific to that observation
  • A "Behavioral signal" paragraph that names the pattern in plain language
  • Optionally, a follow-up suggestion (e.g., "consolidate projects" / "split this queue") — framed as a question the team can take to its retro

Error Handling

ErrorRecovery
mcp__plane unavailableEmit documentation-only output + install hint pointing at ~/.claude.json MCP config
API rate limit (429)Back off + retry with exponential delay; if persistent, advise user to wait and re-run
Empty project (no cycles / issues)Return informative empty state explaining why the command can't compute
Auth error (401/403)Surface verbatim + instruct user to verify env vars or re-issue token
Workspace member lookup failsFall back to assignee UUIDs in output (less readable but functional)

Examples

"How is my team performing on cycle velocity?"

/plane-cycle-velocity BRAVES

→ Renders the cycle-velocity table from references/compound-commands.md § Command 1.

"Are we shipping what we plan?"

/plane-priority-drift BRAVES

→ Renders the priority-drift table; surfaces the gap between planned and shipped priorities.

"Which engineers are stretched too thin?"

/plane-cross-project-load

→ Walks the entire workspace; lists engineers with their active-project / active-cycle / open-issue counts; flags crisis-level stretch.

Resources

  • NOI — the secret-identity statement that anchors every command
  • API surface — endpoints consumed + auth + pagination
  • Compound commands — exact endpoint sequence + output format per command
  • Plane docs — upstream API reference
  • mcp__plane MCP server — direct CRUD wrapper this skill builds on top of

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in skills/.curated/plane of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • agents/plane-analyst.md
  • agents/plane-expert.md
  • references/api-surface.md
  • references/compound-commands.md
  • references/noi.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Plane next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Plane compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Plane this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.9kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k4 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Crush Configurationcharmbracelet/crush29k—~3.7kAutomated safety check: PassCustom licence
Context Mode Output Sandboxmksglu/context-mode26k—~4.1kAutomated safety check: PassCustom licence

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 4 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed

  • Crush Configuration

    charmbracelet/crush

    Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.

    29k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Context Mode Output Sandbox

    mksglu/context-mode

    Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.

    26k GitHub stars~4.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Warp GUI to Agent CLI Migration

    warpdotdev/warp

    Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.

    65k GitHub starsUsed in 1 repo~2.1k tokens
    Agent WorkflowsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Plane

What does Plane do?

Plane is a team behavior observatory — synthesize Plane API data into observations about how teams actually behave under pressure, not just ticket state. Plane is an agent skill from jeremylongshore/tons-of-skills-marketplace. Plane is a team behavior observatory — synthesize Plane API data into observations about how teams actually behave under pressure, not just ticket state.

When should I use Plane?

Plane fits situations like: investigating why is this teams plan diverging from reality; auditing cycle health; finding orphan tickets; identifying review bottlenecks.

How do I install Plane in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill plane -a claude-code`. Or copy the skill folder (skills/.curated/plane in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/plane in your project. Claude Code loads it when a task matches its description.

How do I install Plane in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill plane -a codex`. Or copy the skill folder (skills/.curated/plane in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/plane in your project. Codex loads it when a task matches its description.

Can I use Plane in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill plane -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plane, .gemini/skills/plane, .github/skills/plane and .opencode/skills/plane in your project.

What does Plane need to run?

Going by SKILL.md and its folder, Plane needs credentials named PLANE_API_KEY. Our summary lists: A credential in PLANE_API_KEY. Its frontmatter pre-approves these tools: Read, Bash(jq:*), Bash(date:*), AskUserQuestion. Compatibility (from SKILL.md): Designed for Claude Code; requires mcp__plane MCP server configured (PLANE_API_KEY, PLANE_WORKSPACE_SLUG, PLANE_API_HOST_URL env vars).

Does Plane access the network?

SKILL.md names 1 domain. As links in the text: docs.plane.so. This is read from the text; nothing was executed.

Is Plane safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Plane use?

Plane is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Plane use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4k tokens, read only when the agent opens those files.

What are the alternatives to Plane?

Skills that share tags, products or a category with Plane: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Crush Configuration (charmbracelet/crush, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plane?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.