Individual skill
ticket-triage
Triage and prioritize a support ticket or customer issue. Use when a new ticket comes in and needs categorization, assigning P1-P4 priority, deciding which team should handle it, or checking whether it's a duplicate or known issue before routing.
marketing/ticket-triage/SKILL.md
Source commit cbab58188611e626ccaf54ac346b437d12ea4729
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 207
- Repository last updated
- Sep 26, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- codex-skills Repository topic
- deepseek Repository topic
- deepseek-harness Repository topic
- marketing-automation Repository topic
- research-tools Repository topic
- claude-code Repository topic
- cursor-ai Repository topic
- gemini-cli Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 12,389 bytesSKILL.mdcore · 12,389 bytesreferences/sandbase-api-map.mddoc · 1,012 bytes
Read excerpt
# /ticket-triage
> Use only support, knowledge-base, and project-tracker sources that are actually available and authorized in the host. State clearly when a source was not checked.
Categorize, prioritize, and route an incoming support ticket or customer issue. Produces a structured triage assessment with a suggested initial response.
When checking public documentation or known-issue evidence, read [the SandBase API map](references/sandbase-api-map.md). Resolve the listed capability with `sandbase_discover`, inspect its returned `name` with `sandbase_inspect`, then follow `execute_as` to call `sandbase_run(name: "<returned name>", arguments: { ... })` using only the current schema. For async results, poll `sandbase_run_get` with the returned `run_id` within the task budget; report pending or failed runs without automatically resubmitting them.
## Usage
```
/ticket-triage <ticket text, customer message, or issue description>
```