slack-to-ticket
Skill2 starsChanged 4 months agoNo licenceView on GitHub
Create Jira tickets from Slack conversations, optionally with Confluence documentation pages. Reads Slack threads/channels/search results via slack-cli, analyzes the conversation to extract problems, participants, decisions, and action items, then creates Jira issue(s) via jira-cli with the conversation context. A single conversation may produce multiple tickets if it covers distinct topics. For long or complex conversations (>15 messages), recommends creating a Confluence documentation page via confluence-cli with a context-aware format (postmortem for bugs, PRD for features, slim summary for tasks). Supports input as Slack permalink URL, channel name, thread timestamp, or search query. Presents drafts for interactive review before creating. Trigger phrases include "slack to ticket", "slack-to-ticket", "create ticket from slack", "jira ticket from slack", "create ticket from #channel", "create ticket from thread", "slack conversation to jira", "ticket from slack thread", "jira from slack", "slack to jira", "create issue from slack".
- Installs packages
In this repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adversarial-panelSkill
- agents-initSkill
- agent-swarmSkill
- chrome-useSkill
- codex-cliSkill
- codex-serverSkill
- confluenceSkill
- deepenSkill
- dev-workflowSkill
- diagnoseSkill
- dotnet-seniorSkill
- e2e-testSkill
- en-to-ja-explainerSkill
- figma-shot-boardSkill
- gdrive-cliSkill
- grill-meSkill
- grill-to-implSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- japanese-tech-writingSkill
- jira-cliSkill
- local-skill-factorySkill
- logo-imageSkill
- my-gdriveSkill
- my-skill-factorySkill
- naturalize-jaSkill
- natural-japaneseSkill
- notion-cliSkill
- openai-cliSkill
- orch-qaSkill
- parallel-investigateSkill
- playwright-cliSkill
- pm-reviewSkill
- postmortemSkill
- prd-councilSkill
- prototypeSkill
- pr-reviewSkill
- recap-to-notionSkill
- review-localSkill
- scenario-genSkill
- self-pr-reviewSkill
- session-handoverSkill
- session-recapSkill
- session-watchSkill
- skill-improveSkill
- slack-cliSkill
- subagent-genSkill
- tddSkill
- test-scenarioSkill
- to-prdSkill
- triageSkill
- ui-spec-simSkill
- well-arch-costSkill
- well-arch-reliabilitySkill
- well-arch-securitySkill
- zoom-outSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
39 rules. About 0 are common, 24 are distinctive, and 15 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈24
Distinctive · estimate
This author's own choices. Worth a look.
15
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.