agentleFS
filippofilip95filippofilip95/wizrd/.claude/skills/support/SKILL.md

support

Skill0 starsChanged 10 months agoMITView on GitHub

Use this skill for client issue triage, bug resolution, and troubleshooting. Triggers when user mentions client issue, bug, support ticket, problem, or troubleshooting. Provides response templates, severity assessment, and communication standards.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. pantalytics/odoo-mcp-pro★ 92same name
    2. madeehahassan/plsbuild-os★ 1same name
    3. priyanshu9888/customer-support★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When a support request comes in:

    line 22
  2. Distinctive:

    Check for existing documentation

    line 25
  3. Distinctive:

    Check recent changes or deployments

    line 30
  4. Distinctive:

    Document resolution for future reference

    line 38
  5. Distinctive:

    Keep clients informed even if there's no progress

    line 149
  6. Distinctive:

    Document everything for future reference

    line 150
  7. Distinctive:

    Use technical jargon without explanation

    line 157
  8. Distinctive:

    Leave clients waiting without updates

    line 158

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Support - Client Issue Triage & Resolution

Role

Provide guidelines and templates for handling client support requests professionally and efficiently.

When to Use

This skill auto-activates when you see requests involving:

  • Client issues or complaints
  • Bug reports
  • Support tickets
  • Troubleshooting requests
  • Problem resolution

Core Workflow

Step 1: Triage & Assessment

When a support request comes in:

  1. Identify the severity (Critical/High/Medium/Low)
  2. Categorize the issue type
  3. Check for existing documentation
  4. Determine if it's a known issue

Step 2: Investigation

  1. Gather relevant context from client folder
  2. Check recent changes or deployments
  3. Reproduce the issue if possible
  4. Document findings

Step 3: Resolution & Communication

  1. Develop solution or workaround
  2. Draft response using templates below
  3. Implement fix if authorized
  4. Document resolution for future reference

Severity Levels

Critical (P1)

  • System is down or unusable
  • Data loss or corruption
  • Security breach
  • Response time: < 1 hour

High (P2)

  • Major functionality broken
  • Significant workflow impact
  • No workaround available
  • Response time: < 4 hours

Medium (P3)

  • Feature not working as expected
  • Workaround exists
  • Minor workflow impact
  • Response time: < 24 hours

Low (P4)

  • Cosmetic issues
  • Feature requests
  • Documentation questions
  • Response time: < 48 hours

Response Templates

Initial Acknowledgment

Hi [Name],

Thank you for reporting this issue. I've received your message about [brief description].

I'm looking into this now and will get back to you with an update within [timeframe based on severity].

In the meantime, [any immediate workaround or action they can take].

Best,
[Your Name]

Investigation Update

Hi [Name],

Quick update on the [issue description]:

**What I've found:**
[Key findings]

**Current status:**
[Where we are in the investigation]

**Next steps:**
[What's happening next]

I'll update you again by [time/date].

Best,
[Your Name]

Resolution

Hi [Name],

Good news - the [issue description] has been resolved.

**What was the issue:**
[Root cause explanation]

**What we did:**
[Solution implemented]

**How to verify:**
[Steps for client to confirm fix]

Let me know if you have any questions or if the issue persists.

Best,
[Your Name]

Escalation Needed

Hi [Name],

I've been investigating [issue description] and need to escalate this to [person/team].

**Why escalation is needed:**
[Brief explanation]

**What happens next:**
[Next steps]

**Expected timeline:**
[When they can expect an update]

I'll stay on top of this and keep you informed.

Best,
[Your Name]

Guidelines

Do

  • Acknowledge issues within the SLA timeframe
  • Keep clients informed even if there's no progress
  • Document everything for future reference
  • Provide workarounds when full fixes take time
  • Thank clients for patience on complex issues

Don't

  • Promise specific fix timelines you can't guarantee
  • Blame other systems or vendors
  • Use technical jargon without explanation
  • Leave clients waiting without updates
  • Share internal investigation details unnecessarily

Issue Categories

Technical Issues

  • System errors
  • Integration failures
  • Performance problems
  • Data inconsistencies

User Issues

  • Training gaps
  • Configuration questions
  • Feature requests
  • Access problems

Process Issues

  • Workflow changes needed
  • Documentation gaps
  • Communication breakdowns

Quality Checklist

  • Issue acknowledged within SLA
  • Severity correctly assessed
  • Client updated on progress
  • Root cause documented
  • Resolution verified with client
  • Knowledge base updated if needed

Related Resources

  • /clients/[client]/support/ - Client-specific support history
  • /knowledge-base/common-issues.md - Known issues database
  • /operations/processes/support-workflow.md - Full support process

Automation Level: 70% - human reviews and sends communications Output Location: /clients/[client]/support/[date]-[issue].md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.