linear
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
What this skill does
# 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
```bash
./linear <resource> <action> [arguments] [options]
```
Resources: `issue`, `user`, `team`, `project`
## Commands
### List Users
```bash
./linear user list
```
Returns: `#<user-id> <name> <email>`
### List Teams
```bash
./linear team list
```
Returns: `#<team-id> <name> <key>`
### List Projects
```bash
./linear project list
```
Returns: `#<project-id> <name> <state>`
### List Issues
```bash
./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:**
```bash
./linear issue list --team abc123 --limit 10
./linear issue list --assignee def456 --status "In Progress"
```
### View Issue
```bash
./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
```bash
./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:**
```bash
./linear issue create "Fix login bug" --team abc123 --priority 2
```
### Add Comment
```bash
./linear issue comment <id-or-key> <text>
```
Multi-word text auto-combined. No quotes needed.
### Update Issue
```bash
./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:**
```bash
./linear issue update ENG-123 --status "In Progress" --assignee abc123
```
### Delete Issue
```bash
./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 `--json` flag for machine-readable output
- Use `--help` on any command for details
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess 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.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.