Client Support
Reply to a client or workshop participant about their own Claude work, in Shaw's voice: a how-do-I, an "it's not working" report, a request for tips, a "pick your brain" on quality or process (how do we QA what Claude makes), a question in a check-in, office-hour thread, or client Slack channel, or a check-in reply with no question in it (a status update on what they've built). The trigger is who is writing, not whether they asked something. The channel skill (email-helper, slack-helper) owns delivery and register; the answer's content, the choice between teaching, triaging, and taking it live
Install
npx skills add ShawhinT/non-coding-skills --skill client-supportgit clone --depth 1 https://github.com/ShawhinT/non-coding-skills.git /tmp/non-coding-skills
mkdir -p ~/.claude/skills
cp -r /tmp/non-coding-skills/client-support ~/.claude/skills/client-supportPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Client Support Shaw's engagements put him in front of a lot of people at once: leaders, managers, individual contributors, and everything from first-week Claude users to people already shipping skills. He checks in with them constantly, and the check-ins surface questions and progress reports. This skill is how those get answered: the trigger is who is writing, someone Shaw delivers to, about their own Claude work, not whether their message contains a question. A status update with nothing asked gets a lighter reply: a one-line reaction to what they built and an optional offer of live help. The next lever is for the call, not the email. The skill owns the *content* of the answer: which shape the reply takes, what goes in it, and where to look before writing it. The channel skill it composes with owns everything about *delivery*: `email-helper` for greeting, sign-off, threading, and HTML; `slack-helper` for threads, approval, and the no-sign-off register of a client channel. The job is not to be exhaustive. Shaw's answers are short because the person on the other end has to act on them this week, and because the engagement includes live time where the long version belongs. A reply that reads as a knowledge-base article has usually answered a question nobody asked. ## Before writing **Read the question, then find who's asking.** The asker's role and level set the register and the
Details
- Skill name
client-support- Repository
- ShawhinT/non-coding-skills
- Path
client-support/SKILL.md- Repo updated
- 29 October 2026
FAQ
What does the Client Support skill do?
Reply to a client or workshop participant about their own Claude work, in Shaw's voice: a how-do-I, an "it's not working" report, a request for tips, a "pick your brain" on quality or process (how do we QA what Claude makes), a question in a check-in, office-hour thread, or client Slack channel, or a check-in reply with no question in it (a status update on what they've built). The trigger is who is writing, not whether they asked something. The channel skill (email-helper, slack-helper) owns delivery and register; the answer's content, the choice between teaching, triaging, and taking it live
How do I install the Client Support skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ShawhinT/non-coding-skills --skill client-support. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Client Support popular?
It lives in ShawhinT/non-coding-skills, which has 39 GitHub stars and 6 forks.
Related skills
Aba Brand System
39ShawhinT/non-coding-skills
AI Builder Academy's brand and design system — colors, typography, voice/tone, components, icons, and copy patterns for aibuilder.academy and any ABA-branded surface (landing pages, decks, one-pagers, social graphics, emails, motion graphics). Use whenever Shaw is designing, mocking up, or reviewing anything that should look or sound like ABA. Triggers: "design a landing page for ABA", "make an ABA mockup", "one-pager for [ABA offer]", "what colors / font does ABA use", "ABA-ify this", "make this on brand", "what's the ABA voice", "design an ABA banner / hero / card / form", "slide template fo
Aba Plugin Updater
39ShawhinT/non-coding-skills
Prepare a change to Shaw's aba-plugins marketplace repo (the public plugin clients install via /plugin install aba-skills@aba) as a handoff doc for Claude Code, which executes it natively in the repo. Use whenever he wants to edit, fix, or improve one of the plugin's skills (skill-helper, skill-updater, cost-optimizer), repackage dist/, validate the manifests, or land a commit there. Triggers: "update the plugin", "push a change to aba-plugins", "repackage dist", "cut a plugin release", "add this to the aba-skills plugin". Also fire whenever one of those three skill names comes up as something
Animation Builder
39ShawhinT/non-coding-skills
Build short motion-graphic animations (1–6 seconds) as B-roll overlays for talking-head YouTube videos — icon morphs, label fade-ins, diagrams that draw themselves, side-by-side comparisons, simple flow charts. Use this skill whenever the user asks to create, design, or render an animation, motion graphic, B-roll clip, explainer overlay, or any short visual that needs to be exported as an MP4. Triggers include "make an animation for X", "build a motion graphic", "I need B-roll for this script", "animate the [icon/label/curve/flow]", "render this as a video", "create a short clip that shows X m
Cost Optimizer
39ShawhinT/non-coding-skills
Estimate the token usage and dollar cost of the CURRENT conversation, then translate it into a break-even wage (effective hourly cost) so the user can judge whether the task was worth it. Use whenever the user asks what a conversation cost, how many tokens it used, "was this worth it", "what's the break-even wage", "effective hourly cost", "run the cost estimate", "/cost", "estimate the tokens", or any end-of-conversation cost check. Also fire when the user is weighing the value they got against what a task cost. Produces an estimate (not a billed figure) with list-price and cache-adjusted cos
Call Follow Up
39ShawhinT/non-coding-skills
Process the Follow-up sections Shaw jots on his ABA Calls and ABA Trainings pages after calls. Route each open bullet to where it belongs (the next call page, an ABA task, a CRM Next Contact date, or the email task), then cross off what's handled. Works over any window Shaw names, like yesterday's calls, last week's, a specific date range, or one named call. Use whenever Shaw says "do yesterday's call follow-up", "call follow-up for last week", "follow-up for the [Name] call", "what did I jot down after my calls", "carry this to next week's call", "what's still open from this week's calls", or
Email Helper
39ShawhinT/non-coding-skills
Draft emails in Shaw's voice, and research his Gmail — this skill covers both writing mail and reading it. Use it ANY time Claude is composing or about to compose an email (drafting, replying, forwarding, following up), and ANY time Claude is searching or reading threads to answer a question, verify a fact, or gather context. The trigger is the next tool call: if it is `create_draft`, `search_threads`, `get_thread`, or `label_thread`, this skill should have been invoked first, EVEN when another skill (crm, meeting-prep, outreach, engagements, notion-helper, etc.) is already running and the ema
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.