Test design, vulnerability assessment, and quality assurance (13.9K skills)
Audit existing experimentation infrastructure and past experiments for methodology issues. Use when asked to "audit our experiments", "is our experimentation sound", or "review past test methodology".
The English summary is being prepared. Showing the original description.
Analyze A/B test results — statistical significance, practical significance, and segmentation. Use when asked to "analyze our A/B test", "is this result significant", or "read these experiment results".
The English summary is being prepared. Showing the original description.
Audit embedding infrastructure — model drift, index freshness, query latency, coverage gaps. Use when asked to "audit our embeddings", "is our index stale", or "find embedding coverage gaps".
The English summary is being prepared. Showing the original description.
Audit existing CDN and edge configuration — find cache misses, missing headers, and performance gaps. Use when asked to "audit our CDN", "why is our cache hit rate low", or "find edge config gaps".
The English summary is being prepared. Showing the original description.
Usability review — evaluate an existing flow or UI against usability heuristics, flag friction points, and recommend fixes. Use when asked to "review the UX", "usability audit", "what's wrong with this flow", "UX feedback", "critique this design", or "why are users dropping off here".
The English summary is being prepared. Showing the original description.
Hi-fi interactive HTML prototype — single-file, double-click-to-open, Playwright-verified. Use when asked to "make it clickable", "build a prototype", "hi-fi mockup", "interactive demo", "iOS prototype", "app mockup", "ui demo", or "prototype this". Goes beyond wireframes into visually finished, state-driven HTML with device frames and real images. Not production code — a design artifact for testing flows and pitching ideas.
The English summary is being prepared. Showing the original description.
Design or audit B2B sales pipeline — define stage names, entry/exit criteria, qualification standards, and CRM field requirements. Use when asked to "design our pipeline", "audit our CRM stages", "define what qualified means", or "build a sales process".
The English summary is being prepared. Showing the original description.
Design or audit a feature store — serving, freshness, and sharing across models. Use when asked "do we need a feature store", "design a feature store", or "share features across models".
The English summary is being prepared. Showing the original description.
PR and community reconnaissance — audit current press coverage, social presence, community health, and competitor PR. Use when asked to "audit our PR", "what's our community state", "how do we compare in press", or before planning a launch or community initiative.
The English summary is being prepared. Showing the original description.
Survey existing forecasting code or models in a codebase — find gaps, stale models, and missing validation. Use when asked "what forecasting models do we have", "audit our forecasts", or "find stale models".
The English summary is being prepared. Showing the original description.
Audit existing dependency security — find unscanned packages, license violations, and SBOM gaps. Use when asked to "audit our dependencies", "do we have an SBOM", or "find license violations".
The English summary is being prepared. Showing the original description.
Design an icon system spec or audit existing icons for consistency and accessibility. Use when asked to "design an icon system", "audit our icons", or "are our icons consistent".
The English summary is being prepared. Showing the original description.
Audit UX copy in a product or codebase — find passive errors, generic labels, missing states. Use when asked to "audit our UX copy", "our error messages are bad", or "review the microcopy".
The English summary is being prepared. Showing the original description.
Audit existing API for breaking change risks and missing compatibility controls. Use when asked to "find breaking change risks in our API", "audit our compatibility controls", or "what could break clients".
The English summary is being prepared. Showing the original description.
Audit a proposed API change for breaking changes — classification and impact assessment. Use when asked "is this a breaking change", "will this break clients", or "assess the impact of this API change".
The English summary is being prepared. Showing the original description.
Audit existing data cleaning code — find missing validation, silent data loss, and quality gaps. Use when asked to "audit our data cleaning", "are we losing data silently", or "find data quality gaps".
The English summary is being prepared. Showing the original description.
Audit existing resilience — identify untested failure modes and chaos engineering gaps. Use when asked "how resilient are we", "what failure modes are untested", or "find our chaos engineering gaps".
The English summary is being prepared. Showing the original description.
Audit existing changelog and deprecation practices — find missing entries, undocumented breaks, and stale deprecations. Use when asked to "audit our changelog", "find undocumented breaking changes", or "check for stale deprecations".
The English summary is being prepared. Showing the original description.
Audit existing caching implementation — find cache misses, stampedes, and key design issues. Use when asked to "audit our caching", "why is our hit rate low", or "find cache stampedes".
The English summary is being prepared. Showing the original description.
Audit existing security controls and detection coverage — find gaps against MITRE ATT&CK. Use when asked to "audit our detection coverage", "where are our security control gaps", or "check our MITRE coverage".
The English summary is being prepared. Showing the original description.
Audit existing performance testing — find missing benchmarks, stale baselines, and CI gaps. Use when asked "do we have benchmarks", "audit our performance testing", or "are our baselines stale".
The English summary is being prepared. Showing the original description.
Design a performance benchmark for an API — test scenarios, metrics, and tooling. Use when asked to "benchmark this API", "design a load test", or "measure throughput".
The English summary is being prepared. Showing the original description.
Build or audit knowledge base -- article structure, coverage gaps, deflection rate, and maintenance process. Use when asked to "build a knowledge base", "what docs are missing", "improve our self-serve rate", or "audit our help center".
The English summary is being prepared. Showing the original description.
Internal legal controls review — approval workflows, contract lifecycle, access to sensitive docs. Use when asked to "audit our controls", "review approval workflows", or "who can access sensitive contracts".
The English summary is being prepared. Showing the original description.