What is slack-to-ticket?

A Slack-to-Linear conversion tool that turns a pasted Slack conversation into a structured Linear issue, where Linear is a service for tracking software work.

Use it to extract the topic, urgency, and action items from a Slack thread, propose issue details, and create the issue in the selected team and project.

It saves time when an informal discussion needs to become a clear, trackable task and checks whether a similar issue already exists.

slack-to-ticket — Skill for Claude Code by mostafa-drz

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add mostafa-drz/claude-skills --skill slack-to-ticket

Clone the repo

git clone --depth 1 https://github.com/mostafa-drz/claude-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/slack-to-ticket/github.svg)](https://agentmods.dev/skills/mostafa-drz/claude-skills/slack-to-ticket)

Your own site

<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/slack-to-ticket"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/slack-to-ticket/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/slack-to-ticket"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/slack-to-ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,380 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00056	$0.01380
Opus 5	$0.00028	$0.00690
Sonnet 5	$0.00011	$0.00276
Haiku 4.5	$0.00006	$0.00138

Measured today against content hash 05414d6f863f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

slack-to-ticket scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

code/slack-to-ticket/SKILL.md · 164 lines

How it starts

The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Slack Thread → Linear Ticket

Creates a structured Linear issue from a pasted Slack conversation.

Preferences

Read ~/.claude/skills/slack-to-ticket/preferences.md using the Read tool. If not found, no preferences are set.

Command routing

Check $ARGUMENTS:

help → display help then stop
config → interactive setup then stop
reset → delete ~/.claude/skills/slack-to-ticket/preferences.md, confirm, stop
anything else → process as Slack thread

Help

Slack to Ticket — Create a Linear issue from a Slack thread

Usage:
  /slack-to-ticket <paste thread>    Parse and create issue
  /slack-to-ticket config            Set default team, project, preferences
  /slack-to-ticket reset             Clear preferences
  /slack-to-ticket help              This help

What it does:
  1. Parses the thread for topic, urgency, action items
  2. Checks Linear for duplicate issues
  3. Shows inferred fields for review
  4. Asks for team and project
  5. Creates issue with natural description

Current preferences:
  (shown above under Preferences)

Config

Use AskUserQuestion:

Q1 — "Default Linear team?" (options from list_teams, max 4, + "Ask each time") Q2 — "Default project?" (options from list_projects, max 4, + "None", + "Ask each time") Q3 — "Default priority when no urgency signals?" (Normal (default), Low, Ask each time)

Save to ~/.claude/skills/slack-to-ticket/preferences.md.

First-time detection

If no preferences file exists, show: "First time using /slack-to-ticket? Run /slack-to-ticket config to set default team/project, or continue — I'll ask as needed."

Then proceed normally.

Steps

1. Parse the Slack thread

Analyze $ARGUMENTS and extract:

Topic: Core subject being discussed
Category: Bug, Feature, Improvement, or Task
Action items: Concrete next steps mentioned or implied
Participants: Names/handles of people involved
Reporter: Who started the thread
Urgency: Map signals (urgent, blocking, ASAP, P0, deadlines) to Linear priority: Urgent (1), High (2), Normal (3), Low (4). Default from preferences or Normal (3).

Read the full file on GitHub · 164 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

today Changed · +3 lines 05414d6f863f
12d ago First seen · 161 lines · 56 tokens per session scan A 3aa2bc569af1

Subscribe to this mod's changes

slack-to-ticket is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,380 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Project management ai-tools automation claude claude-skills developer-tools

codex-symphony

Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.

citedy/skills · 61 tokens

timeline-creator

Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.

mhattingpete/claude-skills-marketplace · 47 tokens

daily-working

End-to-end pipeline: pull a task from the project's task tracker by ID (Redmine or GitHub Issues today, more addable via a new adapter), sanity-check and impact-assess it against the codebase before touching anything, implement it with the Claude CLI, verify the result in a real browser via the Claude Chrome extension…

tms-tungnguyen3/daily_working · 98 tokens

shipkit-user-instructions

Use when there are manual tasks the user must complete. Triggers: 'create task', 'track TODO', 'user needs to', 'manual step required'.

stefan-stepzero/shipkit · 38 tokens

caregiver-coordination

Analyze caregiver coordination platforms for scheduling optimization, task assignment, handoff communication, family/professional caregiver integration, care plan compliance, burnout prevention, and documentation workflows..

tinh2/skills-hub-registry · 38 tokens

disability-services

Analyze disability services software — IEP and ISP management, person-centered planning workflows, HCBS Settings Rule compliance, accommodation tracking, assistive technology integration, EVV (Electronic Visit Verification), caregiver and DSP scheduling, and outcome measurement.

tinh2/skills-hub-registry · 50 tokens