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 Deploy Integration

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

Connect deployment evidence to Linear work without granting the deploy pipeline broad issue-edit authority.

MITAuto-check passedDevOps & Cloud

Install Linear Deploy Integration

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

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

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

At a glance

Connect deployment evidence to Linear work without granting the deploy pipeline broad issue-edit authority.

  • Works in 6 steps: Inspect deployment receipts, Linear's… → Choose the native integration, a… → Resolve issue identifiers from trusted… → …
  • Linking releases
  • SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 7 more sections
  • Needs API_KEY and ACCESS_TOKEN

What it does

Linear Deploy Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Connect deployment evidence to Linear work without granting the deploy pipeline broad issue-edit authority. Use when linking releases, commits, pull requests, or rollback receipts to Linear issues. Trigger with "link deploys to Linear", "record Linear release evidence", or "update Linear after deployment".

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 DevOps & Cloud, covering Deployment and Pull requests. It works with Linear and GraphQL. 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

  • Linking releases
  • Rollback receipts to Linear issues
  • With link deploys to Linear
  • Record Linear release evidence

Example prompts

  • “link deploys to Linear”
  • “record Linear release evidence”
  • “update Linear after deployment”
  • “/linear-deploy-integration”

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. Inspect deployment receipts, Linear's source-control integration, identifier conventions, and current issue-transition policy.
  2. Choose the native integration, a read-only evidence link, or a custom mutation path based on the actual gap.
  3. Resolve issue identifiers from trusted release metadata; reject free-form or ambiguous branch parsing.
  4. Preview comments, links, labels, or state changes and separate evidence recording from workflow transition authority.
  5. After the deployment system reports final status and approval is present, perform one idempotent update.
  6. Re-query the issue and preserve the deployment, mutation, and rollback receipts.

What it can do on your machine

Read from SKILL.md and the folder at commit 80f86df. 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 Deploy Integration loads about 1.2k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 494 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~83
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
~2.1k

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 80f86df, republished under its MIT licence (© jeremylongshore). 494 words, ~1,235 tokens.

Download SKILL.mdSave it as .claude/skills/linear-deploy-integration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
linear-deploy-integration
description
Connect deployment evidence to Linear work without granting the deploy pipeline broad issue-edit authority. Use when linking releases, commits, pull requests, or rollback receipts to Linear issues. Trigger with "link deploys to Linear", "record Linear release evidence", or "update Linear after deployment".
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] [deployment-provider] [dry-run|apply]
version
1.13.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
saas, linear, deployment
model
inherit
effort
high

Linear Deployment Evidence Integration

Overview

Design deployment-to-work traceability around stable issue identifiers and owner-approved state changes, while preferring native source-control integration where it satisfies the requirement.

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

  • Linear's GraphQL API is the explicit mutation surface; branch names and commit text are conventions, not proof that a deployment occurred.
  • OAuth or app-actor access should be scoped to the teams and operations the deployment reporter actually needs.
  • Every mutation result must be checked for GraphQL errors and reconciled by issue ID.

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. Inspect deployment receipts, Linear's source-control integration, identifier conventions, and current issue-transition policy.
  2. Choose the native integration, a read-only evidence link, or a custom mutation path based on the actual gap.
  3. Resolve issue identifiers from trusted release metadata; reject free-form or ambiguous branch parsing.
  4. Preview comments, links, labels, or state changes and separate evidence recording from workflow transition authority.
  5. After the deployment system reports final status and approval is present, perform one idempotent update.
  6. Re-query the issue and preserve the deployment, mutation, and rollback receipts.
Show full SKILL.md (185 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
No stable issue identifierRecord unmatched evidence for review; do not update a guessed issue.
Deployment status uncertainWait for the provider's final receipt before mutating Linear.
Transition not authorizedAttach or return evidence without changing state.
RollbackRecord the rollback as a new event; do not erase the original deployment evidence.

Examples

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

Input:

text
deployment=prod-2026-09-11.4; issue=ENG-123; status=succeeded; transition=approval-required

Expected handoff:

text
evidence-link=planned; state-change=withheld; idempotency=deployment-id

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-deploy-integration of jeremylongshore/tons-of-skills-marketplace.

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

Open the folder on GitHubat commit 80f86df

Compare with similar skills

Linear Deploy Integration 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 Deploy Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Linear Deploy Integration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: PassMIT
Monstermq Broker Configvogler75/monster-mq143—~2.2kAutomated safety check: PassGPL-3.0
Update Qmyc-software/qm15k—~1.8kAutomated safety check: PassMIT
Releasear-io/ar-io-node127—~4.2kAutomated safety check: NotesAGPL-3.0
Land and Deploygarrytan/gstack136k—~18kAutomated safety check: NotesMIT
Finding TriageHacktronAI/skills115—~2.9kAutomated safety check: NotesMIT

Similar skills

  • Monstermq Broker Config

    vogler75/monster-mq

    Guide for configuring, deploying, and operating the MonsterMQ broker.

    143 GitHub stars~2.2k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Update Qm

    yc-software/qm

    Update a QM source fork by merging upstream, or upgrade a package deployment dependency, and open a PR.

    15k GitHub stars~1.8k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Release

    ar-io/ar-io-node

    Drive the AR.IO Node release process end-to-end — preflight checks, prepare commit, finalize with image SHAs, test docker compose profiles, tag & publish, and post-release cleanup.

    127 GitHub stars~4.2k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

  • Land and Deploy

    garrytan/gstack

    Merges a pull request, waits for CI and the deploy, then verifies production health with canary checks, picking up where /ship leaves off.

    136k GitHub stars~18k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

  • Finding Triage

    HacktronAI/skills

    Interactively validate and triage Hacktron findings against the actual source code and (optionally) a live deployment, separate true positives from false positives, adjust severity, then either…

    115 GitHub stars~2.9k tokensUpdated 4 mo ago
    Backend & APIsAuto-check: notes

  • GitHub Actions Workflow Automation

    ruvnet/agentic-flow

    Generates and optimizes GitHub Actions workflows with swarm coordination, using named modes for PR management, issue tracking, releases and repository structure.

    819 GitHub starsUsed in 6 repos~6k tokens
    DevOps & CloudAuto-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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    Auto-check passed

Works with

Categories

Questions about Linear Deploy Integration

What does Linear Deploy Integration do?

Connect deployment evidence to Linear work without granting the deploy pipeline broad issue-edit authority. Linear Deploy Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Connect deployment evidence to Linear work without granting the deploy pipeline broad issue-edit authority.

When should I use Linear Deploy Integration?

Linear Deploy Integration fits situations like: linking releases; rollback receipts to Linear issues; with link deploys to Linear; record Linear release evidence.

How do I install Linear Deploy Integration in Claude Code?

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

How do I install Linear Deploy Integration in Codex?

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

Can I use Linear Deploy Integration 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-deploy-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linear-deploy-integration, .gemini/skills/linear-deploy-integration, .github/skills/linear-deploy-integration and .opencode/skills/linear-deploy-integration in your project.

What does Linear Deploy Integration need to run?

Going by SKILL.md and its folder, Linear Deploy Integration 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 Deploy Integration 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 Deploy Integration 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 Deploy Integration use?

Linear Deploy Integration 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 Deploy Integration 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 817 tokens, read only when the agent opens those files.

What are the alternatives to Linear Deploy Integration?

Skills that share tags, products or a category with Linear Deploy Integration: Monstermq Broker Config (vogler75/monster-mq, 143 stars), Update Qm (yc-software/qm, 15k stars), Release (ar-io/ar-io-node, 127 stars) and Land and Deploy (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Linear Deploy Integration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 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.