Browse skills

Synthetic stakeholder panel — build a mixed panel of grounded personas, run independent and cross-reaction rounds against a launch, pricing change, PRD, or message, and return ranked objections and messages to test. Use when asked to "simulate how users will react", "test this launch with a synthetic panel", "focus group this", "how will people react to this pricing change", or "pressure-test this message".

The English summary is being prepared. Showing the original description.

Signal-based prospecting — read target companies' public websites for buying signals (ads running, incumbent agency, tech stack, hiring, stale content, missing booking) with evidence URLs, then build a cohort you can explain. Use when asked to "find buying signals", "profile these companies", "which accounts should we target", "build a target list from these domains", or "what changed at these accounts".

The English summary is being prepared. Showing the original description.

Customer success reconnaissance — audit current onboarding completion, health signals, NRR, churn patterns, and CS motion. Use when asked to "audit our customer success", "why are customers churning", "what's our NRR", or before designing any CS playbook.

The English summary is being prepared. Showing the original description.

Survey pending and required regulatory filings. Use when asked "what filings are due", "survey our regulatory filings", or "are we behind on filings".

The English summary is being prepared. Showing the original description.

Customer segmentation model builder — tiers customers by ARR, health, and expansion potential; defines CS motion per tier; maps resource allocation. Use when asked to "segment our customers", "define our CS tiers", "how should we allocate CS resources", "build a customer segmentation model", or "who gets high-touch vs. digital".

The English summary is being prepared. Showing the original description.

Design and spec an analytical dashboard — define the question each chart answers, write the SQL queries, spec the layout and refresh cadence. Produces a complete dashboard spec ready to implement. Use when asked to "build a dashboard", "analytics dashboard", "BI dashboard", "weekly product health", or "visualize this data".

The English summary is being prepared. Showing the original description.

Audit existing mocks and test doubles — find contract drift, missing error cases, and stale fixtures. Use when asked to "audit our mocks", "find stale test fixtures", or "check for contract drift".

The English summary is being prepared. Showing the original description.

Audit existing vulnerability management — find SLA gaps, missing tiers, and process failures. Use when asked to "audit our vulnerability management", "find patch SLA gaps", or "are we patching fast enough".

The English summary is being prepared. Showing the original description.

Design a Kubernetes cluster architecture — node pools, RBAC, networking, and workload config. Use when asked to "design a Kubernetes cluster", "plan our node pools", or "design K8s architecture for this workload".

The English summary is being prepared. Showing the original description.

Calculate and extend runway — current cash, burn rate, runway months, and the levers available to extend it. Use when asked to "how long is our runway", "when do we run out of money", or "what cuts extend runway by 6 months".

The English summary is being prepared. Showing the original description.

Review existing analytics — find all dashboards and reports, check who uses them, whether metrics are defined, and whether they drive decisions. Recommend what to keep, kill, or add. Use when asked "are our dashboards useful", "analytics review", or "metrics audit".

The English summary is being prepared. Showing the original description.

Survey existing onboarding docs and developer portal — find gaps and structural issues. Use when asked to "survey our onboarding docs", "find developer portal gaps", or "review our onboarding structure".

The English summary is being prepared. Showing the original description.

Design a motion system for a product — duration tokens, easing curves, and animation principles. Use when asked to "design a motion system", "define duration and easing tokens", or "document animation principles".

The English summary is being prepared. Showing the original description.

Audit existing service mesh configuration — find mTLS gaps, traffic policy issues, and observability holes. Use when asked to "audit our service mesh", "find mTLS gaps", or "review traffic policy issues".

The English summary is being prepared. Showing the original description.

Audit existing animations in a codebase — find inconsistencies, missing reduced-motion support, and performance issues. Use when asked to "audit our animations", "check reduced-motion support", or "our animations are janky".

The English summary is being prepared. Showing the original description.

A/B test design — produce an experiment spec with hypothesis, primary metric, MDE, sample size, run time, and decision rule. Also determines when NOT to A/B test and what to do instead. Use when asked to "design an A/B test", "should we test this", "experiment design", "how do we know if this works", "what's the sample size", or "set up an experiment".

The English summary is being prepared. Showing the original description.

Design a service mesh deployment — technology selection, mTLS policy, and traffic management config. Use when asked "should we use a service mesh", "Istio or Linkerd", or "design our mTLS policy".

The English summary is being prepared. Showing the original description.

Design a vulnerability management program — SLAs, asset tiers, escalation, and metrics. Use when asked to "design a patching program", "set vulnerability SLAs", or "define our patch cadence".

The English summary is being prepared. Showing the original description.

Design an animation spec for a component or interaction — timing, easing, and keyframes. Use when asked to "animate this component", "spec the transition", or "define easing and timing for this interaction".

The English summary is being prepared. Showing the original description.

Write a developer quickstart — minimal steps from zero to first successful API call. Use when asked to "write a quickstart", "get users from zero to first API call", or "write a getting started guide".

The English summary is being prepared. Showing the original description.

Write brand guidelines — logo usage, color, typography, voice, and visual principles. Use when asked to "write brand guidelines", "define logo usage rules", or "document our visual identity".

The English summary is being prepared. Showing the original description.

Audit existing brand assets and usage — find inconsistencies, off-brand applications, and gaps. Use when asked to "audit our brand assets", "find off-brand usage", or "check brand consistency".

The English summary is being prepared. Showing the original description.

Design or audit Kubernetes RBAC — roles, bindings, service accounts, and least-privilege model. Use when asked to "audit Kubernetes RBAC", "apply least privilege in K8s", or "review service account permissions".

The English summary is being prepared. Showing the original description.

Customer Success engineer — onboarding optimization, health scoring, expansion revenue, churn prevention, and NRR growth. Use when asked to "improve onboarding", "score account health", "prevent churn", or "grow NRR".

The English summary is being prepared. Showing the original description.