customer-support-triage
- Repo stars 1
- Author updated Live
- Author repo claude-skills
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @00PrabalK00 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: customer-support-triage
description: Classify support requests, ask the right follow-up questions, choose the correct troubleshooting…
category: engineering
runtime: no special runtime
---
# customer-support-triage output preview
## PART A: Task fit
- Use case: Classify support requests, ask the right follow-up questions, choose the correct troubleshooting path, and draft responses in the desired support tone. Use for inbound tickets, bug reports, billing issues, account access problems, or escalation triage..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / Core Workflow / Deliver” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Classify support requests, ask the right follow-up questions, choose the correct troubleshooting path, and draft responses in the desired support tone. Use for inbound tickets, bug reports, billing issues, account access problems, or escalation triage.”.
- **02** When the source has headings, the agent prioritizes “Overview / Core Workflow / Deliver” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Overview / Core Workflow / Deliver”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: customer-support-triage
description: Classify support requests, ask the right follow-up questions, choose the correct troubleshooting…
category: engineering
source: 00PrabalK00/claude-skills
---
# customer-support-triage
## When to use
- Classify support requests, ask the right follow-up questions, choose the correct troubleshooting path, and draft respo…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Overview / Core Workflow / Deliver” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "customer-support-triage" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Overview / Core Workflow / Deliver
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Customer Support Triage
Overview
Move quickly from raw ticket to the next best customer and internal action.
Core Workflow
- Classify the issue type, urgency, severity, and whether the request is support, bug, billing, abuse, or access related.
- Extract the facts already present and identify the minimum follow-up questions needed to unblock triage.
- Choose the troubleshooting or escalation path based on risk, customer impact, and ownership.
- Draft the customer reply in the correct tone with clear next steps and realistic expectations.
- Capture internal notes, escalation reasons, and any evidence that the next team will need.
Deliver
- Provide a triage decision, the next action, and a ready-to-send response draft.
- Keep customer-facing language calm, direct, and empathetic.
- Make internal handoff notes concise but complete.
Guardrails
- Do not promise refunds, fixes, or timelines that are not authorized.
- Escalate security, safety, and account-compromise signals immediately.
- Ask only the follow-up questions that materially change the path forward.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review