ux-contact-support

ux-contact-support is a skill for Claude Code from Uxcel-Lab/product-skills. It costs 119 tokens per session (2,566 once invoked), scanned A, original, MIT.

A design guide for contact and support experiences, including help centers, frequently asked questions, contact methods, live chat, error help, and feedback. It starts by helping users solve problems themselves, then makes human assistance clear when needed.

In plain words
What is it for?
Use it to design or review customer-support journeys for websites and apps. It helps organize self-service, chat, human contact, help at errors, response expectations, and follow-up after a request.
Why use it?
It prevents support from being reduced to an isolated contact form that leaves users waiting or unsure what happens next. It also addresses unclear channels, hidden help, unannounced bots, and feedback requests that interrupt people.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the uxcel plugin — 58 skills shipped together

Good fit Use it to design or review customer-support journeys for websites and apps. It helps organize self-service, chat, human contact, help at errors, response expectations, and follow-up after a request.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/uxcel-lab/product-skills/contact-support
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Uxcel-Lab/product-skills --skill contact-support
Clone the repo
git clone --depth 1 https://github.com/Uxcel-Lab/product-skills

Made for: Claude Code.

Or install uxcel, the plugin that ships this one along with the rest of its 58 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ux-contact-support

README.md
[![agentmods](https://agentmods.dev/badge/skills/uxcel-lab/product-skills/contact-support/github.svg)](https://agentmods.dev/skills/uxcel-lab/product-skills/contact-support)
Your own site
<a href="https://agentmods.dev/skills/uxcel-lab/product-skills/contact-support"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/contact-support/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ux-contact-support

Your own site · 80×15
<a href="https://agentmods.dev/skills/uxcel-lab/product-skills/contact-support"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/contact-support.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 119 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,566 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00119 $0.02566
Opus 5 $0.00060 $0.01283
Sonnet 5 $0.00024 $0.00513
Haiku 4.5 $0.00012 $0.00257

Measured 12d ago against content hash 88abe21b5e25, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

ux-contact-support scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

ux/screens/contact-support/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Contact & Support Skill

How this skill behaves (read first)

This is a generative skill, and it starts from an uncomfortable fact: ~64% of support contacts are caused by a UX failure — missing/unclear info, a service problem, a roadblock, or a task that looks too complex. So the default instinct ("add a contact form") treats the symptom. The skill's first move is to reduce the need with self-service, then make getting a human easy and predictable when it's genuinely warranted. The common failures: no FAQ/help before the form, a "Contact us" button that drops users into a surprise channel, no wait-time or expectations set, a bot that doesn't admit it's a bot, no help offered at the moment of error, and feedback requests that interrupt and pressure. So this skill gates:

  1. Establish why users contact support and what the team can sustain — that orders the channels and sizes the self-service investment.
  2. Apply the always-true core — deflect with good self-service, make contact easy and predictable, close the loop.
  3. Surface the context-dependent decisions (which channels and order, chatbot vs. human, help-button placement) with trade-offs.

Then it hands off to ux-heuristics-audit, ux-accessibility-audit, ux-aesthetics-audit, ux-microcopy-audit, ux-dark-patterns-audit, and ux-mobile-responsiveness-audit for validation.

Scope & composition (per docs/orchestration-policy.md §9): this skill covers the support experience and its surfaces and composes lower-scope skills rather than re-deriving them. Core children (built as part of the support surface): the contact-form field design via ux-inputs-and-forms. Peers that own a sub-part (defer): help search to ux-search and tooltip craft to ux-tooltips (they own those sub-parts if reached). Downstream (offer, don't auto-build): deeper error-message/recovery design via ux-error-recovery. Inherit, don't regenerate: under an existing design system, take color/type/spacing from its tokens — only set those when designing from scratch.

Read the full file on GitHub · 111 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 111 lines · 119 tokens per session scan A 88abe21b5e25

Subscribe to this mod's changes

ux-contact-support is a skill published in the GitHub repository Uxcel-Lab/product-skills (12 stars, last pushed 2mo ago), licensed MIT. It adds 119 tokens to every session and 2,566 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

pm-brand-motion

A guided process for defining a brand's motion style and making a logo animation demonstration.

konglong87/superPM · 77 tokens

pm-proto

A product-prototyping workflow for planning how an application should work and what its screens should contain. It connects product requirements to interface layouts and interactions.

konglong87/superPM · 55 tokens

design-mobile-apps

Use when the user wants to design a mobile app or UI screens, when they mention their Sleek (sleek.design) projects, or when implementing Sleek designs in code (HTML, React Native, SwiftUI).

aiskillstore/marketplace · 49 tokens

diagram-design

Create branded architecture, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, Venn, pyramid/funnel, treemap, bar, line, Gantt and scatter charts, high-level…

aiskillstore/marketplace · 188 tokens

dengguang-zhaoming-bikeng-zhinan

A Chinese-language knowledge guide about home lighting, including ceiling lights, light strips, color temperature, color rendering, and room zoning.

aiskillstore/marketplace · 99 tokens

appllama-app-design-skill

Build native-feeling, benchmark-quality mobile app screens (Expo / React Native). Use when designing or implementing any mobile UI — screens, flows, onboarding, paywalls, tab bars, sheets, settings, empty states — or when polishing motion, navigation, typography, dark mode, or perceived performance. Enforces Apple HIG…

aiskillstore/marketplace · 184 tokens