linear-claude-skill

linear-claude-skill is a skill for Claude Code, Codex from beel-collab/presets.dev. It costs 8 tokens per session (3,640 once invoked), scanned A, a copy of linear-claude-skill, MIT.

A set of tools and workflows for managing Linear, a project-management app for software teams.

In plain words
What is it for?
Use it to view, create, update, list, and comment on Linear issues, and to manage related projects and teams.
Why use it?
It removes the need to handle issues, projects, teams, statuses, and comments manually in the Linear interface.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/linear-helpers.mjs update-status Done 123 124 125.

Good fit Use it to view, create, update, list, and comment on Linear issues, and to manage related projects and teams.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/beel-collab/presets.dev
agentmods
npx agentmods add skills/beel-collab/presets.dev/linear-claude-skill

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for linear-claude-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/beel-collab/presets.dev/linear-claude-skill.svg)](https://agentmods.dev/skills/beel-collab/presets.dev/linear-claude-skill)
Your own site
<a href="https://agentmods.dev/skills/beel-collab/presets.dev/linear-claude-skill"><img src="https://agentmods.dev/badge/skills/beel-collab/presets.dev/linear-claude-skill.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,640 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00008 $0.03640
Opus 5 $0.00004 $0.01820
Sonnet 5 $0.00002 $0.00728
Haiku 4.5 $0.00001 $0.00364

Measured 4d ago against content hash 09b27d6e304e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

linear-claude-skill scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to linear-claude-skill — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

claude/skills/project-management/linear-claude-skill/SKILL.md · 549 lines

How it starts

The opening of the file, as written. The whole thing — 549 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When to Use This Skill

Manage Linear issues, projects, and teams

Use this skill when working with manage linear issues, projects, and teams.

Linear

Tools and workflows for managing issues, projects, and teams in Linear.


⚠️ Tool Availability (READ FIRST)

This skill supports multiple tool backends. Use whichever is available:

  1. MCP Tools (mcp__linear) - Use if available in your tool set
  2. Linear CLI (linear command) - Always available via Bash
  3. Helper Scripts - For complex operations

If MCP tools are NOT available, use the Linear CLI via Bash:

# View an issue
linear issues view ENG-123

# Create an issue
linear issues create --title "Issue title" --description "Description"

# Update issue status (get state IDs first)
linear issues update ENG-123 -s "STATE_ID"

# Add a comment
linear issues comment add ENG-123 -m "Comment text"

# List issues
linear issues list

Do NOT report "MCP tools not available" as a blocker - use CLI instead.


When to Use This Skill

Manage Linear issues, projects, and teams

Use this skill when working with manage linear issues, projects, and teams.

🔐 Security: Varlock Integration

CRITICAL: Never expose API keys in terminal output or Claude's context.

Safe Commands (Always Use)

# Validate LINEAR_API_KEY is set (masked output)
varlock load 2>&1 | grep LINEAR

# Run commands with secrets injected
varlock run -- npx tsx scripts/query.ts "query { viewer { name } }"

# Check schema (safe - no values)
cat .env.schema | grep LINEAR

Unsafe Commands (NEVER Use)

# ❌ NEVER - exposes key to Claude's context
linear config show
echo $LINEAR_API_KEY
printenv | grep LINEAR
cat .env

Setup for New Projects

  1. Create .env.schema with @sensitive annotation:

    # @type=string(startsWith=lin_api_) @required @sensitive
    LINEAR_API_KEY=
    
  2. Add LINEAR_API_KEY to .env (never commit this file)

  3. Configure MCP to use environment variable:

    {
      "mcpServers": {
        "linear": {
          "env": { "LINEAR_API_KEY": "${LINEAR_API_KEY}" }
        }
      }
    }
    

Read the full file on GitHub · 549 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 549 lines · 8 tokens per session scan A 09b27d6e304e

Subscribe to this mod's changes

linear-claude-skill is a skill published in the GitHub repository beel-collab/presets.dev (2 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 3,640 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to linear-claude-skill, differing in 16 lines, and is treated as a copy.

Related

Other skills, from other repositories

github-triage

Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

sammcj/agentic-coding · 50 tokens

backlog

Capture single backlog items, or list and triage an existing project backlog. Use this skill whenever the user wants to file a bug, feature request, or backlog item without writing a full PRD, including casual requests mid-conversation like "create an issue for that", "add this to the backlog", or "file a quick bug…

sammcj/agentic-coding · 182 tokens

reframe-voice

Write, rewrite, or review content in the evidence-led reframe voice style. Use when the user explicitly asks to write in "reframe voice" or "reframe style". Do NOT use for general writing tasks.

sammcj/agentic-coding · 49 tokens

to-tickets

Break a plan, spec, or the current conversation into independently-grabbable tickets on the project issue tracker using tracer-bullet vertical slices, each declaring the tickets that block it. Use when user wants to convert a plan or spec into tickets, create implementation tickets, or break down work into issues.

sammcj/agentic-coding · 64 tokens

to-spec

Turn the current conversation context into a spec and submit it as a GitHub issue. Use when user wants to create a spec or PRD from the current context.

sammcj/agentic-coding · 36 tokens

qa-to-issues

Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Use when user wants to report bugs in their own codebase and create Github issues conversationally.

sammcj/agentic-coding · 43 tokens