Agent skill · data analytics · n8n-io
n8n:linear-issue
Fetch and analyze Linear issue with all related context. Use when starting work on a Linear ticket, analyzing issues, or gathering context about a Linear issue.
Why this skill is useful
Adds specific commands and workflows for fetching and analyzing Linear issues that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, gh installed locally. Requires linear account access. About 7k tokens when loaded. Last updated 2026-08-07. 199,638 stars on the source repository.
What this skill does
Linear Issue Analysis Start work on Linear issue $ARGUMENTS Prerequisites This skill depends on external tools. Before proceeding, verify availability: Required: Linear MCP: Must be connected. Without it the skill cannot function at all. GitHub CLI (gh): Must be installed and authenticated. Run gh auth status to verify. Used to fetch linked PRs and issues. Optional (graceful degradation): Notion MCP: Needed only if the issue links to Notion docs. If unavailable, note the Notion links in the summary and tell the user to check them manually. Loom transcript skill: Needed only if the issue contains Loom videos. If unavailable, note the Loom links in the summary for the user to watch. curl: Used to download images. Almost always available; if missing, skip image downloads and note it. If a required tool is missing, stop and tell the user what needs to be set up before continuing. Instructions Follow these steps to gather comprehensive context about the issue: 1. Fetch the Issue and Comments from Linear Use the Linear MCP tools available in the active harness to fetch the issue details and comments together: Fetch the issue by ID to get full details including attachments Include relations to see blocking/related/duplicate issues Immediately after, fetch all comments for the issue ID Both calls should be made together in the same step to gather the complete context upfront. 2. Check for Private/Security Issues (MANDATORY — do this before anything else) After fetching the issue, immediately check its labels: 1. Look at the labels returned with the issue. 2. If any label is n8n-private: a. Run git remote -v (via Bash) to list all configured remotes. b. If any remote URL contains n8n-io/n8n without the -private suffix (i.e. matches the public repo), stop immediately and tell the user: This issue is marked n8n-private and must be developed in a clean clone of the private repository. One or more of your remotes point to the public n8n-io/n8n repo. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills n8n-io/linear-issue