linear-integration
# Linear Integration
What this skill does
# Linear Integration Use `linearis` CLI for Linear task management. Issue IDs support both UUID and identifiers like `ABC-123`. ## Quick Start ```bash linearis issues list -l 10 # Recent issues linearis issues read ABC-123 # Issue details linearis issues search "bug" # Search issues linearis issues update ABC-123 -s "In Progress" # Update status ``` ## Workflow 1. Check `linearis issues list` before starting work 2. Update issue status when you begin (`In Progress`) 3. Add comments for significant progress 4. Link PRs in comments when opening --- ## Issues ### List Issues ```bash linearis issues list [options] ``` | Option | Description | |--------|-------------| | `-l, --limit <n>` | Limit results (default: 25) | ### Read Issue ```bash linearis issues read <issueId> ``` ### Create Issue ```bash linearis issues create [options] <title> ``` | Option | Description | |--------|-------------| | `-d, --description <desc>` | Issue description | | `-a, --assignee <id>` | Assign to user ID | | `-p, --priority <1-4>` | Priority level | | `--team <team>` | Team key, name, or ID (required if not specified) | | `--project <project>` | Add to project (name or ID) | | `--labels <labels>` | Labels (comma-separated names or IDs) | | `--status <status>` | Status name or ID | | `--cycle <cycle>` | Cycle name or ID (requires --team) | | `--project-milestone <milestone>` | Project milestone (requires --project) | | `--parent-ticket <parentId>` | Parent issue ID or identifier | ### Update Issue ```bash linearis issues update [options] <issueId> ``` | Option | Description | |--------|-------------| | `-t, --title <title>` | New title | | `-d, --description <desc>` | New description | | `-s, --state <state>` | New state name or ID | | `-p, --priority <1-4>` | New priority | | `--assignee <id>` | New assignee ID | | `--project <project>` | New project (name or ID) | **Labels:** | Option | Description | |--------|-------------| | `--labels <labels>` | Labels (comma-separated names or IDs) | | `--label-by <mode>` | How to apply: `adding` (default) or `overwriting` | | `--clear-labels` | Remove all labels | **Relationships:** | Option | Description | |--------|-------------| | `--parent-ticket <id>` | Set parent issue | | `--clear-parent-ticket` | Clear parent | | `--project-milestone <milestone>` | Set milestone | | `--clear-project-milestone` | Clear milestone | | `--cycle <cycle>` | Set cycle | | `--clear-cycle` | Clear cycle | ### Search Issues ```bash linearis issues search [options] <query> ``` | Option | Description | |--------|-------------| | `--team <team>` | Filter by team | | `--assignee <id>` | Filter by assignee ID | | `--project <project>` | Filter by project | | `--states <states>` | Filter by states (comma-separated) | | `-l, --limit <n>` | Limit results (default: 10) | --- ## Comments ### Create Comment ```bash linearis comments create [options] <issueId> ``` | Option | Description | |--------|-------------| | `--body <body>` | Comment body (required) | --- ## Cycles ### List Cycles ```bash linearis cycles list [options] ``` | Option | Description | |--------|-------------| | `--team <team>` | Team key, name, or ID | | `--active` | Only active cycles | | `--around-active <n>` | Return active +/- n cycles (requires --team) | ### Read Cycle ```bash linearis cycles read [options] <cycleIdOrName> ``` | Option | Description | |--------|-------------| | `--team <team>` | Team to scope name lookup | | `--issues-first <n>` | Issues to fetch (default: 50) | --- ## Projects ### List Projects ```bash linearis projects list [options] ``` | Option | Description | |--------|-------------| | `-l, --limit <n>` | Limit results (default: 100) | --- ## Project Milestones ### List Milestones ```bash linearis project-milestones list [options] ``` | Option | Description | |--------|-------------| | `--project <project>` | Project name or ID | | `-l, --limit <n>` | Limit results (default: 50) | ### Read Milestone ```bash linearis project-milestones read [options] <milestoneIdOrName> ``` | Option | Description | |--------|-------------| | `--project <project>` | Project to scope name lookup | | `--issues-first <n>` | Issues to fetch (default: 50) | ### Create Milestone ```bash linearis project-milestones create [options] <name> ``` | Option | Description | |--------|-------------| | `--project <project>` | Project name or ID | | `-d, --description <desc>` | Milestone description | | `--target-date <date>` | Target date (YYYY-MM-DD) | ### Update Milestone ```bash linearis project-milestones update [options] <milestoneIdOrName> ``` | Option | Description | |--------|-------------| | `--project <project>` | Project to scope name lookup | | `-n, --name <name>` | New name | | `-d, --description <desc>` | New description | | `--target-date <date>` | New target date (YYYY-MM-DD) | | `--sort-order <n>` | New sort order | --- ## Labels ### List Labels ```bash linearis labels list [options] ``` | Option | Description | |--------|-------------| | `--team <team>` | Filter by team | --- ## Teams ### List Teams ```bash linearis teams list ``` --- ## Users ### List Users ```bash linearis users list [options] ``` | Option | Description | |--------|-------------| | `--active` | Only show active users | --- ## Embeds ### Download File ```bash linearis embeds download [options] <url> ``` | Option | Description | |--------|-------------| | `--output <path>` | Output file path | | `--overwrite` | Overwrite existing file |
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.