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 Upgrade Migration

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

Upgrade a Linear integration across SDK releases and GraphQL deprecations with typed inventory, staged verification, and rollback.

MITAuto-check passedBackend & APIs

Install Linear Upgrade Migration

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

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

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

At a glance

Upgrade a Linear integration across SDK releases and GraphQL deprecations with typed inventory, staged verification, and rollback.

  • Works in 6 steps: Record current Node, SDK, lockfile,… → Read the target package metadata,… → Classify compile-time renames,… → …
  • Package updates
  • SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 7 more sections
  • Needs API_KEY and ACCESS_TOKEN

What it does

Linear Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Upgrade a Linear integration across SDK releases and GraphQL deprecations with typed inventory, staged verification, and rollback. Use when package updates or schema notices require code changes. Trigger with "upgrade Linear SDK", "migrate Linear API code", or "fix Linear deprecation".

Its SKILL.md is about 1.3k 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 GraphQL and Linear. 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

  • Package updates
  • Schema notices require code changes
  • With upgrade Linear SDK
  • Migrate Linear API code

Example prompts

  • “upgrade Linear SDK”
  • “migrate Linear API code”
  • “fix Linear deprecation”
  • “/linear-upgrade-migration”

Requirements

  • Node.js
  • 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. Record current Node, SDK, lockfile, generated types, GraphQL operations, custom raw queries, and deprecated-field usage.
  2. Read the target package metadata, repository changes, generated schema/type diff, and applicable Linear API changelog entries.
  3. Classify compile-time renames, behavioral changes, auth/data implications, and runtime-only risks.
  4. Upgrade on a bounded branch, commit the resolved lockfile, and repair adapters before business call sites.
  5. Run static checks, unit/fixture tests, GraphQL contract tests, and an approved read-only workspace probe.
  6. Stage rollout with package rollback instructions, monitoring thresholds, and schema reconciliation evidence.

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 Upgrade Migration loads about 1.3k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 78 tokens; SKILL.md has 508 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
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 cfae287, republished under its MIT licence (© jeremylongshore). 508 words, ~1,253 tokens.

Download SKILL.mdSave it as .claude/skills/linear-upgrade-migration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
linear-upgrade-migration
description
Upgrade a Linear integration across SDK releases and GraphQL deprecations with typed inventory, staged verification, and rollback. Use when package updates or schema notices require code changes. Trigger with "upgrade Linear SDK", "migrate Linear API code", or "fix Linear deprecation".
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] [target-version-or-deprecation]
version
1.13.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
saas, linear, upgrade
model
inherit
effort
high

Linear SDK and Schema Upgrade

Overview

Derive the migration from the installed/current SDK diff and live schema instead of assuming every version change repeats the historical 1.x-to-2.x rename.

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

  • The historical SDK 2.x migration changed mutations from model-first to verb-first names; modern upgrades must use actual release and type changes.
  • Linear GraphQL has no conventional versioned API; deprecated fields use @deprecated, and API changes appear in the changelog with an [API] prefix.
  • On 2026-09-11 npm reported @linear/sdk 95.0.0 requiring Node.js >=18.x; recheck before each upgrade.

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. Record current Node, SDK, lockfile, generated types, GraphQL operations, custom raw queries, and deprecated-field usage.
  2. Read the target package metadata, repository changes, generated schema/type diff, and applicable Linear API changelog entries.
  3. Classify compile-time renames, behavioral changes, auth/data implications, and runtime-only risks.
  4. Upgrade on a bounded branch, commit the resolved lockfile, and repair adapters before business call sites.
  5. Run static checks, unit/fixture tests, GraphQL contract tests, and an approved read-only workspace probe.
  6. Stage rollout with package rollback instructions, monitoring thresholds, and schema reconciliation evidence.
