Skills for customer support.
9 skills
This skill takes a customer message passed along by the owner and writes an answer that sounds like them. Before writing, it checks order and refund status in PayPal, Square, Stripe, or Shopify, the customer's past dealings in the CRM, and existing Zoho Desk tickets. It can issue a refund, but only after the owner approves. With Shopify connected, it can also list orders that need attention before customers write in.
Debugs Azure production issues with AppLens, Monitor, resource health, and safe triage.
Addresses GitHub PR review comments systematically with gh—triage, reply, and fix loops.
This skill handles HubSpot support tickets through the hubspot CLI. It creates a ticket linked to a contact or company, lists open or unassigned tickets by priority, moves batches of tickets between stages, logs a resolution note, and closes the ticket. It checks the portal's own pipeline and field values at the start of each session.
This skill gathers reviews from Google, Yelp, and Facebook along with tickets, disputes, and email, and groups them into themes with customer quotes. It drafts a reply to each review in the owner's voice for approval, flags customers who stopped buying, and suggests win-back offers.
Configures Prisma with Postgres, MySQL, SQLite, MongoDB, and other supported providers.
This skill looks up the answer to a customer question across the sources you have, such as past tickets, docs, and account notes. It can check whether a bug was reported earlier or what a given account heard from you in the past. The output gives an answer, key findings, cited sources, gaps, and next steps.
This skill turns a solved ticket or a question that keeps coming up into a knowledge base article. It picks a template such as a how-to or a known-issue notice, writes the title and opening for search, and adds publishing notes. Workarounds and known problems customers should hear about also qualify.
This skill packages a customer problem for the engineering team, product managers, or company leaders. The brief states the impact, describes the issue, lists what support already tried, gives reproduction steps for bugs, and says what is needed. It fits cases with repeated reports, a churn threat, or a missed SLA.
An agent skill is a portable pack of instructions that gives an agent specialized know-how for a task. In the open Agent Skills format (from Anthropic, now widely adopted), that pack is a folder with a SKILL.md file and optional scripts or references the agent can load when needed.
SKILL.md is the required main file in a skill folder. It starts with simple metadata (name and description) plus the instructions. Agents use the metadata to decide when a skill applies, then read the full file — and any linked files — only when the task needs them.
Open the listing and follow the source link — usually a GitHub SKILL.md. Install with your agent’s skill flow, or add the repo the way that product documents. When this site shows the skill text, Copy is on the page.
A prompt is paste-in text for one chat turn (or a short thread). A skill is a reusable file pack an agent can discover and load across a task, sometimes with code attached. Prompts live in the prompt directory; skills usually live on GitHub and we link out.
Each skill uses one sitewide category — the same set as the rest of the directory (Coding agent, Marketing, Document intelligence, and so on). Hops filter to categories that already have skills.
Yes. Submit with a public GitHub SKILL.md URL, or attach a skill as part of a method on a use case. An editor reviews it before it appears here.