chsh-sk-cs-engineer

Reviews customer support replies and triages Nordic technical support cases.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/chshzh/claude --skill chsh-sk-cs-engineer-chshzh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chsh-sk-cs-engineer
Source: https://github.com/chshzh/claude/tree/main/skills/chsh-sk-cs-engineer
Command: npx skills add https://github.com/chshzh/claude --skill chsh-sk-cs-engineer-chshzh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Customer support engineers handling Nordic technical cases risk sending replies with unconfirmed root causes, vague next steps, or missing repro details, and they lack a structured way to triage issues or plan escalation strategy. ## Core Features & Use Cases - Reply Review (Mode A): Checks draft customer replies against a six-point checklist covering specific acknowledgment, evidence-based root causes, committed next-touch times, and loop closure. - Issue Triage (Mode B): Classifies reported issues as technical or process-related, routes deep technical work to specialized debugging skills, and produces a triage summary plus a suggested customer message. - Strategy Discussion (Mode C): Acts as a sounding board for escalations, customer relationships, and recurring case patterns without writing anything to disk. - Use Case: A support engineer drafts a reply about a WiFi disconnect issue; the skill flags that the draft asserts an unverified firmware cause and lacks a committed follow-up time before it is sent. ## Quick Start Ask the assistant to review this draft customer reply before sending it to the customer.

Frequently Asked Questions about chsh-sk-cs-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a customer support reply before sending it?

Use Mode A of this skill to check the draft against a six-point checklist covering specific symptom acknowledgment, evidence-based root causes, committed next-touch times, and loop closure. It flags problems rather than silently rewriting the message.

How do I triage a customer-reported technical issue?

Mode B classifies the issue as technical or process-related, then routes deep technical work to specialized debugging skills such as crash, memory, or throughput analysis. It outputs a triage summary plus a suggested next message to the customer.

When should I use this skill versus a debugging skill?

Use this skill when a customer-facing reply or support strategy is involved. Pure internal engineering debugging with no customer communication should go directly to the specialized debug or memory optimization skills.

What information is needed before diagnosing a technical support case?

The skill requires the board type, NCS version, reproduction steps, and logs before theorizing about a cause. If these are missing, it asks the customer for them up front instead of guessing at a mechanism.

Does this skill modify itself during a conversation?

No, it only proposes self-updates at the end of a conversation and asks for explicit approval through a confirmation prompt before applying any changes. Mid-conversation edits happen only if the user explicitly requests them.