Explore PostHog's Inbox and act on what it surfaces — the place where signal reports cluster into actionable issues and trends. Use when the user asks "what's in my inbox?", "what should I look at?", "which reports are actionable?", "what's PostHog flagged recently?", asks about a specific report by ID or title, wants to act on / fix / implement a report (turn it into a PR), wants to resolve, dismiss, or snooze a report, or wants to see which signal sources are configured. Covers listing, filtering, drilling into, and acting on reports, plus pointers to the deeper `signals` skill when raw signals or semantic search are needed.

Converts DeepWiki documentation from a GitHub repository into a reusable local skill (Cursor, Agent Zero, OpenCode, or any harness using SKILL.md + references/). Verifies DeepWiki tool access, captures raw wiki structure and contents, splits pages into stable reference files, rebuilds a linked hierarchy, and generates a concise SKILL.md with progressive disclosure. Use when the user asks to "convert DeepWiki to a skill", "make a skill from this repo's wiki", "turn DeepWiki into references", "document this GitHub repo as a skill", or wants reusable per-repo documentation derived from DeepWiki output. Do NOT use when the repo has no DeepWiki coverage, when generating skills from source code (use create-skill instead), or for ad hoc repo Q&A (call DeepWiki MCP directly).

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.

Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align content production with broader brand and SEO goals. Triggers on content strategy, content plan, editorial strategy, content pillars, content calendar, editorial calendar, topical authority, topic clusters, content governance, content roadmap, content production. Also triggers when the user is about to start producing content without a strategic plan.

Plan and execute a launch runbook covering pre-launch verification, go-live procedures, DNS cutover, post-launch monitoring, and rollback procedures. Use this skill whenever the user is preparing to launch a website or product, planning a DNS cutover, building a go-live checklist, or executing a launch day. Triggers on launch runbook, go-live, launch day, DNS cutover, deploy to production, site launch, product launch, cutover plan, launch checklist, deployment procedure. Also triggers when a launch is approaching and the team needs structured coordination, even if 'runbook' is not explicitly stated.

Render Markdown from templates and structured data using Knap CLI. Use when the user asks to apply a Knap template, turn JSON or CSV data into notes, batch-generate Markdown files, or format Defuddle output into a note.

Transforms loose ideas or refined concepts into structured PRDs that capture the what, who, and why — problem, target users, goals, non-goals, and testable acceptance criteria — while deliberately deferring the how (architecture, data models, APIs, delivery phasing) to the planning phase. Works through a progressive interview, light de-risking of risky assumptions, and optional codebase exploration. Use when asked to "write a PRD", "create a PRD", "design a feature", "flesh out this idea", "turn this into a spec", "product requirements", "spec this out", or /prd-designer. Outputs a markdown PRD at docs/prds/{name}.md. Optionally creates a GitHub issue via gh CLI. Dependencies: gh CLI (optional, for issue creation).

Doc-aware planning skill. Turns a PRD, ADR, existing plan, or raw idea into a tracer-bullet implementation plan via a relentless one-question-at-a-time interview. Reads accepted ADRs and a PRD together as constraints: ADRs fix architectural decisions; the PRD supplies goals, non-goals, and acceptance criteria that gate each phase. Drafts Proposed ADRs — asking whether a decision is new or supersedes an existing one — and updates CONTEXT.md as terms resolve. Optional tribunal stress-test before finalizing. Use when asked to "plan with docs", "plan this ADR", "turn this PRD into a plan", "break this down into phases", "tracer bullets", "review my plan", "stress test this approach", or /plan-with-docs.

Post-push CI verification and fix workflow. Use when: (1) user says "pr-post", "check ci", "check actions", "fix ci", or "are checks passing", (2) after pushing code to a PR branch, (3) when the user wants to verify GitHub Actions status and fix any failures.

Pre-deployment security audit of Solidity smart contracts in a Foundry project. Combines static analysis (Slither, Aderyn), symbolic execution (Mythril), and property-based testing (forge fuzz + invariant tests with handlers) to catch reentrancy, access-control, oracle/price manipulation, and arithmetic bugs BEFORE deploying to an EVM chain. Also enforces key hygiene (no plaintext private keys, encrypted cast keystore) and a secure deploy workflow. Use when writing, reviewing, testing, or deploying Solidity/Foundry contracts, building a dApp, or working with forge/cast/anvil, MetaMask, or Web3/DeFi code.

Scaffold a one-command `dev-local` launcher for ANY codebase. Investigates the repo to find its services, ports, and infra dependencies, then generates a single `scripts/dev-local.sh` (up/down/status/logs/restart) that runs every dev server in one tmux session, plus a short skill doc describing it. Use when someone says "set up dev-local", "make a one-command dev launcher", "I want one script to start this repo", "scaffold dev-local for this project".

Query the Genome Aggregation Database (gnomAD). Use when determining the rarity or allele frequency of specific genetic variants, retrieving gene constraint metrics (pLI, LOEUF) to assess loss-of-function intolerance, finding variants in a genomic region or gene, or querying structural variants. Don't use for analyzing individual patient genomes, tracking somatic mutations in cancer (use COSMIC), or requesting raw sequencing reads (use ENA).

Review a batch or stack of pull requests, or run a recurring PR-review pass on a repo. Best with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.