linear
Before using Linear workflows, search for linear MCP tools. If not found, treat as not installed.
Works with
0
total installs
0
this week
74.8K
GitHub stars
0
upvotes
Install Skill
Run in your terminal
0
installs
0
this week
74.8K
stars
Installation Guide
How to use linear on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
linear
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches linear from lobehub/lobe-chat and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate linear. Access via /linear 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.
Documentation
Linear Issue Management
Before using Linear workflows, search for linear MCP tools. If not found, treat as not installed.
⚠️ CRITICAL: PR Creation with Linear Issues
When creating a PR that references Linear issues (LOBE-xxx), you MUST:
- Create the PR with magic keywords (
Fixes LOBE-xxx) - IMMEDIATELY after PR creation, add completion comments to ALL referenced Linear issues
- Do NOT consider the task complete until Linear comments are added
This is NON-NEGOTIABLE. Skipping Linear comments is a workflow violation.
Workflow
- Retrieve issue details before starting:
mcp__linear-server__get_issue - Check for sub-issues: Use
mcp__linear-server__list_issueswithparentIdfilter - Update issue status when completing:
mcp__linear-server__update_issue - Add completion comment (REQUIRED):
mcp__linear-server__create_comment
Creating Issues
When creating issues with mcp__linear-server__create_issue, MUST add the claude code label.
Completion Comment Format
Every completed issue MUST have a comment summarizing work done:
## Changes Summary
- **Feature**: Brief description of what was implemented
- **Files Changed**: List key files modified
- **PR**: #xxx or PR URL
### Key Changes
- Change 1
- Change 2
- ...
This is critical for:
- Team visibility
- Code review context
- Future reference
PR Association (REQUIRED)
When creating PRs for Linear issues, include magic keywords in PR body:
Fixes LOBE-123Closes LOBE-123Resolves LOBE-123
Per-Issue Completion Rule
When working on multiple issues, update EACH issue IMMEDIATELY after completing it:
- Complete implementation
- Run
bun run type-check - Run related tests
- Create PR if needed
- Update status to "In Review" (NOT "Done")
- Add completion comment immediately
- Move to next issue
Note: Status → "In Review" when PR created. "Done" only after PR merged.
❌ Wrong: Complete all → Create PR → Forget Linear comments
✅ Correct: Complete → Create PR → Add Linear comments → Task done
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
388mattpocock/skills
premortem
197parcadei/continuous-claude-v3
deslop
118cursor/plugins
framer-motion
99pproenca/dot-skills
write-a-prd
91mattpocock/skills
travel-planner
90ailabs-393/ai-labs-claude-skills
Reviews
- EEmma Sethi★★★★★Dec 12, 2024
linear reduced setup friction for our internal harness; good balance of opinion and flexibility.
- LLiam Patel★★★★★Dec 4, 2024
Registry listing for linear matched our evaluation — installs cleanly and behaves as described in the markdown.
- LLiam Rao★★★★★Nov 27, 2024
linear is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- XXiao Okafor★★★★★Nov 23, 2024
Useful defaults in linear — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- EEmma Iyer★★★★★Nov 3, 2024
I recommend linear for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- DDiya Chen★★★★★Oct 22, 2024
Useful defaults in linear — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- AAditi Diallo★★★★★Oct 18, 2024
Keeps context tight: linear is the kind of skill you can hand to a new teammate without a long onboarding doc.
- AAditi Abebe★★★★★Oct 14, 2024
I recommend linear for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- OOshnikdeep★★★★★Sep 21, 2024
linear has been reliable in day-to-day use. Documentation quality is above average for community skills.
- EEvelyn Martinez★★★★★Sep 17, 2024
linear fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 44
Discussion
Comments — not star reviews- No comments yet — start the thread.