Agent skill · data analytics · jeremylongshore
linear-data-handling
Classify, minimize, export, retain, and delete Linear-derived data with workspace visibility intact. Use when handling issue content, comments, attachments, audit records, exports, or analytics copies. Trigger with "handle Linear data safely", "export Linear records", or "set Linear retention".
Why this skill is useful
Provides specific patterns and code examples for data synchronization and consistency with Linear that the AI wouldn't reliably generate on its own.
What it needs
Requires @linear/sdk installed locally. Requires 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 Data Handling and Export Safety Overview Preserve Linear's team and workspace access boundaries when data leaves the product, and minimize replicated content to the stated purpose. 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 Images and other assets may require authentication; external displays should download and self-host approved assets instead of leaking authenticated URLs. Workspace CSV exports are admin-controlled, owner-only on Enterprise, recorded in the audit log, and delivered through a link that expires after 12 hours. Issue-view CSV limits and role permissions differ; attachment files are not included even when links appear in descriptions. 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 data classes, sources, destinations, fields, team visibility, recipients, retention, and deletion owners. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-data-handling