eric861129/linear
public/SKILLS/Collaboration & Project Management/linear-cli-skill/SKILL.md
Work with Linear issues via CLI - use this skill whenever the user asks about Linear issues, creating, updating, commenting on, or deleting issues, or checking issue status and details
$ install --global
skillsauthnpx skillsauth add eric861129/skills_all-in-one linearInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 4, 2026, 7:37 PM4.1s4 files scanned
SKILL.md
- name:
- linear
- description:
- Work with Linear issues via CLI - use this skill whenever the user asks about Linear issues, creating, updating, commenting on, or deleting issues, or checking issue status and details
- version:
- 0.1.0
Linear Issue Management
Use this skill whenever the user mentions Linear or asks to work with issues.
Lightweight CLI to interact with Linear's issue tracking system. All commands run from the skill directory using ./linear.
Setup
Dependencies install automatically on first run. API key errors are self-explanatory.
Command Pattern
./linear <resource> <action> [arguments] [options]
Resources: issue, user, team, project
Commands
List Users
./linear user list
Returns: #<user-id> <name> <email>
List Teams
./linear team list
Returns: #<team-id> <name> <key>
List Projects
./linear project list
Returns: #<project-id> <name> <state>
List Issues
./linear issue list [options]
Options:
--team <id>- Filter by team ID--assignee <id>- Filter by user ID--status <name>- Filter by status name (case-sensitive)--limit <n>- Limit results (default: 50)
Returns: #<identifier> <title> <status> <assignee>
Examples:
./linear issue list --team abc123 --limit 10
./linear issue list --assignee def456 --status "In Progress"
View Issue
./linear issue view <id-or-key>
Arguments:
<id-or-key>- Issue identifier (e.g.,ENG-123) or UUID
Returns full issue details including title, status, assignee, team, priority, labels, dates, description, and comments.
Create Issue
./linear issue create <title> [options]
Arguments:
<title>- Issue title (multi-word titles auto-combined)
Options:
--team <id>- Team ID (required)--description <text>- Issue description--assignee <id>- User ID--priority <n>- Priority (0=None, 1=Urgent, 2=High, 3=Medium, 4=Low)--status <name>- Initial status
Example:
./linear issue create "Fix login bug" --team abc123 --priority 2
Add Comment
./linear issue comment <id-or-key> <text>
Multi-word text auto-combined. No quotes needed.
Update Issue
./linear issue update <id-or-key> [options]
Options:
--status <name>- Update status--assignee <id>- Update assignee--priority <n>- Update priority--title <text>- Update title--description <text>- Update description
Can update multiple fields in one command.
Example:
./linear issue update ENG-123 --status "In Progress" --assignee abc123
Delete Issue
./linear issue delete <id-or-key>
Soft delete (moves to trash, recoverable).
Important Notes
- Issue identifiers are case-insensitive (
ENG-123=eng-123) - Status names are case-sensitive ("In Progress" ≠ "in progress")
- User/team IDs are UUIDs (get from list commands)
- Issue keys format:
<TEAM_KEY>-<NUMBER>(e.g., ENG-123) - All commands support
--jsonflag for machine-readable output - Use
--helpon any command for details
Related Skills
eric861129/what-if-oracle
development
VerifiedTrustedCommunity
Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like "what if...", "what would happen if...", "what are the possibilities", "explore scenarios", "scenario analysis", "possibility space", "what could go wrong", "best case / worst case", "risk analysis", "contingency planning", "strategic options", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.
38SKILL.mdUpdated Apr 4, 2026
eric861129/venue-templates
development
VerifiedTrustedCommunity
Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
38SKILL.mdUpdated Apr 4, 2026
eric861129/the-fool
development
VerifiedTrustedCommunity
Use when challenging ideas, plans, decisions, or proposals using structured critical reasoning. Invoke to play devil's advocate, run a pre-mortem, red team, or audit evidence and assumptions.
38SKILL.mdUpdated Apr 4, 2026
eric861129/scientific-writing
tools
VerifiedTrustedCommunity
Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research-lookup then (2) convert to flowing prose. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), for research papers and journal submissions.
38SKILL.mdUpdated Apr 4, 2026