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

Linear Core Workflow A

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

Implement a controlled Linear issue lifecycle from discovery through create, update, relation, comment, and archive actions.

MITAuto-check passedBackend & APIs

Install Linear Core Workflow A

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-core-workflow-a -a claude-code

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace linear-core-workflow-a --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/linear-core-workflow-a .claude/skills/linear-core-workflow-a && 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
linear-core-workflow-a
GitHub stars
2.8k
Token cost
~1.2k tokens
SKILL.md length
499 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Implement a controlled Linear issue lifecycle from discovery through create, update, relation, comment, and archive actions.

  • Works in 6 steps: Resolve the authenticated viewer,… → Translate the requested business… → Validate required fields, visibility,… → …
  • Automating issue operations with the GraphQL API
  • SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 7 more sections
  • Needs API_KEY and ACCESS_TOKEN

What it does

Linear Core Workflow A is an agent skill from jeremylongshore/tons-of-skills-marketplace. Implement a controlled Linear issue lifecycle from discovery through create, update, relation, comment, and archive actions. Use when automating issue operations with the GraphQL API or TypeScript SDK. Trigger with "automate Linear issues", "build an issue workflow", or "update Linear issue states".

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; live verification requires network access and an approved Linear workspace credential

It sits in Backend & APIs, covering GraphQL. It works with Linear, GraphQL and TypeScript. 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

  • Automating issue operations with the GraphQL API
  • With automate Linear issues
  • Build an issue workflow
  • Update Linear issue states

Example prompts

  • “automate Linear issues”
  • “build an issue workflow”
  • “update Linear issue states”
  • “/linear-core-workflow-a”

Requirements

  • A credential in API_KEY
  • A credential in ACCESS_TOKEN
  • Compatibility (from SKILL.md): Designed for Claude Code; live verification requires network access and an approved Linear workspace credential
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, Write, Edit

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Resolve the authenticated viewer, organization, target team, workflow states, labels, and assignees using read-only queries.
  2. Translate the requested business transition into an explicit create/update/comment/relation plan with stable IDs.
  3. Validate required fields, visibility, duplicate policy, and whether Triage changes the default initial state.
  4. Preview the exact mutation variables with sensitive or personal fields redacted.
  5. After approval, perform one mutation and verify both GraphQL errors and payload success before the next action.
  6. Return identifiers, resulting state, reconciliation query, and rollback or archive instructions.

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
    • Glob
    • Grep
    • WebFetch
    • Write
    • Edit

    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):

    • linear.app

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

  • Credentials

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

    • API_KEY
    • ACCESS_TOKEN

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

  • Compatibility

    Designed for Claude Code; live verification requires network access and an approved Linear workspace credential

    From compatibility in the SKILL.md frontmatter.

Context cost

Linear Core Workflow A loads about 1.2k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 499 words of instructions outside code blocks.

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

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). 499 words, ~1,222 tokens.

Download SKILL.mdSave it as .claude/skills/linear-core-workflow-a/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
linear-core-workflow-a
description
Implement a controlled Linear issue lifecycle from discovery through create, update, relation, comment, and archive actions. Use when automating issue operations with the GraphQL API or TypeScript SDK. Trigger with "automate Linear issues", "build an issue workflow", or "update Linear issue states".
allowed-tools
Read, Glob, Grep, WebFetch, Write, Edit
compatibility
Designed for Claude Code; live verification requires network access and an approved Linear workspace credential
argument-hint
[repository-path] [team-key] [dry-run|apply]
version
1.13.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
saas, linear, issue-workflow
model
inherit
effort
high

Linear Issue Lifecycle Workflow

Overview

Build an issue workflow that resolves workspace-owned identifiers first and treats each write as a reviewable, reversible business action.

Prerequisites

  • The target repository, Linear workspace, environment, and accountable owner
  • Current security, privacy, compliance, capacity, and change-control requirements
  • An approved Linear credential only when a bounded live verification is necessary

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Linear documentation and package metadata. Use Write or Edit only for requested implementation with known target files. Never write credentials, customer content, unrestricted environment output, or unredacted GraphQL variables.

Current Contract

  • issueCreate requires a team ID; without a state ID Linear selects the team's first Backlog state, or Triage when enabled.
  • The SDK uses verb-first mutation names such as createIssue, updateIssue, and archiveIssue.
  • Changes made during the first three minutes after issue creation are treated as part of creation and do not produce activity-log entries.

Authentication

Use a personal API key only for owner-controlled scripts, OAuth with PKCE for user-delegated applications, or an enabled client-credentials grant for approved automation. Personal keys use Authorization: <API_KEY>; OAuth tokens use Authorization: Bearer <ACCESS_TOKEN>. Store credentials server-side in an approved secret manager.

Treat app approval, team access, scope changes, credential creation, rotation, revocation, and production access as owner-approved actions.

Instructions

  1. Resolve the authenticated viewer, organization, target team, workflow states, labels, and assignees using read-only queries.
  2. Translate the requested business transition into an explicit create/update/comment/relation plan with stable IDs.
  3. Validate required fields, visibility, duplicate policy, and whether Triage changes the default initial state.
  4. Preview the exact mutation variables with sensitive or personal fields redacted.
  5. After approval, perform one mutation and verify both GraphQL errors and payload success before the next action.
  6. Return identifiers, resulting state, reconciliation query, and rollback or archive instructions.
Show full SKILL.md (193 more words)Show less

