Agent skill · Audited from source
support-ticket-triage
skill · composiohq/awesome-codex-skillsLicence not declaredAudited 14 Nov 2026 · source f10a5237c0bd
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit f10a5237c0bd and found no filesystem, network or shell access and no hard-coded secrets. What it does: Triage customer support tickets/emails/chats into categories, priority, and next action; draft responses and create reproducible steps; use for Zendesk/Intercom/Help Scout exports or pasted threads.
Cite
Cite this page
ModelsAtlas. “support-ticket-triage (composiohq/awesome-codex-skills)”. Retrieved 14 Nov 2026. https://modelsatlas.com/skills/composiohq/support-ticket-triage
Trust audit
Audit 0.4.1 · source read 14 Nov 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha f10a5237c0bd · 14 Nov 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publishercomposiohq GitHub organizationOwner of the repository this skill is read from
- Source foldercomposiohq/awesome-codex-skills/support-ticket-triageThe exact folder we audited
- LicenceNot declaredAs the repository states it
- Commit pinned for this verdictf10a5237c0bdA new audit runs when the source changes
- Repository statusNot archivedLast push 111 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Triage customer support tickets/emails/chats into categories, priority, and next action; draft responses and create reproducible steps; use for Zendesk/Intercom/Help Scout exports or pasted threads.
--- name: support-ticket-triage description: Triage customer support tickets/emails/chats into categories, priority, and next action; draft responses and create reproducible steps; use for Zendesk/Intercom/Help Scout exports or pasted threads. metadata: short-description: Categorize and respond to support tickets --- # Support Ticket Triage Standardize how to classify and respond to incoming tickets. ## Inputs to gather - Ticket text (include attachments/links), product area, customer plan/tier if known. - Desired outputs: category taxonomy, priority levels, SLA hints, tone/brand voice, whether to draft a reply. ## Workflow 1) Parse context: identify issue type, product surface, severity, customer impact, reproduction hints, and blockers. 2) Categorize: assign category and subcategory; set priority (e.g., P0–P3) with short justification. 3) Draft response (if asked): concise acknowledgment, empathy, restate issue, next steps, and ask for missing info; include reproduction checklist when uncertain. 4) Internal notes: suspected root cause, logs to pull, teams to loop, and tracking IDs to create/attach. 5) Output: tabular or bullet summary with `Category`, `Priority`, `Summary`, `Proposed Fix/Next Steps`, `Reply Draft`. ## Quality checks - Avoid promises; give ranges not exact ETAs unless provided. - Mask PII if copying to public channels. - If signal is weak, present 2–3 likely categories and what evidence would disambiguate.
Excerpt, first 1,454 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit f10a523
git clone https://github.com/composiohq/awesome-codex-skills git -C awesome-codex-skills checkout f10a5237c0bd
The author documents no install command, so this uses the repository directly. Our verdict covers commit f10a5237c0bd only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
f10a5237c0bd
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/composiohq/support-ticket-triage/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
All coding & review skills →composiohq/awesome-codex-skills
Write and debug spreadsheet formulas (Excel/Google Sheets), pivot tables, and array formulas; translate between dialects; use when users need working formulas with examples and edge-case checks.
composiohq/awesome-codex-skills
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private…
composiohq/awesome-codex-skills
Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
composiohq/awesome-codex-skills
Generate PPTX presentations, DOCX documents, XLSX spreadsheets, and PDF reports from structured JSON input using PaperJSX.
composiohq/awesome-codex-skills
Automated PR review and CI auto-fix for GitHub and GitLab using the Composio CLI. Pulls diffs, fetches failing job logs, posts review comments, and loops fix commits until checks go green.
composiohq/awesome-codex-skills
Diagnose Sentry issues without copy-pasting stack traces. Uses the Composio CLI to pull issue details, events, breadcrumbs, and suspect commits, then maps the frames to local source so the agent can propose a fix…
Add this badge to your README
[](https://modelsatlas.com/skills/composiohq/support-ticket-triage/)
<a href="https://modelsatlas.com/skills/composiohq/support-ticket-triage/"><img src="https://modelsatlas.com/skills/composiohq/support-ticket-triage/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about support-ticket-triage
What does the support-ticket-triage skill do?
Is support-ticket-triage safe to install?
What can support-ticket-triage access on my machine?
How current is this page?
Sources
- github.com/composiohq/awesome-codex-skills/tree/master/support-t — the audited source at commit f10a5237c0bd and every finding aboveObserved · 14 Nov 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the support-ticket-triage skill do?
- Is support-ticket-triage safe to install?
- What can support-ticket-triage access on my machine?