Menu
Customer-facing support desk — ticket intake, severity classification, and routing incidents that affect end users (not money movement and not build pipelines).
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Inspect large or complex XLSX workbooks with this repository's JBang and Apache POI analyzer before answering. Use for workbook structure, formulas, bounded cell evidence, the UCI Online Retail II audit, or embedded images when the binary must stay outside the agent context.
Generate Quarkus test data for NebulaTrack satellite events using Instancio models, Datafaker, and domain-specific formats instead of hardcoded literals
Build systems, CI/CD, Kubernetes, deploy pipelines, feature flags in delivery infrastructure, and service runtime operations owned by platform — not customer ticket queues and not accounts payable.
Billing, refunds, invoices, payment processors, revenue recognition, and anything where money or invoices move — including when a broken API blocks checkout or invoicing.
Review, critique, and give publication-readiness feedback on technical articles, tutorials, blog posts, outlines, and individual sections, especially for Java, Quarkus, and The Main Thread audiences. Use when a user asks "review this", "tear this apart", "give me feedback", "check this tutorial", "is this good enough to publish?", "what's wrong with this?", or provides a draft and asks for editorial or technical critique. Covers technical accuracy, code samples, narrative/pedagogy, and voice calibration. Pair with main-thread-tutorial-structure and authentic-voice when those skills are available.
Apply The Main Thread voice to tutorials, articles, explanations, and technical marketing copy: first-person personal technical narration, direct peer-to-peer engineering prose, fluent German/non-native rhythm, smaller plain vocabulary, concrete stakes, occasional dry humor, and no generic AI polish. Use when drafting, rewriting, or reviewing prose for tone; when a user asks for "my voice", "make this sound less AI", "make it sound like The Main Thread", or "run a voice pass"; and when a draft needs less documentation smell, less repetition, or a negation-budget pass. This skill controls wording only. Pair with main-thread-tutorial-structure for invisible story scaffolding, verification, and code standards, and with article-reviewer for critique.
| name | support-triage |
| description | Customer-facing support desk — ticket intake, severity classification, and routing incidents that affect end users (not money movement and not build pipelines). |
When this skill applies, the user is asking about user-visible outages, SLAs, ticket numbers, or customer impact.
After you activate this skill, call routeToSupport with a one-line reason. Then follow up using support-only tools if needed.
Do not use this skill for invoice disputes, refunds, or payment processors — that is finance. Do not use it for CI, Kubernetes, or deploy pipelines — that is devops.
