Siftrank
noperator/siftrank
Find needles in haystacks with SiftRank. An agent skill from noperator/siftrank.
How to pick the owning team and the priority for an inbound support ticket, including what to do when a ticket spans two teams.
Install Ticket Routing Playbook
$ npx skills add Kiln-AI/Kiln --skill ticket-routing-playbook -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Kiln-AI/Kiln ticket-routing-playbook --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Kiln-AI/Kiln.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'.agents/playwright_project/skills/255490964102 - ticket-routing-playbook' .claude/skills/ticket-routing-playbook && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ticket-routing-playbook" agent skill from https://github.com/Kiln-AI/Kiln/tree/main/.agents/playwright_project/skills/255490964102%20-%20ticket-routing-playbook into .claude/skills/ticket-routing-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ticket-routing-playbook", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Kiln-AI/Kiln/tree/main/.agents/playwright_project/skills/255490964102%20-%20ticket-routing-playbookType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Kiln-AI/Kiln --skill ticket-routing-playbook -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Kiln-AI/Kiln ticket-routing-playbook --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Kiln-AI/Kiln.git skills-src && mkdir -p .agents/skills && cp -r skills-src/'.agents/playwright_project/skills/255490964102 - ticket-routing-playbook' .agents/skills/ticket-routing-playbook && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ticket-routing-playbook" agent skill from https://github.com/Kiln-AI/Kiln/tree/main/.agents/playwright_project/skills/255490964102%20-%20ticket-routing-playbook into .agents/skills/ticket-routing-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ticket-routing-playbook", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Kiln-AI/Kiln --skill ticket-routing-playbook -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Kiln-AI/Kiln ticket-routing-playbook --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Kiln-AI/Kiln.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/'.agents/playwright_project/skills/255490964102 - ticket-routing-playbook' .cursor/skills/ticket-routing-playbook && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ticket-routing-playbook" agent skill from https://github.com/Kiln-AI/Kiln/tree/main/.agents/playwright_project/skills/255490964102%20-%20ticket-routing-playbook into .cursor/skills/ticket-routing-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ticket-routing-playbook", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Kiln-AI/Kiln.git --path '.agents/playwright_project/skills/255490964102 - ticket-routing-playbook'--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Kiln-AI/Kiln --skill ticket-routing-playbook -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Kiln-AI/Kiln ticket-routing-playbook --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Kiln-AI/Kiln.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/'.agents/playwright_project/skills/255490964102 - ticket-routing-playbook' .gemini/skills/ticket-routing-playbook && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ticket-routing-playbook" agent skill from https://github.com/Kiln-AI/Kiln/tree/main/.agents/playwright_project/skills/255490964102%20-%20ticket-routing-playbook into .gemini/skills/ticket-routing-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ticket-routing-playbook", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Kiln-AI/Kiln ticket-routing-playbookInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Kiln-AI/Kiln --skill ticket-routing-playbook -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Kiln-AI/Kiln.git skills-src && mkdir -p .github/skills && cp -r skills-src/'.agents/playwright_project/skills/255490964102 - ticket-routing-playbook' .github/skills/ticket-routing-playbook && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ticket-routing-playbook" agent skill from https://github.com/Kiln-AI/Kiln/tree/main/.agents/playwright_project/skills/255490964102%20-%20ticket-routing-playbook into .github/skills/ticket-routing-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ticket-routing-playbook", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Kiln-AI/Kiln --skill ticket-routing-playbook -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Kiln-AI/Kiln ticket-routing-playbook --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Kiln-AI/Kiln.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/'.agents/playwright_project/skills/255490964102 - ticket-routing-playbook' .opencode/skills/ticket-routing-playbook && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ticket-routing-playbook" agent skill from https://github.com/Kiln-AI/Kiln/tree/main/.agents/playwright_project/skills/255490964102%20-%20ticket-routing-playbook into .opencode/skills/ticket-routing-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ticket-routing-playbook", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ticket-routing-playbook- GitHub stars
- 5.2k
- Token cost
- ~425 tokens
- SKILL.md length
- 222 words
- Files
- 2
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
How to pick the owning team and the priority for an inbound support ticket, including what to do when a ticket spans two teams.
- Triaging a ticket
- SKILL.md covers Teams, Priority and Summaries
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Customer support
What it does
Ticket Routing Playbook is an agent skill from Kiln-AI/Kiln. How to pick the owning team and the priority for an inbound support ticket, including what to do when a ticket spans two teams. Use when triaging a ticket.
Its SKILL.md is about 430 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.
It sits in Sales & Support, covering Customer support. The repository describes itself as: Build, Evaluate, and Optimize AI Systems. Includes evals, RAG, agents, fine-tuning, synthetic data generation, dataset management, MCP, and more.
When your agent uses it
- Triaging a ticket
- Tasks that involve Customer support
Example prompts
- “/ticket-routing-playbook”
What it can do on your machine
Read from SKILL.md and the folder at commit 8ac9075. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ticket Routing Playbook loads about 425 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 222 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 222 words (~425 tokens).
“Use this skill whenever you are deciding which team owns an inbound support ticket, or what its priority should be.”
- name
- ticket-routing-playbook
Files
SKILL.md and 1 other file in .agents/playwright_project/skills/255490964102 - ticket-routing-playbook of Kiln-AI/Kiln.
- SKILL.md
- skill.kiln
Open the folder on GitHubat commit 8ac9075
Compare with similar skills
Ticket Routing Playbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ticket Routing Playbook this skillKiln-AI/Kiln | 5.2k | — | ~425 | Automated safety check: Pass | Custom licence | |
| Siftranknoperator/siftrank | 225 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Supporthaacked/dotfiles | 134 | — | ~2.9k | Automated safety check: Pass | None | |
| Customer Support Agentmastra-ai/mastra | 29k | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Ticket TriageBevel-Software/Hexis | 100 | 1 repos | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Add Agent Adaptersafedep/gryph | 172 | — | ~679 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Support
haacked/dotfiles
Support hero workflow — start a ticket investigation with auto-organized notes, find existing notes, or generate the weekly highlights log.
Customer Support Agent
mastra-ai/mastra
Authoring playbook for building agents that triage and reply to customer messages — support tickets, email inquiries, chat questions, refund requests, or product issues.
Ticket Triage
Bevel-Software/Hexis
Triage and prioritize a support ticket or customer issue. An agent skill from Bevel-Software/Hexis.
Add Agent Adapter
safedep/gryph
A skill your agent uses when adding support for a new AI coding agent to Gryph, or when changing how an existing agent adapter is wired.
Agent Support Matrix
jazzyalex/agent-sessions
Maintain Agent Sessions agent support matrix and JSON/JSONL parsing compatibility.
More from Kiln-AI/Kiln
All 14 skills in this repoKiln Check Deprecation
Kiln-AI/Kiln
Check Kiln's model list for deprecated or sunset models across all providers.
Kiln Check Finetune Deprecation
Kiln-AI/Kiln
Check Kiln's fine-tunable model list for deprecated or unsupported base models.
Release Digest
Kiln-AI/Kiln
Post a "what's changed since the last release" recap to the release Slack channel for final QA.
Kiln Conventions
Kiln-AI/Kiln
Kiln's code conventions and per-area gotchas, plus a diff gate that enforces the mechanical ones.
Playwright
Kiln-AI/Kiln
Look at Kiln's UI in a real browser, and run its end-to-end tests.
Open PR
Kiln-AI/Kiln
Open a pull request on the Kiln repo for a human to complete.
Related
Categories
Questions about Ticket Routing Playbook
What does Ticket Routing Playbook do?
How to pick the owning team and the priority for an inbound support ticket, including what to do when a ticket spans two teams. Ticket Routing Playbook is an agent skill from Kiln-AI/Kiln. How to pick the owning team and the priority for an inbound support ticket, including what to do when a ticket spans two teams.
When should I use Ticket Routing Playbook?
Ticket Routing Playbook fits situations like: triaging a ticket; tasks that involve Customer support.
How do I install Ticket Routing Playbook in Claude Code?
Run `npx skills add Kiln-AI/Kiln --skill ticket-routing-playbook -a claude-code`. Or copy the skill folder (.agents/playwright_project/skills/255490964102 - ticket-routing-playbook in Kiln-AI/Kiln) into .claude/skills/ticket-routing-playbook in your project. Claude Code loads it when a task matches its description.
How do I install Ticket Routing Playbook in Codex?
Run `npx skills add Kiln-AI/Kiln --skill ticket-routing-playbook -a codex`. Or copy the skill folder (.agents/playwright_project/skills/255490964102 - ticket-routing-playbook in Kiln-AI/Kiln) into .agents/skills/ticket-routing-playbook in your project. Codex loads it when a task matches its description.
Can I use Ticket Routing Playbook in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Kiln-AI/Kiln --skill ticket-routing-playbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ticket-routing-playbook, .gemini/skills/ticket-routing-playbook, .github/skills/ticket-routing-playbook and .opencode/skills/ticket-routing-playbook in your project.
What does Ticket Routing Playbook need to run?
SKILL.md names no scripts, command-line tools or credentials: Ticket Routing Playbook is instructions for the agent only.
Does Ticket Routing Playbook access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ticket Routing Playbook safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ticket Routing Playbook use?
Ticket Routing Playbook has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Ticket Routing Playbook use?
About 425 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ticket Routing Playbook?
Skills that share tags, products or a category with Ticket Routing Playbook: Siftrank (noperator/siftrank, 225 stars), Support (haacked/dotfiles, 134 stars), Customer Support Agent (mastra-ai/mastra, 29k stars) and Ticket Triage (Bevel-Software/Hexis, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ticket Routing Playbook?
Kiln-AI (a GitHub organization) maintains it in Kiln-AI/Kiln, which has 5,181 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 9, 2026.
Source: Kiln-AI/Kiln on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.