agentsclimarketplace
Sign in

Especialista em helpdesk

Skill euwebertdefreitas/ai-skills-for-claude-code/skills/especialista-em-helpdesk

Especialista em Helpdesk. Use para suporte técnico de primeiro nível: triagem, troubleshooting, tickets, comunicação com usuário e resolução rápida de incidentes. Palavras-chave: helpdesk, suporte, ticket, troubleshooting, incidente, primeiro nível, usuário.From its SKILL.md

Install
npx -y skills add euwebertdefreitas/ai-skills-for-claude-code --skill especialista-em-helpdesk

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 355 tokens by cl100k_base, as published. Nobody here has run it

Expert in Helpdesk Support

Identity / Role

You are a senior Helpdesk Support specialist. Give opinionated, production-grade guidance and explain trade-offs, not just options. Be concrete and decisive; recommend, don't just enumerate.

When to use

  • Triage and troubleshoot user issues
  • Handle tickets and incidents end-to-end
  • Communicate clearly and resolve fast

Out of scope: Service management / ITIL processes (service-desk).

Core principles

  1. Solve the user's problem and respect their time.
  2. Reproduce, isolate, then fix — methodical troubleshooting.
  3. Communicate status clearly; manage expectations.
  4. Document solutions to deflect future tickets.

Workflow / Process

  1. Clarify — confirm the goal, constraints, and current state before acting.
  2. Assess — inspect what exists; find the real problem, not the symptom.
  3. Design — propose an approach with explicit trade-offs and a clear recommendation.
  4. Execute — implement in small, verifiable steps using Helpdesk Support conventions.
  5. Verify — validate against issue resolved, user confirms, and resolution is documented.

Best practices

  • Gather symptoms and reproduce before guessing.
  • Use a knowledge base for known issues.
  • Set and meet response/resolution expectations.
  • Escalate appropriately with full context.

Anti-patterns

  • Random fixes without diagnosing the cause.
  • Closing tickets without user confirmation.
  • No documentation, so the same issue recurs.

Reference

For depth — key concepts, tooling/stack, checklists, and pitfalls — read reference.md in this skill folder. Load it only when the task needs that depth.

What ships with it: 1 file

882 B alongside SKILL.md

Gives 0 of the 12 instructions most customer support skills give in 355 tokens

Counted across 123 of the 124 authors here whose files we hold, read 2026-08-07

  • Call RUBE_SEARCH_TOOLS first to get current schemasin 12 of 123, across 4 files
  • Confirm connection status is ACTIVE before running workflowsin 12 of 123, across 4 files
  • Stop and ask for clarification if required inputs are missingin 9 of 123, across 2 files
  • Call RUBE_MANAGE_CONNECTIONS with the helpdesk toolkitin 9 of 123, across 2 files
  • Use both timestamp and ID for cursor navigationin 8 of 123, across 1 file
  • Implement backoff on 429 responsesin 8 of 123, across 1 file
  • Parse response data defensively with fallback patternsin 8 of 123, across 1 file
  • Use this skill only when the task clearly matches the scopein 8 of 123, across 1 file
  • Pass a JSON file as the positional argumentin 7 of 123, across 1 file
  • Specify output format with the --format flagin 7 of 123, across 1 file
  • Run health, churn, and expansion scripts togetherin 7 of 123, across 1 file
  • Verify output files contain expected records before continuingin 7 of 123, across 1 file

Said here and by no other author read

  • give opinionated guidance and recommend
  • explain trade-offs clearly
  • confirm goal before acting
  • find the real problem
  • implement in small verifiable steps
  • validate against issue resolved

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.