Experience Portal Create
forcedotcom/sf-skills
Create / provision / set up a NEW Digital Experience (Communities) / Experience Cloud site — employee service, IT support, help desk, HR, customer, and partner portals — via the headless-360 MCP…
Triage support tickets by pulling helpdesk context, searching issue trackers and knowledge bases in parallel, classifying the issue, and giving reps a recommended next action.
Install Support Ticket Triage
$ npx skills add zapier/gtm-cheat-codes --skill support-ticket-triage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zapier/gtm-cheat-codes support-ticket-triage --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/zapier/gtm-cheat-codes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/customer-support/support-ticket-triage .claude/skills/support-ticket-triage && 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 "support-ticket-triage" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/customer-support/support-ticket-triage into .claude/skills/support-ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "support-ticket-triage", 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/zapier/gtm-cheat-codes/tree/main/skills/customer-support/support-ticket-triageType 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 zapier/gtm-cheat-codes --skill support-ticket-triage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zapier/gtm-cheat-codes support-ticket-triage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/customer-support/support-ticket-triage .agents/skills/support-ticket-triage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "support-ticket-triage" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/customer-support/support-ticket-triage into .agents/skills/support-ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "support-ticket-triage", 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 zapier/gtm-cheat-codes --skill support-ticket-triage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zapier/gtm-cheat-codes support-ticket-triage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/customer-support/support-ticket-triage .cursor/skills/support-ticket-triage && 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 "support-ticket-triage" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/customer-support/support-ticket-triage into .cursor/skills/support-ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "support-ticket-triage", 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/zapier/gtm-cheat-codes.git --path skills/customer-support/support-ticket-triage--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 zapier/gtm-cheat-codes --skill support-ticket-triage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zapier/gtm-cheat-codes support-ticket-triage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/customer-support/support-ticket-triage .gemini/skills/support-ticket-triage && 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 "support-ticket-triage" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/customer-support/support-ticket-triage into .gemini/skills/support-ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "support-ticket-triage", 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 zapier/gtm-cheat-codes support-ticket-triageInstalls 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 zapier/gtm-cheat-codes --skill support-ticket-triage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/customer-support/support-ticket-triage .github/skills/support-ticket-triage && 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 "support-ticket-triage" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/customer-support/support-ticket-triage into .github/skills/support-ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "support-ticket-triage", 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 zapier/gtm-cheat-codes --skill support-ticket-triage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zapier/gtm-cheat-codes support-ticket-triage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/customer-support/support-ticket-triage .opencode/skills/support-ticket-triage && 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 "support-ticket-triage" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/customer-support/support-ticket-triage into .opencode/skills/support-ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "support-ticket-triage", 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
support-ticket-triage- GitHub stars
- 342
- Token cost
- ~670 tokens
- SKILL.md length
- 341 words
- Files
- 6
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Triage support tickets by pulling helpdesk context, searching issue trackers and knowledge bases in parallel, classifying the issue, and giving reps a recommended next action.
- Works in 6 steps: Accept a ticket URL, ticket ID, or… → Pull ticket context through Zapier MCP:… → Search connected systems in parallel → …
- Tasks that involve Customer support
- SKILL.md covers Workflow, Zapier MCP And SDK Role, Output Format and Guardrails, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Support Ticket Triage is an agent skill from zapier/gtm-cheat-codes, published by the product's own GitHub organization. Triage support tickets by pulling helpdesk context, searching issue trackers and knowledge bases in parallel, classifying the issue, and giving reps a recommended next action.
Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `ONBOARDING-PROMPT.md`, `README.md` and `SCHEMA-MAP.md`).
It sits in Sales & Support, covering Customer support. It works with Zapier and Model Context Protocol. The repository describes itself as: A field guide for go to market teams using coding agents. Installable skills for campaign planning, CRM context, customer proof, and reviewable agent workflows. The licence is MIT.
When your agent uses it
- Tasks that involve Customer support
Example prompts
- “/support-ticket-triage”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Accept a ticket URL, ticket ID, or pasted customer message.
- Pull ticket context through Zapier MCP: subject, body, comments, requester, tags, priority, custom fields, status, and assignee.
- Search connected systems in parallel
- Classify the issue into exactly one category: known defect, feature gap, configuration issue, performance issue, or novel issue.
- Return a concise triage summary with evidence, relevant links, and a recommended next action.
- Draft a customer-facing reply only when the rep asks.
What it can do on your machine
Read from SKILL.md and the folder at commit 022a288. 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
Links to these hosts (documentation or services it may open):
zapier.com
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
Support Ticket Triage loads about 670 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 341 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
The full file from zapier/gtm-cheat-codes at commit 022a288, republished under its MIT licence (© zapier). 341 words, ~670 tokens.
Download SKILL.mdSave it as
.claude/skills/support-ticket-triage/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- support-ticket-triage
- description
- Triage support tickets by pulling helpdesk context, searching issue trackers and knowledge bases in parallel, classifying the issue, and giving reps a recommended next action.
Support Ticket Triage Agent
Use this skill when a support rep needs fast, source-backed context before replying to a customer ticket.
Workflow
- Accept a ticket URL, ticket ID, or pasted customer message.
- Pull ticket context through Zapier MCP: subject, body, comments, requester, tags, priority, custom fields, status, and assignee.
- Search connected systems in parallel:
- Defect tracker for open or recently fixed bugs.
- Feature backlog for known gaps or expected behavior.
- Helpdesk history for similar tickets and resolutions.
- Knowledge base for docs, runbooks, and troubleshooting steps.
- Classify the issue into exactly one category: known defect, feature gap, configuration issue, performance issue, or novel issue.
- Return a concise triage summary with evidence, relevant links, and a recommended next action.
- Draft a customer-facing reply only when the rep asks.
Zapier MCP And SDK Role
- Use Zapier MCP to read helpdesk tickets, comments, requester details, issue tracker records, feature backlog items, knowledge-base docs, and optional CRM or account context.
- Use Zapier SDK only if the workflow becomes a durable automation, such as tagging, escalation packet creation, similar-ticket linking, SLA warnings, follow-up reminders, regression alerts, or triage digests.
- Keep customer replies, ticket updates, tags, escalation packets, and broad alerts human-approved.
Output Format
- Ticket category
- Best matching evidence
- Related docs or similar tickets
- Recommended next action
- Optional customer reply draft
- Open questions or escalation gaps
Guardrails
- Do not auto-reply to customers.
- Do not expose internal defect IDs, sprint numbers, or engineering-only notes in customer-facing drafts.
- Do not query observability tools unless the rep provides a concrete signal such as a trace ID, timestamp, error code, or request ID.
- Do not invent matches, timelines, fixes, or customer-impact claims.
- Do not store ticket data beyond the working session unless the approved workflow explicitly requires it.
Inspired By
This skill is generalized from a real implementation by Corey Smith at ClickUp. Corey built an MCP-powered support triage agent that pulls Zendesk context, searches defect tracking and feature backlog systems in parallel, classifies the ticket, and gives reps structured context before they type a reply.
© zapier, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files in skills/customer-support/support-ticket-triage of zapier/gtm-cheat-codes.
- SKILL.md
- ONBOARDING-PROMPT.md
- README.md
- SCHEMA-MAP.md
- SETUP.md
- metadata.yaml
Open the folder on GitHubat commit 022a288
Compare with similar skills
Support Ticket Triage 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 |
|---|---|---|---|---|---|---|
| Support Ticket Triage this skillzapier/gtm-cheat-codes | 342 | — | ~670 | Automated safety check: Pass | MIT | |
| Experience Portal Createforcedotcom/sf-skills | 1.1k | — | ~7.2k | Automated safety check: Notes | Apache-2.0 | |
| Zsxqunnoo/zsxq-skill | 304 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Sales OsromangojiberryAI/gojiberryai-sales-os | 139 | — | ~2k | Automated safety check: Pass | MIT | |
| Zapier Demozapier/zapier-mcp | 430 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Zapier Statuszapier/zapier-mcp | 430 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Zsxq
unnoo/zsxq-skill
知识星球 CLI（zsxq-cli）与底层接口完整操作指南，涵盖星球和内容管理、Skill Pay 微信支付场景。当用户提到知识星球、zsxq、小密圈、星球、登录/认证、发帖、评论、回答、编辑、删除主题、定时发布/定时任务/定时回答、投票、问答主题、markdown 正文、AI…
Sales Os
romangojiberryAI/gojiberryai-sales-os
A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os.
- Official
Zapier Demo
zapier/zapier-mcp
Walk a new user through setting up their first Zapier action and running it live — the smallest possible win.
- Official
Zapier Status
zapier/zapier-mcp
Check the health of your Zapier MCP setup. An agent skill from zapier/zapier-mcp.
Setup Open Index
DrDroidLab/open-index
Install and configure Open Index as the read/write context layer for a domain-specialized agent.
More from zapier/gtm-cheat-codes
All 21 skills in this repo- Official
Customer Deck Builder
zapier/gtm-cheat-codes
Builds a tailored sales or customer success deck from approved CRM context and generates it in Gamma through Zapier MCP for calls like QBRs or renewals.
- Official
Customer Story Writer
zapier/gtm-cheat-codes
Drafts customer stories or metric-led story pages from approved transcripts, notes and quotes, keeping verified claims apart from ones that still need approval.
- Official
Customer Social Proof Finder
zapier/gtm-cheat-codes
Finds approved case studies, quotes, stats, logos and peer examples for campaigns, decks, emails and sales conversations, and flags anything that still needs approval.
- Official
Install Zapier
zapier/gtm-cheat-codes
Works out whether you need Zapier MCP, the SDK or the CLI, then walks through installing and verifying that one path step by step.
- Official
Media Inbox Triage
zapier/gtm-cheat-codes
Sorts a shared Gmail inbox for press, partnership and high-intent requests, scores urgency, suggests an owner and routes items through Zapier MCP for human review.
- Official
MCP Sheet Cache Bridge
zapier/gtm-cheat-codes
Designs an event-driven Google Sheets cache tab that mirrors a Zapier Tables source of truth, so spreadsheet-based tools keep working without direct API reads.
Related
Works with
Categories
Questions about Support Ticket Triage
What does Support Ticket Triage do?
Triage support tickets by pulling helpdesk context, searching issue trackers and knowledge bases in parallel, classifying the issue, and giving reps a recommended next action. Support Ticket Triage is an agent skill from zapier/gtm-cheat-codes, published by the product's own GitHub organization. Triage support tickets by pulling helpdesk context, searching issue trackers and knowledge bases in parallel, classifying the issue, and giving reps a recommended next action.
When should I use Support Ticket Triage?
Support Ticket Triage fits situations like: tasks that involve Customer support.
How do I install Support Ticket Triage in Claude Code?
Run `npx skills add zapier/gtm-cheat-codes --skill support-ticket-triage -a claude-code`. Or copy the skill folder (skills/customer-support/support-ticket-triage in zapier/gtm-cheat-codes) into .claude/skills/support-ticket-triage in your project. Claude Code loads it when a task matches its description.
How do I install Support Ticket Triage in Codex?
Run `npx skills add zapier/gtm-cheat-codes --skill support-ticket-triage -a codex`. Or copy the skill folder (skills/customer-support/support-ticket-triage in zapier/gtm-cheat-codes) into .agents/skills/support-ticket-triage in your project. Codex loads it when a task matches its description.
Can I use Support Ticket Triage 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 zapier/gtm-cheat-codes --skill support-ticket-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/support-ticket-triage, .gemini/skills/support-ticket-triage, .github/skills/support-ticket-triage and .opencode/skills/support-ticket-triage in your project.
What does Support Ticket Triage need to run?
SKILL.md names no scripts, command-line tools or credentials: Support Ticket Triage is instructions for the agent only.
Does Support Ticket Triage access the network?
SKILL.md names 1 domain. As links in the text: zapier.com. This is read from the text; nothing was executed.
Is Support Ticket Triage 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 Support Ticket Triage use?
Support Ticket Triage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Support Ticket Triage use?
About 670 tokens (SKILL.md is roughly 2.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 Support Ticket Triage?
Skills that share tags, products or a category with Support Ticket Triage: Experience Portal Create (forcedotcom/sf-skills, 1.1k stars), Zsxq (unnoo/zsxq-skill, 304 stars), Sales Os (romangojiberryAI/gojiberryai-sales-os, 139 stars) and Zapier Demo (zapier/zapier-mcp, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Support Ticket Triage?
zapier (a GitHub organization, an official publisher) maintains it in zapier/gtm-cheat-codes, which has 342 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on July 13, 2026.
Source: zapier/gtm-cheat-codes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.