skills

Structures recurring manager-report 1:1s with a rolling shared agenda that balances check-in, blockers, two-way feedback, and career growth instead of status updates. Use when someone asks "what should I cover in my 1:1s", "build me a 1:1 agenda template", "my 1:1s have turned into status meetings", or is setting up 1:1s with new reports. Do NOT use for general meeting agendas - use meeting-agenda instead; for writing a formal review document, use performance-review-writer; for drafting a specific piece of feedback, use feedback-writer.

Analyzes an A/B experiment to a defensible verdict - sample-size and minimum-detectable-effect math, two-proportion significance testing with confidence intervals, and checks for the traps that fake a win (peeking, sample ratio mismatch, multiple comparisons). Use when someone asks "is this test significant", "did variant B win", "how long should I run this experiment", "what sample size do I need", or shows experiment results and asks whether to ship. Do NOT use for logging and organizing ML training runs - use experiment-tracking instead; for causal questions without a randomized experiment use causal-inference; for general funnel or metric investigation use funnel-analysis or product-analytics.

Drafts a margin-aware 3-email cart-recovery sequence that reminds, handles objections, then incentivizes only as a last touch. Use when a checkout is started but not completed and you need cart-recovery (abandoned-cart) emails, when wiring an abandoned-cart flow in Shopify, Klaviyo, or similar, or when asked to recover lost carts without overspending on discounts.

Structures and drafts argumentative academic essays - a contestable thesis, claim-evidence-analysis body paragraphs, a fairly-engaged counterargument, and a synthesizing conclusion - marking every spot that needs a real citation instead of inventing sources. Use when a student or writer asks "help me outline my essay", "is my thesis strong enough", "structure my argument for this paper", or needs a draft refined for logic and formal register. Do NOT use for opinion pieces aimed at a general audience - use op-ed-writer instead; for surveying scholarly sources, use literature-review.

Runs a full WCAG 2.2 accessibility audit of an interface - keyboard, screen reader, contrast and zoom, forms, and media, in a fixed pass order - and delivers a severity-triaged findings table with concrete fixes. Use when someone asks "is this page accessible", "run an a11y audit on this UI", "will this pass WCAG AA", "why can't a screen reader use this form", or is preparing for an accessibility review, procurement questionnaire, or VPAT. Do NOT use for color-and-contrast-only questions such as palette checks or colorblind-safe data visualization - use color-accessibility instead.

Designs a disciplined ad creative testing system with hooks, isolated variables, and statistical rigor. Use when setting up a testing pipeline or when creative performance is declining.

Rewrites a section or page into concise, self-contained answer blocks that AI answer engines and search snippets can lift and cite verbatim. Use when restructuring a blog post, FAQ, docs page, or landing copy to win a featured snippet or get quoted by AI Overviews, ChatGPT, or Perplexity, or when a draft buries its answer in setup. Do NOT use for keyword research, full-article drafting, or technical/crawlability SEO - use a dedicated SEO or copywriting skill instead.

Build the monthly client report that renews retainers - results-first structure with business outcomes before activity, the metric-that-matters-to-them rule, work-completed as evidence rather than headline, and a next-month plan with one client-action recommendation. Includes a full copy-paste template and a good/bad results-section pair. Use when an agency team says "write this month's client report", "our reports are just a list of tasks we did", "the client says they don't know what they're paying for", or "make our reporting actually defend the retainer". Do NOT use for the quarterly business review deck - use agency-qbr-upsell instead.

Reposition a generalist agency around a vertical or service specialization, write the "we're the agency that X for Y" statement, and design a paid-audit entry offer backed by aligned case studies. Use when an agency owner says "we do everything for everyone and it's killing our pricing", "should we niche down", "prospects can't tell us apart from every other agency", or "how do we productize the front of our funnel". Do NOT use for writing a one-line positioning statement for a product or startup - use positioning-statement instead.

Run agency quarterly business reviews that expand accounts - the four-part QBR agenda (results retrospective, goal re-alignment, roadmap, expansion proposal), an expansion trigger inventory, land-and-expand sequencing, and price-increase timing. Use when an agency owner says "our QBRs are just bigger status meetings", "how do I grow existing retainers", "when do I raise this client's price", or "the client's goals changed and our scope didn't". Do NOT use for SaaS customer-success QBRs run by a CS team - use customer-success-qbr instead.

