n8n:create issue

Engineering Community

Skill notes

Determine Target

Decide where the issue should be created based on user input: If the user says "Linear", "ticket", or provides a team key (e.g., AI, NODE, N8N) → Linear If the user says "GitHub", "GH issue", or "open source" → GitHub If ambiguous, ask the user which platform they want

Prerequisites

Verify the Linear MCP is connected before proceeding.

Style Guide

Title Sentence case — capitalize only the first word (e.g., "Add webhook verification to Trello trigger") Descriptive — a reader should understand the scope without opening the ticket 5–15 words — long enough to be specific, short enough to scan Imperative mood for features/enhancements — "Add ...", "Support ...", "Improve ..."

Creating the Ticket

Gather required fields — if any are missing, ask the user: Title Team Description (draft one from the user's input using the templates above) Present a preview before creating — show the user:

Things to Never Do (Linear)

Never create issues in Triage status Never set Urgent priority without explicit user instruction Never apply triage-state, release, or docs-automation labels Never set assignee unless the user explicitly asks Never set a cycle or milestone unless the user explicitly asks

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@n8n-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview n8n-create-issue.preview
# Expected output

- **URLs** — embed directly in the description using markdown image syntax (`![description](url)`)
- **File paths** — if the user provides a local file path, ask them to upload it to a hosting service (e.g., GitHub, Imgur) or use `mcp__linear-server__create_attachment` to attach it to the Linear ticket after creation
- **Pasted images in conversation** — describe what the image shows in the ticket description and note that a screenshot was provided. You cannot upload binary data directly.
- **Default to Normal (3)** unless the user explicitly states otherwise
- **Never set Urgent (1)** unless the user explicitly says "urgent", "P0", "production down", or "security vulnerability"
- **Never set None (0)** — always make a priority assessment. If unsure, use Normal (3)

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.