Explorar skills

Generates a set of interview questions precisely matched to a named subject's known background, public record, and the specific story angle — so every question earns its place and no time is wasted on answers the journalist already has.

Produces a structured, host-ready research brief on an upcoming podcast guest — covering their background, key work, public positions, conversation history, and suggested angles — so the host can prepare a focused interview.

Use Context Hub (chub) for curated, versioned API/SDK docs and agent skills. Keep OpenAI tasks on official docs first.

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Decomposition playbook + specialist-roster conventions + anti-temptation rules for an orchestrator profile routing work through Kanban. The "don't do the work yourself" rule and the basic lifecycle are auto-injected into every kanban worker's system prompt; this skill is the deeper playbook when you're specifically playing the orchestrator role.

54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.

Gerencia especificações persistentes para fluxos de trabalho de codificação de IA. Ative esta skill quando o usuário mencionar explicitamente especificações, forjamento, planejamento estruturado ou comandos relacionados à criação, implementação ou listagem de especificações.

When the user asks about startup metrics, SaaS metrics, unit economics, or business performance tracking. Triggers on: "startup metrics", "SaaS metrics", "CAC and LTV", "unit economics", "burn multiple", "rule of 40", "magic number", "marketplace metrics", "churn rate", "MRR", "ARR", "net revenue retention", "runway", or requests for metrics dashboards and investor reporting.

Writes a clear, professional status update on a media production for commissioners, editors, funders, or executive stakeholders who need to know where a project stands without reading through internal working documents.

Minimize total codebase size through ruthless simplification. Measure success by final code amount, not effort. Bias toward deletion.

Identify untested code by mapping source files to test files. Finds functions without tests and tests missing edge case coverage.

Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.