Fetches linear-claude-skill from sickn33/antigravity-awesome-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/linear-claude-skill
Restart Cursor to activate linear-claude-skill. Access via /linear-claude-skill in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Use this skill when working with manage linear issues, projects, and teams.
Linear
Tools and workflows for managing issues, projects, and teams in Linear.
⚠️ Tool Availability (READ FIRST)
This skill supports multiple tool backends. Use whichever is available:
MCP Tools (mcp__linear) - Use if available in your tool set
Linear CLI (linear command) - Always available via Bash
Helper Scripts - For complex operations
If MCP tools are NOT available, use the Linear CLI via Bash:
# View an issuelinear issues view ENG-123
# Create an issuelinear issues create --title"Issue title"--description"Description"# Update issue status (get state IDs first)linear issues update ENG-123 -s"STATE_ID"# Add a commentlinear issues comment add ENG-123 -m"Comment text"# List issueslinear issues list
Do NOT report "MCP tools not available" as a blocker - use CLI instead.
When to Use This Skill
Manage Linear issues, projects, and teams
Use this skill when working with manage linear issues, projects, and teams.
🔐 Security: Varlock Integration
CRITICAL: Never expose API keys in terminal output or Claude's context.
Safe Commands (Always Use)
# Validate LINEAR_API_KEY is set (masked output)varlock load 2>&1|grep LINEAR
# Run commands with secrets injectedvarlock run -- npx tsx scripts/query.ts "query { viewer { name } }"# Check schema (safe - no values)cat .env.schema |grep LINEAR
Unsafe Commands (NEVER Use)
# ❌ NEVER - exposes key to Claude's contextlinear config show
echo$LINEAR_API_KEYprintenv|grep LINEAR
cat .env
Go to Settings (gear icon) -> Security & access -> Personal API keys
Click Create key and copy the key (starts with lin_api_)
Add to your environment:
# Option A: Add to shell profile (~/.zshrc or ~/.bashrc)exportLINEAR_API_KEY="lin_api_your_key_here"# Option B: Add to Claude Code environmentecho'LINEAR_API_KEY=lin_api_your_key_here'>> ~/.claude/.env
# Then reload your shell or restart Claude Code
3. Test Connection
Verify everything works:
npx tsx ~/.claude/skills/linear/scripts/query.ts "query { viewer { name } }"
You should see your name from Linear.
4. Common Operations
# Create issue in a projectnpx tsx scripts/linear-ops.ts create-issue "Project""Title""Description"# Update issue statusnpx tsx scripts/linear-ops.ts status Done ENG-123 ENG-124
# Create sub-issuenpx tsx scripts/linear-ops.ts create-sub-issue ENG-100 "Sub-task""Details"# Update project statusnpx tsx scripts/linear-ops.ts project-status "Phase 1" completed
# Show all commandsnpx tsx scripts/linear-ops.ts help
Use this skill when working with manage linear issues, projects, and teams.
Project Planning Workflow
Create Issues in the Correct Project from the Start
Best Practice: When planning a new phase or initiative, create the project and its issues together in a single planning session. Avoid creating issues in a catch-all project and moving them later.
WARNING: Do NOT use deprecated community servers. See troubleshooting.md for details.
MCP Reliability (Official Server)
Operation
Reliability
Notes
Create issue
✅ High
Full support
Update status
✅ High
Use state: "Done" directly
List/Search issues
✅ High
Supports filters, queries
Add comment
✅ High
Works with issue IDs
Quick Status Update
# Via MCP - use human-readable state namesupdate_issue with id="issue-uuid", state="Done"# Via helper script (bulk operations)node scripts/linear-helpers.mjs update-status Done 123124125
Helper Script Reference
For detailed helper script usage, see troubleshooting.md.
Parallel Agent Execution
For bulk operations or background execution, use the Linear-specialist subagent:
Implementation Guide
Prerequisites
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
