Loading...
Loading...
Found 43 Skills
Re-explains the previous assistant message in a much simpler way — for when the reply made you go "bro what". Use /bro to get a plain-language version of the last answer.
Flag Elastic-internal jargon in documentation and suggest plain-language replacements. Use when the user asks to check or review docs for terms that external readers would not understand, or when a docs review runs. Do not trigger on ordinary drafting or editing.
Create professional architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as standalone HTML files with SVG graphics, a built-in dark/light theme toggle, and one-click export to PNG / JPEG / WebP / SVG. Accepts plain-language descriptions or pasted Mermaid code (flowchart, sequenceDiagram, stateDiagram) and lays the diagram out from scratch in archify style. Use when the user asks for system architecture diagrams, infrastructure diagrams, cloud architecture visualizations, security diagrams, network topology, technical workflows, approval flows, runbooks, CI/CD flows, process diagrams, API call sequences, request lifecycles, data pipelines, ETL/ELT maps, PII boundaries, data lineage, state machines, lifecycle diagrams, status transitions, or asks to convert/beautify a Mermaid diagram.
Local web reader for Bible passages with ELI5 annotations — a FastAPI + Claude Agent SDK page that loads a passage from FHL, drops plain-language notes onto the words themselves, and lets a bible-buddy agent verify or expand any of them. Use when the user wants to READ or STUDY scripture in a browser rather than in the terminal: 開網頁查經、網頁版 bible buddy、經文標注、ELI5 筆記、劃線筆記、annotate a passage, bible reader UI, start the bible web app. EXCLUDE: terminal Bible Q&A (bible-buddy), devotionals (bible-bread), content review (bible-fact-check).
Analyze, draft, and review Severability clauses for General contracts. Use when the user mentions severability, savings clause, void provision, or asks to review, redline, or generate this clause type. Returns structured risk assessment, plain-language summary, and suggested alternative language.
Analyze, draft, and review Insurance clauses for Construction contracts. Use when the user mentions insurance clause, coverage requirements, construction insurance, or asks to review, redline, or generate this clause type. Returns structured risk assessment, plain-language summary, and suggested alternative language.
Draft and validate commit messages that comply with Conventional Commits 1.0.0. Use when writing git commit messages, enforcing commit format in reviews/CI, mapping commits to SemVer intent, or converting plain-language change notes into spec-compliant messages with optional scope, body, footers, and breaking-change markers.
Analyze, draft, and review Survival clauses for General contracts. Use when the user mentions survival clause, surviving provisions, post-termination obligations, or asks to review, redline, or generate this clause type. Returns structured risk assessment, plain-language summary, and suggested alternative language.
Map plain-language Nexor requirements to exact configuration and build it through Nexor MCP tools. Covers arbitrary lead metadata, notifications, CRM sync, field/status events, qualification gates, workflow tools and hooks, webhooks, jobs, cloud/scheduled functions, cadence, channel and knowledge-base assignment, multi-agent systems, and transfers. Use when a customer asks how an agent can receive or use custom lead information, describes custom behavior, an integration, routing, or a multi-agent build. Discover account configuration before questions, decompose variables, stages, and boundaries, require plan review and sign-off before mutation, prefer deterministic primitives, and read back every expected channel, connection, and knowledge assignment regardless of creation order.
Audit a website and deliver a one-page, plain-language SEO report anyone can act on, centered on a single do-this-week action.
The user built or changed something visual — a UI, an animation, a game, a generated video — and wants it verified, or asks "why does my UI look wrong", "check that the fix actually worked", "does the animation glitch". Use this to record the running thing, critique the recording against plain-language pass criteria, and iterate until it passes with before/after proof.
Routing skill of last resort. Takes a plain-language QA situation and names the right 1-2 skills to use and in what order. Use ONLY when the request does not match any other skill's trigger phrases. Use when: "which skill should I use," "where do I start," "I'm not sure what to test," "/qa-do," or any vague QA situation that doesn't map to one skill. Not for: bootstrapping a brand-new project with no QA — use qa-start. Not for: capturing project setup/context — use qa-project-context. If the request clearly matches another skill, invoke that skill directly instead of routing through here. Related: qa-start, qa-project-context, test-strategy.