Designs reliable multi-agent LLM systems - choosing a topology, writing handoff contracts between agents, deciding what runs in parallel vs series, and setting context, retry, and cost budgets that stop runaway loops. Use when someone asks "should I split this into multiple agents", "my agents keep looping", "how do I pass context between agents", "orchestrator vs pipeline vs router", or is architecting an agent workflow. Do NOT use for tuning a single prompt - use prompt-engineer instead; do NOT use for measuring agent output quality - use llm-evaluation instead; for making a product agent-operable end to end, use build-on-agent-native.

Reduces alert noise by making alerts actionable, symptom-based, and tied to SLOs. Identifies and kills flappy, duplicate, and cause-based alerts. Use when alert fatigue is degrading on-call response quality.

Writes an Amazon product title, five bullets, and backend search terms that obey Amazon's character, byte, and keyword rules while staying click-worthy in the search grid. Use when drafting or fixing a Seller Central listing, rewriting an Amazon title or bullet points, packing backend search terms, or recovering a listing flagged or suppressed for content. Do NOT use when writing on-site product-detail-page copy for your own storefront or marketing site - use product-description-writer instead.

Builds a coherent UI motion system - a duration token scale, named easing curves, choreography rules, and a per-component mapping - so every transition in the product draws from one vocabulary instead of ad-hoc values. Use when someone asks "define our motion tokens", "our animations feel inconsistent", "what duration should this modal use", "set up easing standards", or is starting a design system and needs the motion layer. Do NOT use to spec the motion of one specific component or flow - use motion-spec instead; for animated type treatments, use kinetic-typography.

Runs an annual planning cycle end to end - strategic reflection, 3-5 company priorities with explicit not-doing decisions, cascaded OKRs reconciled between top-down framing and bottom-up team plans, resource allocation with named trade-offs, a quarterly review cadence, and the CEO narrative memo. Use when a leader asks "run our annual planning", "set next year's company priorities", "our planning is just a budget exercise", or needs to turn a leadership offsite into a committed plan. Do NOT use for writing a single team's quarterly OKRs - use okr-builder instead; for a product-specific roadmap, use product-roadmap.

Generates a typed API client from an OpenAPI/Swagger spec, with a hand-controlled transport wrapper for timeouts, auth, and typed errors. Use when integrating a REST API that ships an openapi.yaml/swagger.json, when generating or regenerating a client from a spec, or when a hand-written client keeps drifting from the upstream contract. Do NOT use when the task is the backoff/retry policy itself - use rate-limit-handler instead; do NOT use for cursor pagination or keeping a local copy in sync - use pagination-and-sync-engineer instead.

Designs REST API surfaces - resource naming, HTTP method and status-code semantics, error shapes, pagination, and filtering - and delivers an endpoint spec a consumer can build against without asking questions. Use when someone asks "how should I name this endpoint", "what status code should this return", "should this be PUT or PATCH", "how do I paginate this list", or is reviewing an API before it ships to external consumers. Do NOT use for planning breaking-change rollouts and deprecation windows - use api-versioning-strategist instead; for GraphQL type and resolver design - use graphql-schema instead; for generating client SDKs from an existing spec - use api-client-generator instead; for designing inbound webhook endpoints - use webhook-receiver-hardener instead.

Produces an API version scheme (date-pinned header or URI), a breaking-vs-additive change policy, and a published deprecation/sunset timeline with translation shims. Use when removing or renaming a field or endpoint, tightening validation, cutting a "v2", binding a partner integration to a version, or planning how long an old version lives. Do NOT use when designing the resource shape, URLs, status codes, or pagination of a new endpoint - use REST API Design instead; this skill owns only the version scheme and deprecation path layered on top of that contract.