Approval Boundaries

Do not create, reveal, rotate, or revoke credentials; authorize an OAuth app; change scopes or team access; create, mutate, archive, or delete workspace data; configure or re-enable webhooks; import or export data; change roles, SCIM, or audit streaming; transmit diagnostics; change paid entitlements; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested.

Output

Return the workspace and team scope, auth mode without credential value, files and contracts inspected, exact operation names, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action.

Error Handling

ConditionResponse
Team or state not foundStop and list visible candidates; never fall back to the first team silently.
Duplicate issueReconcile by an approved external key or canonical URL before creating.
Partial mutation responseTreat any GraphQL error as unresolved and verify the issue by ID.
Rollback requestedPrefer a documented compensating update or archive; do not delete history casually.

Examples

Use a compact handoff that makes scope, mutation authority, and verification evidence reviewable.

Input:

text
team=ENG; action=create; title=redacted-summary; mode=dry-run

Expected handoff:

text
team-id=resolved; mutation=issueCreate; approval=pending; rollback=archive

Resources

© 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 1 other file (references) in skills/.curated/linear-core-workflow-a of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Linear Core Workflow A 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.

Linear Core Workflow A compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Linear Core Workflow A this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: PassMIT
GraphQL Operations with CodegenChrisWiles/claude-code-showcase6.1k3 repos~1.5kAutomated safety check: PassNone
Twenty Syncable Entity Wiringtwentyhq/twenty58k—~2.9kAutomated safety check: PassCustom licence
Linearletta-ai/lettabot327—~583Automated safety check: PassApache-2.0
Ar Io Gateway Operatorar-io/ar-io-node127—~8.8kAutomated safety check: NotesAGPL-3.0
Apollo Clientapollographql/skills117—~1.9kAutomated safety check: PassMIT

Similar skills

  • GraphQL Operations with Codegen

    ChrisWiles/claude-code-showcase

    Sets the rules for writing GraphQL queries and mutations in .gql files, running codegen, and using generated Apollo hooks with proper error and loading handling.

    6.1k GitHub starsUsed in 3 repos~1.5k tokens
    Backend & APIsAuto-check passed

  • Twenty Syncable Entity Wiring

    twentyhq/twenty

    Registers a new syncable entity in three NestJS modules and adds its service and GraphQL resolver layers when contributing to the Twenty server.

    58k GitHub stars~2.9k tokensUpdated today
    Backend & APIsAuto-check passed

  • Linear

    letta-ai/lettabot

    Manage Linear issues via GraphQL API. An agent skill from letta-ai/lettabot.

    327 GitHub stars~583 tokensUpdated 4 mo ago
    Backend & APIsAuto-check passed

  • Ar Io Gateway Operator

    ar-io/ar-io-node

    Operate any AR.IO node deployment — architecture, daily ops, diagnostics, and recurring pitfalls that apply to every operator.

    127 GitHub stars~8.8k tokensUpdated today
    Backend & APIsAuto-check: notes

  • Apollo Client

    apollographql/skills

    Guide for building React applications with Apollo Client 4.x.

    117 GitHub stars~1.9k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed

  • Linear API

    nesszer/linear-cli

    Execute raw GraphQL queries and mutations against the Linear API.

    138 GitHub stars~213 tokensUpdated 26 days ago
    Backend & APIsAuto-check: notes

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 Linear Core Workflow A

What does Linear Core Workflow A do?

Implement a controlled Linear issue lifecycle from discovery through create, update, relation, comment, and archive actions. Linear Core Workflow A is an agent skill from jeremylongshore/tons-of-skills-marketplace. Implement a controlled Linear issue lifecycle from discovery through create, update, relation, comment, and archive actions.

When should I use Linear Core Workflow A?

Linear Core Workflow A fits situations like: automating issue operations with the GraphQL API; with automate Linear issues; build an issue workflow; update Linear issue states.

How do I install Linear Core Workflow A in Claude Code?

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

How do I install Linear Core Workflow A in Codex?

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

Can I use Linear Core Workflow A 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 linear-core-workflow-a -a cursor` (or -a -a, -a or -a for the others). To copy it by hand, put the folder in .cursor/skills/linear-core-workflow-a, .gemini/skills/linear-core-workflow-a, .github/skills/linear-core-workflow-a and .opencode/skills/linear-core-workflow-a in your project.

What does Linear Core Workflow A need to run?

Going by SKILL.md and its folder, Linear Core Workflow A needs credentials named API_KEY and ACCESS_TOKEN. Our summary lists: A credential in API_KEY; A credential in ACCESS_TOKEN. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; live verification requires network access and an approved Linear workspace credential.

Does Linear Core Workflow A access the network?

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

Is Linear Core Workflow A 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 Linear Core Workflow A use?

Linear Core Workflow A 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 Linear Core Workflow A use?

About 1.2k tokens (SKILL.md is roughly 4.9k 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 816 tokens, read only when the agent opens those files.

What are the alternatives to Linear Core Workflow A?

Skills that share tags, products or a category with Linear Core Workflow A: GraphQL Operations with Codegen (ChrisWiles/claude-code-showcase, 6.1k stars), Twenty Syncable Entity Wiring (twentyhq/twenty, 58k stars), Linear (letta-ai/lettabot, 327 stars) and Ar Io Gateway Operator (ar-io/ar-io-node, 127 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Linear Core Workflow A?

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.