SkillA skill gives Relay a specialist method it can reuse on your work.Operations and financeCommunity
Low riskSecurity review passed

to-tickets

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker.

How it works

What to-tickets does

Edges as text in one file per ticket locally, or native blocking links on a real tracker.

Inputs and results

What goes in, what comes back

  1. You give

    A short brief describing what you need

    Add a specialist method to the work.

  2. You get

    A finished result to review

    The method guides the work with your files and context.

  3. You check

    The sources and open questions

    Review the output against your brief.

Questions and answers

Questions about to-tickets

Updated Aug 27, 2026.

What does to-tickets do?

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

Who is to-tickets for?

It is designed for teams that want to hand off recurring work and review the result before it is used.

What do I need to use it?

Nothing extra is needed. Sign in to Relay to run it with your own files and context.

What does to-tickets produce?

A finished result to review. Results come back with their sources and any open questions for you to check before anything is used.

How much does to-tickets cost?

It is free to use. Paid model usage, if any, is shown before a run.

Can an AI agent use it?

Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.

Details

Trust, access and technical details

Trust and access

Visibility
Public: anyone can view
Status
Published and maintained
Pricing
Free
Low riskSecurity review passedBehavior not evaluated
Reviewed version
cmtas2ua70098…
Reviewed
Aug 27, 2026
Static signals
0 signals
Source provenance
Commit pinned

Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.

Use it from code or an agent

Read the public definition, then check cost and inputs with a preflight before a run.

Open definition

POST /api/v1/runs/preflight

How agents connect to Relay →

Tags and source

Repo
mattpocock/skills
License
MIT

Have a task this would help with?

Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.

Loading request box