Customer support
Skill yigityildiz0/universal-ai-skill-library/skills/common/customer-support
Customer-support umbrella skill. Use when Codex should draft support replies, triage issues, summarize tickets, or prepare help content.From its SKILL.md
npx -y skills add yigityildiz0/universal-ai-skill-library --skill customer-supportAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.6 KB, 100 tokens by cl100k_base, as published. Nobody here has run it
Customer Support
Use this skill when the task is about customer resolution clarity and tone.
Workflow
- Clarify issue, urgency, and desired outcome.
- Separate diagnosis, current status, and next action.
- Route to email or reading skills when helpful.
Deliverables
- A support-ready reply or triage note.
- A short action list or FAQ update.
Guardrails
- Do not promise timelines or fixes you do not have.
- Do not flatten sensitive context.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most customer support skills give in 100 tokens
Counted across 123 of the 124 authors here whose files we hold, read 2026-08-07
- Call RUBE_SEARCH_TOOLS first to get current schemasin 12 of 123, across 4 files
- Confirm connection status is ACTIVE before running workflowsin 12 of 123, across 4 files
- Stop and ask for clarification if required inputs are missingin 9 of 123, across 2 files
- Call RUBE_MANAGE_CONNECTIONS with the helpdesk toolkitin 9 of 123, across 2 files
- Use both timestamp and ID for cursor navigationin 8 of 123, across 1 file
- Implement backoff on 429 responsesin 8 of 123, across 1 file
- Parse response data defensively with fallback patternsin 8 of 123, across 1 file
- Use this skill only when the task clearly matches the scopein 8 of 123, across 1 file
- Pass a JSON file as the positional argumentin 7 of 123, across 1 file
- Specify output format with the --format flagin 7 of 123, across 1 file
- Run health, churn, and expansion scripts togetherin 7 of 123, across 1 file
- Verify output files contain expected records before continuingin 7 of 123, across 1 file
Said here and by no other author read
- clarify issue, urgency, and desired outcome
- separate diagnosis, current status, and next action
- route to email or reading skills when helpful
- produce a support-ready reply or triage note
- produce a short action list or FAQ update
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.