Explore skills

Use when fixing a bug, unexpected behavior, or test failure. Investigation-first TDD loop that traces root cause before touching code.

Помогает писать системные промпты для LLM. Используй когда нужно написать prompt, system prompt, системный промпт, инструкцию для модели.

Generate a polished, client-ready weekly status report for a marketing, content, or creator agency client. Use whenever the user asks to "build the weekly report", "write the Friday update", "summarize the week for [client name]", or pastes raw work logs / Linear / Notion exports and asks for a client-facing summary. Do NOT use this skill for internal team retros or for individual employee perform

Evaluate whether a product experiment hypothesis is specific, measurable, and suitable for testing. Use this skill when the user already has a draft hypothesis and wants to know if it is strong enough for an A/B test or other product experiment.

Product scoping agent that cuts feature bloat and defines the minimum viable product. Triggers on: MVP scope, feature prioritization, what to build first, scope the product, feature list, v1 features.

Create and modify APIs using WunderGraph Cosmo Connect. Covers gRPC plugin development (Go/TypeScript), standalone gRPC services, schema-to-proto workflows, CLI commands (wgc), local router setup, graph.yaml composition, field resolvers, batching, federation entities, and deployment. Use when building Cosmo Connect subgraphs, plugins, gRPC services, or setting up a local Cosmo Router.

Use when the user explicitly asks to research the scope of a requirement or proposed change against the current codebase — e.g. "research the scope of this requirement", "what would adding X touch in this codebase", "do scope research on this spec", "/scope-research". Surveys the codebase to surface concrete facts about which files/areas a change would touch and the relevant facts about each touch

Evaluate a shared AI skill or skill repository before installing or copying patterns.

Use when the user explicitly asks for an "AB", adversarial, two-sided, or "red-team" code review of code changes they have made — e.g. "AB review my diff", "do an AB review of my changes", "red-team this code change", "have two reviewers argue about my code". Dispatches two opposing sub-agents — one building the evidence-based case that the change is mergeable, one building the case that it must n

Use when about to present long or complex AI-generated markdown to the user — typically >150 lines, >5 H2 sections, or content like code reviews, implementation plans, specs, research reports. Also use when the user explicitly asks to convert a markdown source into a readable HTML report. Produces a single self-contained HTML report (TL;DR hero, sticky TOC with importance stars, semantic-color cal

Structure and interpret a cohort analysis to understand retention, engagement, or behavior patterns over time. Use this skill when a team needs to understand how different user groups behave across their lifecycle.

DCB0129 compliance walkthrough for Digital Clinical Safety Officers and health IT manufacturers. Guides you through NHS England's mandatory Clinical Risk Management Standard for the manufacture of health IT systems — hazard identification, risk assessment, safety case, and DCSO responsibilities.