Show full SKILL.md (194 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 release evidenceDo not guess migration steps from the version number; inspect the package/schema diff.
Node incompatibleUpgrade runtime through its own approved lane or choose a supported SDK version.
Deprecated field still worksSchedule removal from the documented notice; do not rely on a non-functioning stub.
Live probe differsStop rollout, preserve the response contract, and update tests/adapter deliberately.

Examples

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

Input:

text
current=resolved-lockfile; target=95.0.0; raw-queries=4; deprecations=inventory

Expected handoff:

text
diff=reviewed; tests=required; rollout=staged; rollback=package-pin

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-upgrade-migration of jeremylongshore/tons-of-skills-marketplace.

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

Open the folder on GitHubat commit cfae287

Compare with similar skills

Linear Upgrade Migration 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 Upgrade Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Linear Upgrade Migration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.3kAutomated safety check: PassMIT
Linearletta-ai/lettabot327—~583Automated safety check: PassApache-2.0
Linear APInesszer/linear-cli138—~213Automated safety check: NotesMIT
Linearteam-mirai/mirai-gikai212—~1.9kAutomated safety check: PassAGPL-3.0
LinearRedWoodOG/Hermes-Desktop1772 repos~2.8kAutomated safety check: PassMIT
Linear CLIletta-ai/skills1491 repos~1.1kAutomated safety check: PassISC

Similar skills

  • 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

  • Linear API

    nesszer/linear-cli

    Execute raw GraphQL queries and mutations against the Linear API.

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

  • Linear

    team-mirai/mirai-gikai

    Linear と対話するためのスキル。Linear MCP サーバー（mcplinear ツール）を 優先的に使用し、MCP でカバーされない生の GraphQL 操作（イントロスペクション、 ファイルアップロードなど）は lineargraphql クライアントツールにフォールバックする。

    212 GitHub stars~1.9k tokensUpdated today
    Backend & APIsAuto-check passed

  • Linear

    RedWoodOG/Hermes-Desktop

    Manage Linear issues, projects, and teams via the GraphQL API.

    177 GitHub starsUsed in 2 repos~2.8k tokens
    Backend & APIsAuto-check passed

  • Linear CLI

    letta-ai/skills

    Manage Linear issues from the command line using the linear cli.

    149 GitHub starsUsed in 1 repo~1.1k tokens
    Backend & APIsAuto-check passed

  • Linear

    taracodlabs/aiden

    Manage Linear issues, projects, and cycles via the Linear GraphQL API

    852 GitHub stars~1k tokensUpdated 27 days ago
    Backend & APIsAuto-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 Linear Upgrade Migration

What does Linear Upgrade Migration do?

Upgrade a Linear integration across SDK releases and GraphQL deprecations with typed inventory, staged verification, and rollback. Linear Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Upgrade a Linear integration across SDK releases and GraphQL deprecations with typed inventory, staged verification, and rollback.

When should I use Linear Upgrade Migration?

Linear Upgrade Migration fits situations like: package updates; schema notices require code changes; with upgrade Linear SDK; migrate Linear API code.

How do I install Linear Upgrade Migration in Claude Code?

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

How do I install Linear Upgrade Migration in Codex?

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

Can I use Linear Upgrade Migration 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-upgrade-migration -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-upgrade-migration, .gemini/skills/linear-upgrade-migration, .github/skills/linear-upgrade-migration and .opencode/skills/linear-upgrade-migration in your project.

What does Linear Upgrade Migration need to run?

Going by SKILL.md and its folder, Linear Upgrade Migration needs credentials named API_KEY and ACCESS_TOKEN. Our summary lists: Node.js; 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 Upgrade Migration 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 Upgrade Migration 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 Upgrade Migration use?

Linear Upgrade Migration 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 Upgrade Migration use?

About 1.3k tokens (SKILL.md is roughly 5k 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 Upgrade Migration?

Skills that share tags, products or a category with Linear Upgrade Migration: Linear (letta-ai/lettabot, 327 stars), Linear API (nesszer/linear-cli, 138 stars), Linear (team-mirai/mirai-gikai, 212 stars) and Linear (RedWoodOG/Hermes-Desktop, 177 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Linear Upgrade Migration?

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.