Agent skill · writing content · jeremylongshore
linear-migration-deep-dive
Plan and execute a controlled migration into Linear using supported import assistants or the CLI importer. Use when moving issues from Jira, GitHub, Asana, Shortcut, another Linear workspace, or CSV. Trigger with "migrate to Linear", "import issues into Linear", or "plan Linear cutover".
Why this skill is useful
Provides detailed migration workflows and scripts for transferring data from popular issue tracking tools to Linear, which the AI wouldn't reliably generate on its own.
What it needs
Requires bash installed locally. Requires asana, github, jira, linear account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Linear Workspace Data Migration Overview Choose the supported importer that preserves the required data, pilot a bounded team, and prove mappings and rollback before cutover. 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 Imports require a workspace admin; dedicated import assistants are preferred because they retain more source data and can support bulk deletion for a limited time. The CLI importer is for sources without a dedicated assistant and does not preserve all data such as comments or projects. Re-importing the same source into the same team skips already-imported issues unless the prior import is deleted first. 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: <APIKEY>; OAuth tokens use Authorization: Bearer <ACCESSTOKEN>. 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. Inventory source entities, volumes, users, teams, statuses, labels, projects, comments, attachments, timestamps, and compliance constraints. 2. Choose a dedicated assistant when available; use the CLI only after documenting the data it cannot preserve. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-migration-deep-dive--a58345