ticket

Create structured Linear tickets from pipeline sessions with errors and workarounds.

1|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Soria-Inc/soria-stack --skill ticket-soria-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket
Source: https://github.com/Soria-Inc/soria-stack/tree/main/ticket
Command: npx skills add https://github.com/Soria-Inc/soria-stack --skill ticket-soria-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

File a structured Linear ticket from a pipeline session to capture context, errors, workarounds, and tool failures so engineers can act without re-discovering the problem.

Core Features & Use Cases

  • Owns all Linear writes to keep ticket quality consistent.
  • Captures session context (errors, workarounds, tool failures) and attaches it to the ticket.
  • Guides triage with environment info, reproduction steps, and links to related tickets.

Quick Start

Invoke /ticket during a session to file a Linear ticket with the collected context.

Frequently Asked Questions about ticket

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Linear ticket from a pipeline session to capture errors and context?

To create a Linear ticket from a pipeline session, invoke the ticketing workflow during ingestion or diagnosis to capture errors, workarounds, and root-cause hints directly into a structured issue.

What is the best way to file structured Linear tickets with consistent titles and priorities?

Filing structured Linear tickets with consistent titles and priorities requires a centralized ticketing workflow that owns all writes, applies duplication checks, and enforces environment capture and field completion.

Can I automatically link a new Linear ticket to related issues during root-cause diagnosis?

Yes, during root-cause diagnosis the ticketing workflow generates artifacts and automatically links the new Linear ticket to related issues to preserve context for engineers.

Does the ticketing workflow support environment capture and reproduction steps for triage?

The ticketing workflow supports triage by capturing session context, environment information, and reproduction steps, attaching them directly to the Linear ticket to guide engineering efforts.

When should I use an automated Linear ticket workflow instead of manual entry for pipeline failures?

Use an automated Linear ticket workflow for pipeline failures when you need to capture tool failures and workarounds across the ETVLR lifecycle without forcing engineers to re-discover the problem.

How do duplication checks work when filing Linear tickets from pipeline sessions?

Duplication checks work by scanning existing issues during the ticketing workflow to prevent duplicate Linear tickets and ensure new entries link to related context instead of fragmenting information.