Use when executing your B2B prospecting strategy inside Apollo.io specifically - turning an ICP into stacked Apollo search filters, building and tiering Apollo Lists, finding and verifying emails with credit discipline, tracking buying signals via Apollo filters and saved-search alerts, and running multi-step Apollo Sequences. Trigger on "Apollo", "Apollo.io", "set up Apollo filters", "Apollo saved search", "Apollo list", "Apollo sequence", "find emails in Apollo", "Apollo credits", "export from Apollo to my CRM", "Apollo Chrome extension", "Apollo intent data", "how do I prospect in Apollo". This skill assumes the strategy is already done in the methodology skills and shows how to operationalize it in Apollo. Do NOT use for designing the ICP itself - use [[icp-persona-builder]]. Do NOT use for writing the actual email copy - use [[cold-email-craft]]. Do NOT use for fixing domain authentication / SPF / DKIM / DMARC - use [[cold-email-deliverability]]. Do NOT use for reading funnel metrics conceptually - use [

Writes App Store and Play Store listing copy to platform-specific rules - iOS name, subtitle, and hidden keyword field; Android title, short description, and keyword-woven full description - delivering every field with character counts, a ranked keyword list, and title options to A/B test. Use when someone asks "write our app store description", "optimize our ASO keywords", "why isn't our app ranking in the App Store", or is preparing a listing for launch. Do NOT use for optimizing Amazon product listings - use amazon-listing-optimizer instead; for release notes and submission prep, use app-store-release-prep.

Produce a reproducible signing, versioning, and store-declaration pipeline so an iOS or Android build passes App Store Connect / Play Console submission. Use when building or uploading a distribution .ipa/.aab, fixing signing/provisioning-profile or entitlement errors, bumping CFBundleVersion/versionCode, filling App Privacy / Data safety forms or PrivacyInfo.xcprivacy, wiring Fastlane lanes, or diagnosing a store rejection. Do NOT use for general (non-mobile) release steps like changelogs, tagging, or backend deploys - use prepare-release instead; do NOT use for store listing titles, descriptions, or keywords - use app-store-copy instead.

Converts sync meetings and vague pings into structured asynchronous messages - TL;DR up front, an explicit ask with owner and deadline, and a default-action line that keeps work moving if nobody replies - plus team response norms per channel. Use when someone asks "how do I say this without a meeting", "rewrite this message so people actually respond", "help my remote team stop living on calls", or "draft an async decision doc". Do NOT use for the recurring exec status update itself - use eng-status-rollup instead - for extracting actions from a meeting that already happened - use meeting-notes-to-actions instead - or for designing the meeting you do keep - use meeting-agenda instead.

Builds and refines audience and segment targeting for paid campaigns - first-party audience construction, lookalike expansion, exclusion lists, platform sizing floors, and saturation diagnosis - and delivers a filled targeting matrix per campaign. Use when someone asks "who should I target with these ads", "why is my ad set stuck in learning", "my CPMs keep rising but conversions are flat", "should I use a 1% or 5% lookalike", or is launching a campaign, diagnosing poor reach quality, or expanding into a new customer segment. Do NOT use for auditing an entire paid program's structure and spend efficiency - use paid-acquisition-audit instead; do NOT use for defining the ideal customer profile itself - use icp-persona-builder instead; do NOT use for market segmentation strategy outside paid media - use segmentation-strategy instead.

Evaluates a major purchase with total cost of ownership, opportunity cost, affordability red lines, and a cooling-off rule, producing a scored buy/wait/walk verdict. Use when someone asks "should I buy this car", "can I afford this", "is this purchase a good idea", or is about to finance anything with a monthly payment. Do NOT use for fitting an approved purchase into the monthly plan - use budget-builder instead; for whether the purchase should outrank debt payoff or savings - use financial-planner; for home-purchase retirement trade-offs - use retirement-projection.

Translates common lab panels - CBC, CMP, lipid panel, thyroid, hormones, HbA1c - into plain language, flags values against the lab's own reference ranges, and produces a prioritized question list to bring to a physician. Use when someone asks "what does my bloodwork mean", "is my ALT high", "explain my lipid panel", or "what should I ask my doctor about these results". General wellness education, not medical advice - it flags and explains, never diagnoses or prescribes. Do NOT use to summarize a medical chart or clinical document - use clinical-summary instead; for diet changes motivated by results, hand off to nutrition-planner.

Runs a company board as an instrument - cadence, a no-surprises pre-wire, a board pack shipped days ahead, and meetings that end in decisions with owners. Use when someone asks "how do I prepare for my board meeting", "what goes in a board deck", "my board meetings feel like theater", "how often should we meet", or "how do I handle a difficult board member". Applies to venture-backed and private company boards; nonprofit and association boards follow different fiduciary and consensus norms, so adapt with care there. Do NOT use for writing the monthly investor update - use investor-update-writer instead - or for general internal meeting agendas - use meeting-agenda instead.

Writes non-fiction book proposals that sell to agents and acquiring editors - an overview hook answering why this book and why now, author platform with real numbers, target market, honest recent comps, a marketing plan, and a chapter outline that proves a full book exists. Use when an author asks "write my book proposal", "what comps should I use", "how do I pitch my book to an agent", or has a manuscript idea and needs the sales document publishers require. Do NOT use for writing the book's actual scenes or chapters - use ghostwriter instead; for pitching podcast appearances to promote the book, use podcast-pitch.

Writes a brand guidelines document - personality traits with is/is-not definitions, voice principles, a tone-by-context matrix, writing mechanics, a say-this-not-that word list, and visual usage rules - all made concrete with do/don't examples. Use when someone asks "write our brand guidelines", "document our voice and tone", "make a style guide the whole team can follow", or teams keep producing off-brand copy and design. Do NOT use for inventing the brand name itself - use brand-naming instead; for organizing messaging by audience and claim, use messaging-hierarchy.

Generates twenty-plus brand or product name candidates across five naming archetypes, scores them against weighted criteria without averaging, and runs linguistic and memorability safety checks. Use when someone asks "help me name my startup", "is this a good product name", "generate name ideas for this feature", or is auditing an existing name for distinctiveness, strategic fit, and risk. Not a substitute for professional trademark clearance. Do NOT use for crafting the positioning the name must express - use positioning-statement instead; for briefing the visual identity around a chosen name, use logo-brief-writer.

Builds a zero-based monthly budget from take-home income using the 50/30/20 framework with explicit adaptation rules and sinking funds for irregular expenses. Use when someone says "help me make a budget", "I don't know where my money goes", "my spending feels out of control", or after an income change or move. Do NOT use for choosing what to fund first across debt, savings, and investing - use financial-planner instead; for sequencing multiple debts - use debt-payoff-planner; for sizing the cash cushion - use emergency-fund-planner; for company or campaign budget variance reporting - use budget-vs-actual instead.

Paces and reallocates ad budget across channels through the month to hit both CAC and volume targets, with daily tolerance bands, a reallocation reserve, and escalation red lines. Use when someone asks "are we pacing to spend the budget", "we're overspending and it's only the 12th", "should I move budget from Meta to Google mid-month", "how do I spend the rest of the budget without wrecking CAC", or is managing live campaign spend at month start or month end. Do NOT use for explaining why last month's spend missed plan - use budget-vs-actual instead - or for auditing whether the channels themselves are worth funding - use paid-acquisition-audit instead.

Structures a budget-vs-actual variance analysis that isolates root causes - price/volume/mix decomposition, timing vs structural expense buckets, a materiality screen, and reforecast flags - instead of restating numbers. Use when someone asks "why did we miss budget", "write the variance commentary for the board deck", "explain this expense overrun", or is closing the month and owes narrative on the P&L. Do NOT use to build the budget or plan itself - use budget-builder instead; do NOT use for a full driver-based forecast model - use fpa-model instead; do NOT use for cash timing and runway questions - use cash-flow-forecast instead.

Build an application on Builder.io's open-source Agent-Native framework (@agent-native/core) - the model where the agent acts inside the app as a first-class peer to the UI, sharing one set of actions and one database with the interface. Covers the core primitives (actions as the single source of truth, SQL-backed shared state, real-time sync, context-awareness, agent-to-agent, automations, the skills convention), the CLI and cloneable-template workflow, and where to read version-matched docs. Use when someone says "build an agent-native app", "use the agent-native framework", "defineAction", "@agent-native/core", "clone an agent-native template", "make the agent a peer to my UI", or "an app where the agent and the UI call the same actions". Do NOT use for authoring generic Claude Agent Skills / SKILL.md files - that is skill-creator; do NOT use for building a standalone MCP server unrelated to this framework - that is the MCP-builder path; do NOT use for plain Next.js / React scaffolding with no agent runtim

Produces a documented inventory of the implicit business rules, edge cases, and bug-as-feature behaviors that tangled code encodes, with real input-to-output examples, so a rewrite preserves behavior. Use when you are about to rewrite, port, or replace legacy code whose only specification is the source, and you see policy buried in conditionals, magic numbers, hardcoded dates, or per-customer special cases. Do NOT use when you need an executable safety net before refactoring - use characterization-test-writer instead; do NOT use when you need to find service boundaries in a monolith - use monolith-decomposer instead.

Keeps not-yet-ready homebuyers warm for months with timeline-based segmentation, listing alerts with a why-this-one note, a monthly market-update touch, the pre-approval nudge, and re-engagement triggers. Use when an agent says "keep my buyer leads warm", "these buyers aren't ready yet", "build my buyer drip", or "leads keep going cold and buying with someone else". Do NOT use for generic marketing email drips - use email-drip-builder instead - or for post-open-house first contact, which is open-house-follow-up.

Use when you need to decide WHO IN YOUR ICP TO HIT NOW based on timing and trigger events rather than static fit - "who should I reach out to this week", "what's a good reason to reach out", "track buying signals", "find trigger events", "champion changed jobs", "they just raised a round", "new VP just started", "they're hiring for X", "they installed a competitor", "intent data spiked", "why now opener", "warm up our outbound", "score and prioritize accounts by signal". Workflow: enumerate the six signal categories (company triggers, people/job-change triggers, hiring reqs, technographics, third-party intent, first-party engagement), map each signal to a "why now" opening line and the play/sequence it should fire, then rank accounts with a fit×signal scoring matrix so you work the hottest first. Do NOT use for defining who fits in the abstract (firmographics, personas) - use [[icp-persona-builder]]; do NOT use for the tool mechanics of pulling/saving signals - use [[apollo-prospecting]].

Designs multi-layer caching - CDN, application, and database - choosing the pattern, TTL, and invalidation plan per data type, and produces a cache-decision table plus stampede protection. Use when someone asks "should I cache this", "Redis or CDN for this endpoint", "how do I invalidate this cache", "why is my cache hit rate so low", or is bolting Redis onto a slow service. Do NOT use for sizing or tuning database connection pools - use connection-pool-tuner instead - and do NOT use for frontend bundle, image, or Core Web Vitals work - use web-performance instead.

Drafts short, honest recruiting outreach and InMail messages to a passive candidate, anchored on one researched, candidate-published professional fact, for a human recruiter to review and send. Use when someone asks "write an InMail to this engineer", "personalize this sourcing message", "draft outreach from this profile", or is contacting a passive candidate about a specific role. Do NOT use for sales or founder cold email to prospects - use cold-email-craft. Do NOT use for designing the multi-touch cadence, channel mix, and follow-up timing around the message - use outreach-sequence-designer. Do NOT use for writing the job description itself - use job-description-writer.

Use when a founder needs to understand or model ownership and dilution. Triggers on "model my cap table", "how much will I be diluted", "option pool", "SAFE conversion", "post-money vs pre-money", "what do I own after this round", "pro rata". Turns equity from a black box into a model the founder controls.

Produce an accurate, properly timed caption track (SRT or WebVTT) from a video's audio - transcribing or aligning to the voiceover script, timing cues to speech, and enforcing line-length and reading-speed rules so captions are readable and in sync. Use when someone says "generate captions", "make subtitles from the audio", "transcribe and caption this", "export an SRT or VTT", "the captions are out of sync", or "the subtitles flash by too fast to read". Do NOT use to burn-in, style, reframe, or position an existing caption track for a platform (9:16, brand styling, safe areas) - that is social-video-formatter; do NOT use to animate text word-by-word as a motion graphic - that is kinetic-typography; do NOT use to write the spoken script in the first place - that is narration-script.