Works with
Packaged from the source skill for Claude, Codex and 4 more.
About this skill
Support Ops turns ticket and arrival exports into an operational view of a support queue. Alireza Rezvani’s skill includes local Python tools for SLA reporting, live or asynchronous capacity planning, and distinguishing self-service opportunities from automation or product defects.
It works on supplied CSV or JSON files without helpdesk credentials. Reports can identify breaches, at-risk tickets, staffing gaps and recurring contact reasons. Staffing outputs are planning estimates, and potential deflection hours are an upper bound until measured against real customer contact rates.
Use this skill when
- An SLA report needs to distinguish business hours from elapsed hours and include open breached tickets.
- A support lead needs an interval-based capacity scenario with measured handling time and shrinkage.
- Repeated contacts need a decision between documentation, agent assistance and a root-cause fix.
What it can do
- Summarize first-response and resolution attainment, response-time percentiles, backlog age and reopens.
- Model live-channel service levels with Erlang C or asynchronous workload and backlog drain; expose concurrency and occupancy assumptions.
- Rank contact reasons using volume, handling effort and answer reuse, and produce a short operational action list.
Typical workflows
- Export de-identified tickets, define priority targets and the service clock, and check timestamp and calendar assumptions.
- Review breaches and arrival peaks, then compare staffing scenarios using the team’s actual handling time and availability.
- Sample recurring issues before choosing a fix, assign an owner and measure contact-rate changes after rollout. The package does not change tickets, schedules or help-center content on its own.
What is inside the skill
Section headings from the original SKILL.md (about 582 words of instructions). Read the full text in the source repository before installing.
- Workflow
- Hard rules
- Report
- Scripts
- References and assets
Bundled files
assets/intervals.example.csvassets/sla_policy.example.jsonassets/tickets.example.csvreferences/deflection_and_kcs.mdreferences/sla_design_and_measurement.mdreferences/staffing_and_erlang_c.mdscripts/deflection_finder.pyscripts/sla_check.pyscripts/staffing_plan.pyLICENSE
Example prompts
- Analyze this de-identified ticket CSV against a weekday 09:00–17:00 Europe/Warsaw SLA. Include open breaches, response percentiles and any holiday-calendar assumptions.
- Build a live-chat capacity scenario from this 30-minute arrival export, using our measured handling time, 25% shrinkage and a stated concurrency assumption. Show peak staffing gaps and model limitations.
- Group these recurring ticket reasons into self-service, agent automation, product fix or manual review. Show the supporting counts and treat estimated saved hours as a hypothesis to measure.
How to install Support Ops
Claude Packaged
- Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files.
- For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
- For Claude apps, upload the ZIP in the Skills section of the capabilities settings.
- Start a new session and describe the task in your own words. Claude picks the skill when the request matches its description.
Codex Packaged
- Download the Codex package. The ZIP contains one folder named after the skill, with SKILL.md and bundled resources.
- Unpack the complete folder into .agents/skills/ inside your repository, or into ~/.agents/skills/ for personal use. Preserve its relative reference-file paths.
- Start a new Codex session and invoke the skill by name or with $skill-name, or describe a matching task.
- AGENTS.md is separate project guidance. The ZIP does not generate or modify that file.
GPT Packaged
- Download the GPT package from the skill page.
- Create or edit a custom GPT (or a ChatGPT project) and paste the contents of SKILL.md into the instructions field.
- Upload the bundled reference files as knowledge so the GPT can consult them.
- Test with one of the example prompts from the skill page and adjust the instructions if your use case differs.
Gemini Packaged
- Download the Gemini package from the skill page.
- For a project, unpack the complete folder into .gemini/skills/ or .agents/skills/. For personal use, use ~/.gemini/skills/ or ~/.agents/skills/.
- Run /skills reload in Gemini CLI, then /skills list to check discovery. There is no need to paste the skill into GEMINI.md.
- Test a matching task and verify the referenced tools and files are available.
Cursor Packaged
- Download the Cursor package from the skill page.
- Unpack the complete skill folder into .cursor/skills/ or .agents/skills/ in your project. For personal local use, ~/.cursor/skills/ and ~/.agents/skills/ are also supported.
- Start a new Cursor session. Type / in Agent chat and select the skill name, or describe a matching task.
- Commit the skill folder and resources for team use. Personal local skills are not automatically available to remote agents or automation runs.
OpenCode Packaged
- Download the OpenCode package from the skill page.
- Unpack the complete folder into .opencode/skills/ in your project, or ~/.config/opencode/skills/ for personal use. OpenCode also supports .agents/skills/ and .claude/skills/ compatibility locations.
- Keep supporting files at their original relative paths. AGENTS.md is separate project-wide guidance and is not generated by this ZIP.
- Start OpenCode in the project and test a matching task with the model and permissions you use.
Permissions & security
Inspect the source, license and declared permissions before use. Read the scripts before running them. Review method
Support Ops FAQ
What does the Support Ops skill do?
Analyze support exports for SLA breaches, staffing pressure and recurring issues, with explicit clock assumptions and limits on estimated savings.
Which AI agents can use Support Ops?
Packages for Claude, Codex and 4 more are built from the same source instructions.
How do I install Support Ops in Claude?
Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
Who made Support Ops and what is the license?
Support Ops is published by Alireza Rezvani under the MIT license. The source is https://github.com/alirezarezvani/claude-skills/tree/main/business-growth/skills/support-ops. The catalog keeps the original attribution.
What permissions does Support Ops need?
Declared permissions: read project files, write generated skill files. Risk level: low. Check the scripts in the source before running them.