SkillMedev
- 361 skills
- 0 followers
- 1 day ago last updated
- ▌
- ▌ Vercel Firewall And Botid · skillmedevHarden a Vercel app at the platform edge - the Vercel WAF (custom rules, IP blocking, managed rulesets like OWASP CRS + bot_protection + ai_bots, rate limiting), Attack Challenge Mode, system bypass rules, automatic DDoS mitigation, and BotID bot verification on sensitive routes. Use when someone says "protect my Vercel app", "add a WAF rule", "rate limit my API", "block this IP / country / user-agent", "I'm getting DDoSed", "stop bots / scrapers / AI crawlers", "turn on Attack Mode", "verify human vs bot on checkout/signup/login", or "set up BotID". Do NOT use for app-level auth/session logic - that is application code; do NOT use for env vars or secrets - use vercel-env-management; do NOT use for the deploy/promote/rollback flow - use vercel-deploy-pipeline.
- ▌ Eda Playbook · skillmedevRuns a structured exploratory data analysis on a new or suspect dataset - schema audit, target analysis, feature profiling, missingness patterns, and leakage checks - ending in a written decision log. Use when someone says "I just got this dataset, where do I start", "my model metrics look too good", "audit this data before we model it", or is debugging unexpected model behavior. Do NOT use for writing the transformation code itself - use pandas-expert instead; for ongoing production data monitoring use data-quality; for constructing model features after EDA use ml-feature-engineering; for answering a one-off business question from a database use sql-to-insights.
- ▌ Model Card Writer · skillmedevProduces a complete model card - intended use, training data provenance, evaluation results with slices, limitations, and usage guidance - for any model shared beyond its team or affecting people. Use when someone asks "write a model card", "document this model before release", "what should our model documentation include", or is preparing a model for deployment, handoff, or external publication. Do NOT use for producing the underlying evaluation numbers - use model-evaluation-report instead; for ongoing production monitoring plans use data-drift-monitor.
- ▌ Data Drift Monitor · skillmedevDesigns a production drift-monitoring plan for ML systems - statistical tests per feature type, PSI and KS alert thresholds, monitoring cadence, and evidence-based retraining triggers - including a runnable PSI calculator. Use when someone asks "how do I know if my model is drifting", "set up drift monitoring for this model", "should we retrain", or is investigating unexplained model performance degradation. Do NOT use for judging whether a model is good enough to ship in the first place - use model-evaluation-report instead; for tracking training runs use experiment-tracking; for documenting the model for consumers use model-card-writer.
- ▌ Experiment Tracking · skillmedevSets up disciplined ML experiment tracking - run logging schemas, artifact versioning, naming conventions, and reproducibility standards - and produces the run-record template a team actually follows. Use when someone asks "how should we track our ML experiments", "why can't we reproduce this result", "how do I set up MLflow or W&B for the team", or is bootstrapping a new ML project. Do NOT use for analyzing product A/B tests - use ab-test-analyzer instead; for monitoring deployed models use data-drift-monitor; for judging whether a trained model is good enough to ship use model-evaluation-report.
- ▌ Feature Store Design · skillmedevDesigns a reusable, leakage-safe feature store - entity and naming contracts, point-in-time correct training joins, feature versioning, online/offline consistency with staleness SLOs, and governance. Use when someone asks "should we build a feature store", "how do I share features across models", "our model trains great but serves garbage", "how do I version a feature definition", or is diagnosing training-serving skew. Do NOT use for designing the feature transformations themselves - use ml-feature-engineering instead; for monitoring feature and prediction distributions after deployment - use data-drift-monitor instead; for general relational schema design - use database-schema instead.
- ▌ Model Evaluation Report · skillmedevProduces a rigorous, honest evaluation report for an ML model - real baselines, business-matched metrics with confidence intervals, slice-level error analysis, calibration checks, and a go/no-go recommendation. Use when someone asks "is this model good enough to ship", "write up the eval for this model", "did we actually beat the old model", or before any model promotion, stakeholder demo, or retraining decision. Do NOT use for evaluating LLM or prompt outputs - use llm-evaluation instead; for analyzing randomized product experiments use ab-test-analyzer; for documenting a shipped model for consumers use model-card-writer.
- ▌ GRAPHQL Schema · skillmedevDesigns GraphQL schemas and resolvers that scale - domain-modeled types, Relay pagination, DataLoader batching to kill N+1, mutation payloads with typed user errors, and depth/complexity limits that stop abusive queries. Use when someone asks "how should I structure this GraphQL type", "my resolvers are hammering the database", "cursor or offset pagination", "how do I version a GraphQL API", or is designing or reviewing a schema or federation split. Do NOT use for REST or RPC endpoint design - use api-design instead; do NOT use for the underlying table design - use database-schema instead; for hunting existing N+1s in a codebase, use n-plus-one-hunter.
- ▌ Database Schema Designer · skillmedevDesigns normalized, constrained, migration-friendly relational schemas - entity modeling, key and type selection, indexes derived from real query patterns, and safe forward/rollback migrations. Use when someone asks "design a schema for X", "should I normalize or denormalize this", "what should my primary key be", "how do I add this column without downtime", or "why is my unique constraint broken with soft deletes". Do NOT use for tuning a slow query on an existing schema - use sql-query-optimizer instead; for picking indexes from a live workload, use index-advisor; for sizing database connection pools, use connection-pool-tuner; for range/hash partitioning decisions, use partition-planner.
- ▌ Supabase Expert · skillmedevBuilds secure Supabase apps - Row Level Security policies as the authorization layer, schema design against auth.users, Edge Functions for service-role work, realtime subscriptions, and versioned migrations. Use when someone asks "set up RLS for my tables", "is my Supabase app secure", "anyone can read my table with the anon key", "when do I need an Edge Function", or "why is my realtime subscription not receiving rows". Do NOT use for general Postgres schema design without Supabase - use database-schema instead; for tuning slow queries, use sql-query-optimizer; for Stripe billing inside a Supabase app, use stripe-integration.
- ▌ Web Performance · skillmedevDiagnoses and fixes Core Web Vitals - LCP, INP, and CLS - through an ordered audit procedure with concrete code-level changes for images, fonts, JavaScript, and third-party scripts. Use when someone asks "why is my page slow", "how do I fix my LCP", "we're failing Core Web Vitals", "improve my Lighthouse score", or wants a frontend performance audit before a launch or SEO push. Do NOT use for testing server capacity under concurrent traffic - use load-testing instead; for native mobile app performance, use mobile-perf-profiler; for Next.js-on-Vercel-specific tuning, use next-on-vercel-perf.
- ▌ Next JS App Router · skillmedevBuilds and reviews Next.js App Router code - server/client component boundaries, data fetching, caching and revalidation choices, streaming with Suspense, and Server Action mutations - and delivers routes where every dynamic-vs-cached decision is explicit. Use when someone asks "should this be a client component", "why is my data stale", "where do I put use client", "how do I stream this page", or "how do server actions work". Do NOT use for Vercel-specific runtime and cost tuning of an already-built app - use next-on-vercel-perf instead; for edge middleware and ISR deployment topology - use vercel-edge-and-isr instead; for framework-agnostic Core Web Vitals work - use web-performance instead; for designing an application-wide cache layer beyond the framework - use caching-strategy instead.
- ▌ Stripe Expert · skillmedevImplements Stripe payments, subscriptions, and webhooks so billing state stays correct - Checkout Sessions, signature-verified idempotent webhook handlers, dunning, and SCA handling. Use when someone asks "add Stripe subscriptions to my app", "why is my webhook signature verification failing", "my database says subscribed but Stripe says canceled", "how do I avoid double-charging on retries", or "how should I handle failed payments". Do NOT use for choosing price points, tiers, or packaging - use saas-pricing instead; for general-purpose webhook receiver hardening beyond Stripe, use webhook-receiver-hardener; for idempotency patterns outside payments, use idempotency-enforcer.
- ▌ Growth Model · skillmedevBuilds a driver-based growth model - acquisition, activation, retention, monetization, and a loop factor - that projects users and revenue bottom-up, runs base/upside/downside scenarios, and names the one constraint to work on next. Use when someone asks "build me a growth model", "what should our user projection be", "which lever moves growth most", "model our viral loop", or wants projections driven by real inputs instead of a hockey-stick guess. Do NOT use for the SaaS MRR bridge, NRR, and revenue-forecasting mechanics - use revenue-modeling. Do NOT use for decomposing historical active-user change into new, retained, resurrected, and churned - use growth-accounting. Do NOT use for per-customer CAC/LTV math - use unit-economics.
- ▌ Saas Pricing Model · skillmedevDesigns a SaaS pricing model - the value metric, three-tier packaging with feature gates, list prices, annual discount, and a built-in expansion path targeting net revenue retention - delivered as a pricing page spec. Use when a founder asks "how should we price our SaaS", "per seat or usage-based", "what features go in each tier", or is building or overhauling a pricing page. Do NOT use for pricing strategy outside SaaS packaging - use pricing-strategy instead; for the upsell motion after pricing exists, use expansion-revenue.
- ▌ Unit Economics · skillmedevCompute CAC, contribution margin, LTV, LTV:CAC, and payback with honest definitions, a runnable calculator, and a verdict on whether each customer makes money. Use when someone asks "what's my CAC", "is my LTV:CAC healthy", "how long is my payback period", "can I afford to spend more on ads", or before scaling acquisition spend. Do NOT use for gym-specific front-end economics and Client-Financed Acquisition - use gym-money-model instead; for multi-year revenue projections and MRR bridges use revenue-modeling; for cohort-level retention and growth diagnosis use growth-accounting.
- ▌ Expansion Revenue · skillmedevBuilds a systematic expansion playbook for existing SaaS customers - a catalog of usage triggers (limit approach, new team adoption, milestone hit) with routing rules, outcome-anchored upsell and cross-sell talk tracks, ownership and comp models, and metrics led by net revenue retention. Use when someone asks "how do we grow revenue from existing accounts", "build an upsell playbook", "our NRR is too low", or wants trigger-based expansion instead of reps guessing. Do NOT use for designing tiers and value metrics from scratch - use saas-pricing instead; for stopping customers from leaving, use churn-reduction.
- ▌
- ▌ Customer Success Qbr · skillmedevRuns quarterly business reviews that prove delivered value, score account health, and open the expansion and renewal conversation - producing an agenda, a value-delivered slide format, a health-score definition, and an expansion script. Use when someone asks "how do I run a QBR", "prep my quarterly business review", "build a customer health score", "how do I bring up renewal in a QBR", or is preparing an executive business review for a key account. Do NOT use for designing the expansion motion and pricing itself - use expansion-revenue instead - or for rescuing an account already at risk of churning - use churn-reduction instead.
- ▌ Fact Checker · skillmedevVerifies discrete factual claims against multiple independent sources and returns a calibrated verdict - Verified, Likely true, Likely false, Unverifiable, or False - with confidence and citations. Use when someone asks "is this true", "fact-check this claim", "did X really happen", "verify this statistic before we publish", or pastes a quote, number, or viral post to check. Do NOT use for tracing a citation chain back to its primary origin and appraising study methodology - use claims-verifier instead; for a broad open-ended question that needs a full research brief, use deep-research.
- ▌ Policy Brief · skillmedevWrites a concise, evidence-based policy brief - problem, options compared on consistent criteria, and a recommendation - that a decision-maker can act on in minutes. Use when someone asks "write a policy brief", "summarize the evidence and options for this decision", "brief the minister/board/council on X", or needs a one-to-four-page document that turns research into a recommended action. Do NOT use for persuasive opinion pieces - use op-ed-writer instead; for long-form marketing documents, use whitepapers; for condensing an existing long document, use executive-summary.
- ▌ Academic Essay · skillmedevStructures 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.
- ▌ Citation Tracker · skillmedevVerifies that every citation is real, unretracted, and complete, rates source quality by evidence tier, and formats reference lists precisely in APA, MLA, Chicago, or IEEE. Use when someone asks "check my references", "format this bibliography in APA", "are these citations real", or "convert my reference list to IEEE". Do NOT use for checking whether the claims in the text are true - use fact-checker or claims-verifier instead. Do NOT use for writing the review itself - use literature-review or systematic-review instead.
- ▌ Literature Review · skillmedevProduces a thematic literature review that organizes a field into an argument - consensus, disputes, evidence quality, and the open gap the reader should care about. Use when someone asks "write my related-work section", "review the literature on X", "what does the research say about X", or "organize these papers into themes". Do NOT use for an exhaustive, protocol-registered review with formal inclusion criteria and risk-of-bias appraisal - use systematic-review instead. Do NOT use for synthesizing interviews or mixed non-academic sources into decision themes - use research-synthesis instead.
- ▌ Systematic Review · skillmedevRuns a PRISMA-compliant systematic review from PICO question and pre-registered protocol through search strings, two-stage screening, risk-of-bias appraisal, and GRADE-rated synthesis. Use when someone asks "run a systematic review", "build my search strategy and inclusion criteria", "screen these studies against a protocol", or "meta-analyze the evidence on X". Do NOT use for a thematic narrative review of a field without a registered protocol and exhaustive search - use literature-review instead. Do NOT use for synthesizing mixed non-study sources into decision themes - use research-synthesis instead.
- ▌ Deep Research · skillmedevRuns a thorough multi-source research process - decompose the question, gather independent sources, cross-check, synthesize - and delivers a structured, cited brief with confidence levels and gaps. Use when someone asks "research this topic in depth", "give me everything on X", "what does the evidence say about Y", or needs a broad question answered from secondary sources with citations. Do NOT use for designing a study that collects new data - use primary-research instead; for distilling an already-gathered pile of 20+ sources into themes, use research-synthesis; for verifying one discrete claim, use fact-checker.
- ▌ Error Handling · skillmedevDesigns typed, observable, recoverable error handling - an explicit taxonomy of retryable vs terminal failures, Result types at boundaries, single-point logging, and retry policies with real backoff numbers. Use when someone asks "should I retry this error", "how do I structure error types", "why are my logs full of duplicate stack traces", "where do I put the try/catch", or is designing failure paths for an API, job, or client. Do NOT use for building the circuit breaker component itself - use circuit-breaker-builder instead; do NOT use for handling 429s against third-party APIs - use rate-limit-handler instead; do NOT use for writing user-facing error copy - use error-message-writer instead.
- ▌ LLM Evaluation · skillmedevBuilds evaluation harnesses for LLM products - golden datasets, deterministic checks, calibrated LLM-as-judge rubrics, and CI regression gates that turn "seems good" into a tracked number. Use when someone asks "how do I know this prompt change didn't break anything", "set up evals for my RAG pipeline", "is LLM-as-judge reliable", "why did quality drop after the model swap", or is shipping an LLM feature with no quality measurement. Do NOT use for classical ML model reporting (precision/recall, ROC curves, confusion matrices on trained classifiers) - use model-evaluation-report instead; do NOT use for analyzing online A/B experiments - use ab-test-analyzer instead.
- ▌ Prompt Engineer · skillmedevTurns a vague request into a structured, reliable prompt - role, context, task, format, failure handling, and few-shot examples - that produces consistent output across real inputs. Use when someone asks "why does my prompt give inconsistent results", "write a prompt for this task", "the model keeps breaking my JSON", "how do I stop prompt injection from user input", or is building any LLM feature whose prompt was written ad hoc. Do NOT use for converting a working prompt into a reusable agent skill - use prompt-to-skill instead; do NOT use for measuring whether a prompt change improved quality - use llm-evaluation instead.
- ▌ Agent Orchestration · skillmedevDesigns 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.
- ▌ Feature Engineering · skillmedevDesigns ML features with leakage-safe pipelines, correct categorical encoding by cardinality, numeric transforms, and validation that a feature earns its place. Use when someone asks "how should I encode this high-cardinality column", "why does my model score great offline and fail in production", "what features should I build from this table", or "should I scale these inputs". Do NOT use for building the serving infrastructure that stores and versions features across models - use feature-store-design instead; for detecting when live feature distributions shift after deployment - use data-drift-monitor instead; for initial dataset exploration and profiling - use eda-playbook instead.
- ▌ Quiz Generator · skillmedevWrites quizzes and assessments with a stated Bloom's-level distribution, misconception-based distractors, and an answer key with rationales - plus a summary table of level, type, and points per question. Use when someone asks "write a quiz on...", "make a 10-question test for chapter 5", "generate review questions", or "check these multiple-choice questions for quality". Do NOT use for building the grading rubric for an essay or project - use rubric-builder instead; for designing the lesson the quiz sits inside, use lesson-plan-builder; for opinion or research surveys rather than knowledge assessment, use survey-designer.
- ▌ Rubric Builder · skillmedevBuilds grading rubrics - analytic, holistic, or single-point - with criteria traced to learning objectives, 3-5 performance levels, observable behavior in every cell, and defensible weighting. Use when someone asks "make a rubric for this essay", "how should I grade this project", "turn these objectives into scoring criteria", or "my rubric feels vague, fix it". Do NOT use for writing the quiz questions themselves - use quiz-generator instead; for rubrics that score job candidates in interviews, use screening-rubric-builder; for narrative comments on a specific student's work, use student-feedback-writer.
- ▌ Curriculum Mapper · skillmedevMaps a course's scope and sequence across a term or year - units, weeks, standards coverage with introduced/developed/mastered notation, and Bloom's-level progression - and flags gaps and redundancy. Use when someone asks "map my curriculum for the year", "build a scope and sequence for this course", "audit my course for standards gaps", or is deciding unit order for a semester. Do NOT use for planning a single lesson - use lesson-plan-builder instead; for adapting one lesson to mixed readiness levels in one classroom, use differentiated-instruction.
- ▌ Lesson Plan Builder · skillmedevBuilds a complete single-lesson plan - measurable objective, timed four-part arc (hook, direct instruction, guided practice, closure), a formative check with a proceed/re-teach rule, and differentiation notes - clear enough that a substitute could run it. Use when someone asks "write a lesson plan for...", "plan a 50-minute class on photosynthesis", "how should I structure tomorrow's lesson", or "turn this standard into a lesson". Do NOT use for sequencing a multi-week unit or full course - use curriculum-mapper instead; for deep per-learner adaptation of an existing lesson, use differentiated-instruction; for writing the quiz itself, use quiz-generator.
- ▌ Student Feedback Writer · skillmedevWrites specific, growth-oriented feedback on student work using the Glow-Grow-Go structure - evidence from the actual work, one improvement priority, and a concrete next action - sized to the context from draft comments to progress reports. Use when someone asks "write feedback on this essay", "help me comment on these lab reports", "draft progress report narratives", or "make this comment more useful to the student". Do NOT use for feedback to colleagues or direct reports at work - use feedback-writer instead; for formal employee performance reviews, use performance-review-writer; for building the scoring rubric itself, use rubric-builder.
- ▌ Differentiated Instruction · skillmedevAdapts an existing lesson or unit for mixed readiness levels using tiered assignments, flexible grouping, and scaffolds that fade - without lowering the learning objective. Use when someone says "differentiate this lesson", "I have students at three levels in one class", "add scaffolds and extensions to this unit", or needs one lesson to reach struggling and advanced learners at once. Do NOT use for writing a lesson from scratch - use lesson-plan-builder instead; for sequencing units across a term or auditing standards coverage, use curriculum-mapper.
- ▌ Fp A Operating Model · skillmedevBuilds a driver-based FP&A operating model linking business inputs to P&L, balance sheet, and cash flow outputs. Use when building an annual plan, preparing investor materials, running scenario analysis, or stress-testing the business.
- ▌ Expense And Approval Policy · skillmedevDrafts a clear, enforceable expense and approval policy - per-category spend limits, a dollar-tiered approval matrix, receipt and documentation rules, 30/90-day submission deadlines, and audit sampling. Use when someone says "write our expense policy", "who should approve what spend", "set reimbursement rules", or is onboarding a finance system or preparing for a compliance review. Do NOT use for building a departmental or personal budget - use budget-builder instead; do NOT use for the monthly close checklist - use month-end-close instead; do NOT use for general internal SOPs outside spend - use process-doc instead.
- ▌ Month End Close · skillmedevGuides finance teams through a controlled month-end close - sub-ledger cutoffs, journal entries in dependency order, full balance-sheet reconciliation, flux analysis, and sign-off - targeting a locked close by business day 5-10. Use when someone asks "help me close the books", "build a close checklist", "our close takes three weeks, how do we shorten it", "what order do the journal entries go in", or is preparing for an audit. Do NOT use for constructing or interpreting the financial statements themselves - use financial-statement-builder instead - or for writing the budget-variance narrative that follows the close - use budget-vs-actual instead.
- ▌ Budget Vs Actual Variance Analysis · skillmedevStructures 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.
- ▌ Cash Flow Forecast · skillmedevBuilds a rolling 13-week and 12-month cash flow forecast with runway view. Use when managing liquidity, planning for fundraising, preparing board materials, or stress-testing the business under downside scenarios.
- ▌ Financial Statement Builder · skillmedevBuilds and interprets the income statement, balance sheet, and cash flow statement as one linked system - construction order, the three mechanical ties between statements, and the review checks that catch errors. Use when someone asks "build me a three-statement model", "why doesn't my balance sheet balance", "how does net income flow into the cash flow statement", "check this financial package for errors", or is explaining statements to stakeholders. Do NOT use for spreadsheet layout and formula hygiene - use spreadsheet-model-builder instead - for forward-looking 13-week or 12-month cash projections - use cash-flow-forecast instead - or for the monthly process that produces the trial balance - use month-end-close instead.
- ▌ Variant Copy Scaler · skillmedevGenerates distinct, on-brand copy for every size, color, and bundle variant from a single master description, splitting a shared core from a thin per-variant layer so variant pages avoid thin or duplicate-content problems. Use when someone asks "write descriptions for all 12 colorways", "our variant pages are cannibalizing each other", "should each SKU get its own page", or when one product ships in many variants and needs per-variant PDP copy, or near-identical variant pages are creating duplicate-content or canonical problems. Do NOT use to write the single master or parent PDP description from specs - use product-description-writer instead; do NOT use for category or collection page copy - use category-page-copywriter instead.
- ▌ Review To Faq Builder · skillmedevMines customer reviews and Q&A exports into a pre-purchase PDP FAQ and objection-handling block that answers shopper hesitation before it forms, ordered by conversion impact. Use when someone asks "turn these reviews into an FAQ", "shoppers keep asking the same questions before buying", "how do I address the negative reviews on the product page", or has a review or Q&A export and wants to write or rebuild a product page FAQ or cut returns from preventable surprises. Do NOT use to analyze support tickets or CSAT/NPS verbatims for quality root causes - use csat-root-cause instead; do NOT use to write the main product description - use product-description-writer instead.
- ▌ Abandoned Cart Sequence · skillmedevDrafts 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.
- ▌ Comparison Page Builder · skillmedevBuilds an honest "X vs Y" or "best alternative to X" comparison page - scannable table plus use-case routing copy - for high-intent commercial searches. Use when someone asks "write a page comparing us to a competitor", "build an X vs Y comparison page", "create an alternative-to page", or wants a competitor comparison table and copy that names a rival and helps the reader choose. Do NOT use for a general marketing landing page - use landing-page-copy instead; for competitor research itself, use competitive-intelligence.
- ▌ Amazon Listing Optimizer · skillmedevWrites 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.
- ▌ Category Page Copywriter · skillmedevWrite the intro and lower-page copy for an ecommerce collection or category page so it ranks for a commercial query while pushing shoppers toward a product fast. Use when someone asks "write copy for my ecommerce category pages", "write the intro blurb for my collection page", or "write SEO copy for my collection page below the product grid" - the above-grid intro, the H1, and the supporting content under the grid. Do NOT use for standalone marketing or campaign landing pages - use landing-page-copy instead; do NOT use for a single product's description - use product-description-writer instead.
- ▌ Product Description Writer · skillmedevWrites the single on-site PDP master copy - a benefit-led, scannable product detail page in the brand's voice - from a raw spec sheet or feature list. Use when you have a spec list, feature bullets, or a bare template description for one product and need conversion copy for its on-site product detail page. Do NOT use for Amazon or marketplace listings - use amazon-listing-optimizer instead; do NOT use to spin one master into many size/color variants - use variant-copy-scaler instead.
- ▌ Framework Upgrader · skillmedevDrives a major-version framework bump as a sequence of small, reversible, CI-gated PRs using official codemods and changelog diffing while keeping the app green. Use when bumping React, Rails, Spring Boot, Angular, or any framework across a major version with breaking API/config changes; do NOT use for language or runtime version jumps (Python 2 to 3, Node majors, Java LTS) - use language-version-migrator instead.
- ▌ Monolith Decomposer · skillmedevFinds and validates one bounded-context seam to extract from a monolith - gated on coupling-graph, co-change, data-ownership, and transaction-boundary evidence - and sequences an incremental strangler-fig extraction plan. Use when someone asks "where should we cut this monolith", "is this module ready to extract as a service", "plan the extraction of billing from the app", or is evaluating whether a candidate seam is clean. Do NOT use for designing the target service architecture, service communication, or greenfield service boundaries - use microservices instead; do NOT use to document the implicit business rules inside the code being moved - use business-rule-extractor instead. This skill decides where to cut and in what order.
- ▌ Dead Code Eliminator · skillmedevProves code is unreachable with converging evidence, then removes it and its tests, fixtures, and flags in reversible slices without breaking dynamic callers. Use when deleting suspected dead code, cleaning up after a migration or feature retirement, trimming a bloated module, or before estimating work on unfamiliar code. Do NOT use when you want to survey and rank an area's debt without committing to deletion - use find-tech-debt instead.
- ▌ Strangler Fig Planner · skillmedevProduces an incremental migration plan that runs a legacy and a new system side by side behind a routing seam, slicing and sequencing whole capabilities so the old system stays live until its last route is cut. Use when planning to replace or rebuild a large, business-critical system that must keep serving traffic throughout. Do NOT use when extracting a single service from a still-living monolith - use monolith-decomposer instead; for generic non-migration implementation planning, use the plan skill instead.
- ▌ Business Rule Extractor · skillmedevProduces 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.
- ▌ Language Version Migrator · skillmedevPorts a codebase across a breaking language or runtime version with compatibility shims, batched automated transforms, dual-runtime CI, and old-vs-new output diffing, ending in a flag-flip cutover with a rollback rule. Use when someone says "migrate us from Python 2 to 3", "we're jumping Node majors", "move to the next Java LTS", or any runtime upgrade where source must change to keep compiling or behaving correctly. Do NOT use for an application framework's major version (React, Rails, Spring) - use framework-upgrader instead; for proving a database schema or data migration is safe, use migration-safety-checker; and skip it entirely when the runtime change is purely operational (base image, CI matrix, deploy target) with no syntax or semantic breaks.
- ▌ Characterization Test Writer · skillmedevWrites pinning and characterization tests that lock in the current behavior of untested legacy code - bugs included - before a refactor, so any later behavior change trips an alarm. Use when someone says "I need a safety net before refactoring this", "this module has no tests and I have to change it", "capture what this function does today", or the correct behavior is simply whatever the code does now. Do NOT use for writing tests for new behavior built red-green - use tdd-expert instead; do NOT use to decide which code is worth testing or to rank coverage gaps - use coverage-gap-finder instead; do NOT use to verify existing assertions are strong - use mutation-test-runner instead.
- ▌ Carousel Scripter · skillmedevScripts a multi-slide Instagram or LinkedIn carousel as a hook slide, one-idea-per-slide value frames, and a single-CTA closing slide, with per-slide copy and design direction. Use when the user asks to write, script, or outline a carousel, turn a post/idea/listicle into swipeable slides, or build an Instagram carousel or LinkedIn document (PDF) post.
- ▌ Hashtag Strategist · skillmedevBuilds a tiered hashtag and keyword set sized to the account's actual reach - mixing broad, niche, and branded tags per platform limits and screening out banned, spammy, or shadow-flagged tags. Use when someone asks "what hashtags should I use", "build me a hashtag set for this post", "audit my tag block", or is creating reusable tag sets per content pillar on Instagram, TikTok, LinkedIn, X, or YouTube. Do NOT use for writing the caption itself - use social-caption-writer instead. Do NOT use for clustering SEO search keywords by topic or intent - use keyword-cluster-builder instead.
- ▌ Social Caption Writer · skillmedevWrite one platform-native caption from a topic and brand voice, with a front-loaded hook, native length, and a single earned CTA. Use when the user gives a topic (and optionally brand voice or a described image/video) and asks for an Instagram, LinkedIn, X/Twitter, or TikTok caption. Do NOT use when the user wants a dedicated standalone LinkedIn post - use linkedin-post-writer instead; or a multi-post X thread - use tweet-thread-builder instead; or to adapt one existing piece of content into versions for several channels - use cross-platform-reformatter instead.
- ▌ Social Hook Generator · skillmedevGenerates 10 labeled opening lines for a written social post, one per hook archetype, so the writer can test instead of guess. Use when drafting or rewriting the first line of a LinkedIn post, X post or thread, Instagram caption, or newsletter intro. Do NOT use when the hook is the spoken or on-screen opener of a short-form video (TikTok, Reels, Shorts) - use video-hook-writer instead.
- ▌ Social Content Calendar · skillmedevBuilds a 4-week multi-platform posting calendar for a brand or social team, balancing content pillars, per-channel cadence, and real key dates into a week-by-week grid. Use when the user asks to plan, build, or audit a social content calendar or posting schedule across multiple channels (LinkedIn, X, Instagram, TikTok, YouTube Shorts), assign content pillars and ratios, or map a month of posts to launches and events. Do NOT use when planning a solo creator's single-channel video or podcast cadence and theme rotation - use creator-content-calendar instead.
- ▌ Engagement Reply Drafter · skillmedevDrafts short, on-brand replies to public social comments and DMs, including graceful handling of praise, questions, complaints, and criticism. Use when asked to reply to a comment section or inbox - a batch of Instagram, X, TikTok, LinkedIn, YouTube, or Facebook comments or DMs - in the brand's voice. Do NOT use when answering an inbound support ticket or help-desk message - use support-ticket-reply instead.
- ▌ Cross Platform Reformatter · skillmedevRe-expresses one finished piece of content as the native-equivalent post on each target channel, holding the core idea constant while flexing length, structure, register, and conventions per platform. Use when you have a single written post, article, script, or message and need the same idea posted natively on LinkedIn, X, Instagram, TikTok, YouTube Shorts, or a newsletter. Do NOT use when fanning one long-form asset out into different asset types (clip, quote card, blog) - use content-repurposing instead; do NOT use when writing one fresh caption from a topic - use social-caption-writer instead.
- ▌ Rate Limit Handler · skillmedevAdds retry-with-backoff, Retry-After handling, and client-side throttling so a caller stays under an upstream API's rate limits instead of hammering it. Use when you call a rate-limited or quota-enforced third-party API, see 429 or 503 responses or Retry-After headers, or have a worker fleet that needs to share one upstream's quota. Do NOT use to fail fast when a dependency is down - use circuit-breaker-builder instead; do NOT use to scaffold the HTTP client itself - use api-client-generator instead.
- ▌ API Client Generator · skillmedevGenerates 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.
- ▌ Idempotency Enforcer · skillmedevDesigns client-supplied idempotency keys, deduplication storage, and replay semantics so at-least-once delivery and client retries return the first result instead of double-charging or double-shipping. Use when someone asks "how do I stop duplicate charges on retry", "add an Idempotency-Key header to this endpoint", "the queue redelivered a job and we shipped twice", or before exposing any unsafe POST behind a retrying client or queue. Do NOT use for inbound third-party webhook handlers whose dedup is keyed on a provider event ID - use webhook-receiver-hardener instead and reference this skill only for the storage pattern; do NOT use for designing the client-side retry/backoff policy itself - use rate-limit-handler instead.
- ▌ Circuit Breaker Builder · skillmedevWraps flaky upstream dependencies in circuit breakers, aggressive timeouts, and per-dependency bulkheads so a slow or failing service degrades gracefully instead of cascading into a full outage. Use when a slow or unavailable upstream is stalling your threads, outbound calls hang with no timeout, one dependency's outage is taking down unrelated traffic, or you are integrating a network call that can realistically be slow or down. Do NOT use when the goal is staying under a provider's request quota or handling 429s - use rate-limit-handler instead; do NOT use to size a database connection pool - use connection-pool-tuner instead.
- ▌ API Versioning Strategist · skillmedevProduces 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.
- ▌ Webhook Receiver Hardener · skillmedevHardens an inbound webhook endpoint so it verifies the sender signature on the raw body, resists replays, and acknowledges fast by persisting-then-enqueueing before any processing. Use when building or reviewing a handler that receives webhooks from Stripe, GitHub, or any third party, when adding HMAC signature verification, or when a sender is replaying events or hammering you with retries after slow acks.
- ▌ Pagination And Sync Engineer · skillmedevDesigns correct cursor pagination and incremental delta sync against a mutating dataset - cursor contracts, updated_at watermarks, delete propagation, checkpointing, and idempotent reprocessing. Use when someone says "my sync is skipping rows", "should I use cursor or offset pagination", "design the pagination contract for this list endpoint", "keep a local copy of this API in sync", or has an offset/page=N loop against changing data. Do NOT use for generating a typed API client or SDK from a spec - use api-client-generator instead; do NOT use for on-device offline-first sync with conflict resolution between a mobile client and server - use mobile-offline-sync instead; this skill owns server-to-server paging and one-way replication correctness.
- ▌ Brand Naming · skillmedevGenerates 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.
- ▌ Brand Guidelines Doc · skillmedevWrites 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.
- ▌ Visual Hierarchy · skillmedevDiagnoses and fixes visual hierarchy in a page, screen, or layout using ranked levers - size, weight, color, position, whitespace - and the one-focal-point-per-view rule. Use when someone asks "why does this layout feel flat", "what should the eye see first", "everything is competing on this screen", or wants the reading order of a composition made intentional. Do NOT use for a full multi-dimension design review covering usability and craft - use design-critique instead; for building the underlying type scale, use typography-system.
- ▌ Logo Brief Writer · skillmedevWrites a complete creative brief for a logo or identity project - business context, a three-adjective personality axis, deliverables and constraints, competitive territory, rounds and timeline, and concrete success criteria. Use when someone asks "write a logo brief", "brief a designer for our rebrand", "what do I send the identity studio", or is kicking off a brand identity engagement. Do NOT use for generating the brand name itself - use brand-naming instead; for documenting the finished identity system's usage rules, use brand-guidelines; for briefing broader creative direction, use moodboard-builder.
- ▌ Moodboard Builder · skillmedevAssembles a curated moodboard of 8 to 16 images plus a 150-300 word art direction statement that argues for one visual direction. Use when someone asks "build a moodboard", "set the visual direction for this brand", "get the team aligned on look and feel before design starts", or is presenting art direction to a client. Do NOT use for sourcing and licensing individual production images - use visual-asset-curation or stock-photo-finder instead; for codifying an already-approved identity into usage rules, use brand-guidelines.
- ▌ Typography System · skillmedevChooses and pairs typefaces and builds a modular type scale - ratio, named roles, line heights, measure limits, and responsive values - as a complete design-system type layer. Use when someone asks "what fonts should we use", "build our type scale", "why does our typography feel inconsistent", or is establishing the typographic voice for a brand or product. Do NOT use for animated or motion typography - use kinetic-typography instead; for page-level emphasis, spacing, and layout decisions, use visual-hierarchy; for assembling the full brand book, use brand-guidelines.
- ▌ Color Palette Builder · skillmedevBuilds an accessible brand color palette - one anchor color, role assignments, 9-step tonal scales, 60-30-10 distribution, and documented usage rules - ready for a developer to implement without guessing. Use when someone asks "pick our brand colors", "build a color system for our app", "what shade should our buttons be", or is defining the color layer of a design system. Do NOT use for auditing or fixing contrast failures and color-blindness issues in an existing product - use color-accessibility instead; for assembling the full brand book around the palette, use brand-guidelines.
- ▌ Spark Pyspark · skillmedevWrites and tunes PySpark jobs - join strategy and broadcast size limits, shuffle-partition sizing, skew diagnosis and salting, UDF avoidance, caching, and output file layout - with concrete size and skew thresholds. Use when someone asks "why is my Spark job slow", "should I broadcast this join", "one task takes forever while the rest finish", "my job OOMs during a join", or is writing a new PySpark ETL job. Do NOT use for Kafka topic, consumer-group, or streaming-pipeline design - use kafka-pipelines instead; do NOT use for single-machine dataframe work that fits in memory - use pandas-expert instead.
- ▌ Time Series Analysis · skillmedevDecomposes and forecasts time-indexed data with STL, ARIMA/SARIMA, and Prophet, validated by time-ordered backtests against a seasonal-naive baseline. Use when someone asks "forecast next quarter's demand", "is this series seasonal", "why is my ARIMA forecast flat", "how do I backtest a forecast", or has any metric indexed by time that needs prediction or decomposition. Do NOT use for explaining what a trend means for strategy - use trend-analysis instead; for estimating the causal impact of an intervention on a series use causal-inference; for translating a forecast into an ARR or MRR plan use revenue-modeling.
- ▌ Data Quality Framework · skillmedevDesigns layered data quality checks across completeness, validity, consistency, uniqueness, timeliness, and accuracy, with severity tiers, freshness SLAs, and anomaly baselines wired into dbt and CI. Use when someone asks "how do I stop bad data reaching dashboards", "set up dbt tests for this model", "our pipeline loaded duplicate rows again", "what data quality checks should this table have", or "how fresh does this source need to be". Do NOT use for detecting distribution drift in ML features and predictions - use data-drift-monitor instead; for one-off exploration and profiling of a new dataset - use eda-playbook instead; for infrastructure and application telemetry - use observability-stack instead; for removing personal data from datasets - use pii-scrubber instead.
- ▌ Mongodb Expert · skillmedevDesigns MongoDB schemas, indexes, and aggregation pipelines that perform - embed-vs-reference decision rules, the 16MB document limit, ESR compound-index ordering, explain-plan verification, and operational settings for replica sets and sharding. Use when someone asks "should I embed or reference this", "why is my Mongo query slow", "design a MongoDB schema for X", "how do I structure this aggregation pipeline", or "what should my shard key be". Do NOT use for relational or SQL schema design - use database-schema instead; for tuning SQL queries use sql-query-optimizer; for Postgres-on-Supabase work use supabase-expert.
- ▌ Kafka Pipelines · skillmedevDesigns Kafka streaming pipelines end to end - partition-count sizing math, key choice, consumer-group sizing, offset strategy, delivery semantics, poll tuning, and dead-letter handling - with production configs. Use when someone asks "how many partitions should this topic have", "my consumer group keeps rebalancing", "consumer lag keeps growing", "how do I handle poison messages", or is designing a new topic or event-driven pipeline. Do NOT use for Spark batch or PySpark job tuning - use spark-jobs instead; do NOT use for HTTP webhook ingestion reliability - use webhook-receiver-hardener instead.
- ▌ SQL Query Optimizer · skillmedevDiagnoses slow SQL from the execution plan, names the cost driver, and delivers the rewritten query plus index DDL with the expected plan change and write-side cost stated. The general entry point for slow-query work that routes deep cases to specialist skills. Use when someone asks "why is this query slow", "can you optimize this SQL", "what index do I need", "this endpoint got slow and it's the database", or pastes an EXPLAIN output. Do NOT use for deep index strategy across a whole schema - use index-advisor instead; for pure query-shape rewrites when indexes are already right - use query-rewriter instead; for ORM-driven repeated-query patterns - use n-plus-one-hunter instead; for line-by-line EXPLAIN interpretation training - use explain-plan-reader instead; for table partitioning decisions - use partition-planner instead.
- ▌ Clickhouse Analytics · skillmedevDesigns ClickHouse schemas and queries for fast analytics - MergeTree engine selection, ORDER BY key design, partitioning, materialized views, and projections. Use when someone asks "why is my ClickHouse query slow", "how should I order my sorting key", "should I use a materialized view or projection", "how do I deduplicate events", or is modeling an event or metrics table for OLAP. Do NOT use for tuning row-store OLTP databases like Postgres or MySQL - use sql-query-optimizer instead; for general relational schema design use database-schema; for reading query plans on traditional databases use explain-plan-reader; for the streaming ingestion side use kafka-pipelines.
- ▌ Demo Script · skillmedevBuilds a product demo script around the buyer's discovered pain - a 60-second situation recap opening, three to four before/after "moments" mapped to the buyer's metric, and a close that ends before the slot does. Use when someone asks "help me script this demo", "how should I structure tomorrow's product walkthrough", "turn these discovery notes into a demo plan", or before any live or recorded demo. Do NOT use for staging and directing the demo environment, data, and rehearsal - use product-demo-director instead. Do NOT use when discovery hasn't happened yet - run discovery-call-prep first, because a demo without known pain is a feature tour.
- ▌ Objection Handler · skillmedevDiagnoses what is actually behind a B2B sales objection - price, timing, authority, need, competitor, or status quo - and supplies a calibrated, non-pushy response for each with reframe patterns and exact language. Use when someone asks "they said it's too expensive, what do I say", "how do I handle 'not right now'", "the buyer says they're fine with their current tool", or a rep needs a response framework mid-deal. Do NOT use for gym or local-fitness lead objections and speed-to-lead cadence - use objection-handling-and-speed-to-lead instead; for writing a full call script, use closer-sales-script.
- ▌ Mutual Action Plan · skillmedevBuilds a mutual action plan (MAP) with shared milestones, named owners, and buffer-padded dates that drives a qualified deal from verbal intent to signature and go-live. Use when someone asks "build a mutual action plan for this deal", "how do I keep this deal from stalling", "the buyer said yes but nothing is moving", or once a prospect is qualified and has expressed intent to move forward. Do NOT use for preparing the qualification call itself - use discovery-call-prep instead. Do NOT use for scripting the negotiation and close conversation - use closer-sales-script instead.
- ▌ Discovery Call Prep · skillmedevPrepares a rep for a B2B discovery call - targeted company research, a falsifiable hypothesis stack, a layered question plan with MEDDICC and SPICED coverage, and explicit call goals, delivered as a filled prep sheet. Use when someone asks "help me prep for a discovery call", "what should I ask this prospect tomorrow", "build a question plan for my first call with this account", or before any first or second call with a prospect. Do NOT use for scripting the pitch and close of an already-qualified deal - use closer-sales-script instead. Do NOT use for building the outbound sequence that books the call - use outreach-sequence-designer instead.
- ▌ Rfp Response Writer · skillmedevAnswers RFPs and security questionnaires with discipline - a go/no-go score before any writing (win probability times deal size against effort, under 30 percent win chance means decline), a compliance matrix mapping every requirement to a response, answer-library reuse, and win themes threaded through every section. Use when a user says "we got an RFP, help us respond", "should we even bid on this RFP", "build a compliance matrix for this RFP", "answer this security questionnaire", or "our RFP responses take weeks and we keep losing". Do NOT use for proactive proposals sent without a formal solicitation - use sales-proposal-writer instead.
- ▌ Sales Proposal Writer · skillmedevWrites a B2B sales proposal or SOW that restates the buyer's problem in their own words, quantifies the cost of inaction, presents price as anchored options, and drives one dated next step. Use when someone asks "write a proposal for this client", "turn my discovery notes into a proposal", "how should I present pricing in this proposal", or when a deal needs a document to move from discovery to close. Do NOT use for a one-page internal decision brief - use one-pager-designer instead; for investor decks use pitch-deck-builder; for setting the underlying price model use pricing-strategy.
- ▌ Sales Follow Up Cadence · skillmedevDesigns a post-meeting follow-up cadence for active deals - recap within 2 hours, value-add touches on a day 0/2/5/7 rhythm, channel switches when a deal goes quiet, and a clean breakup after 5-7 touches. Use when someone says "the prospect went dark after the demo", "how do I follow up without being annoying", "what should I send after the call", or a deal has stalled between meetings. Do NOT use for cold-prospect sequences before any meeting has happened - use outreach-sequence-designer instead; do NOT use for writing the cold email itself - use cold-email-craft instead; do NOT use for structuring the close with shared milestones - use mutual-action-plan instead.
- ▌ Launch Day Runbook · skillmedevUse when you are running an actual launch day in real time across channels. Triggers on "launch day runbook", "we launch tomorrow", "Product Hunt launch day plan", "hour by hour launch schedule", "who does what on launch day", "PH / Hacker News / Twitter / email sequencing", "launch day checklist", "our launch is going sideways", "contingency if we get rate-limited / Show HN flops / site goes down". Turns the plan into a minute-by-minute war room. Do NOT use when you are still picking the launch date, beats, or channel mix - use [[launch-plan-sequencer]] for the calendar first; this is the execution companion that runs the day it lands on.
- ▌ Messaging Hierarchy · skillmedevUse when turning a positioning statement into actual copy - building the value proposition, message pillars, proof points, and per-channel messaging that keep the website, ads, and sales deck all saying the same thing. Triggers on "write our value proposition", "message pillars", "messaging framework", "messaging house", "key messages", "proof points", "our website and sales say different things", "per-channel messaging", "on-message copy". Takes the positioning-statement as input and feeds landing-page-copy. Do NOT use when you have not yet fixed positioning - use positioning-statement first. Do NOT use when you need the actual hero/landing page words - use landing-page-copy. Do NOT use to sequence launch phases - use launch-plan-sequencer; for the hour-by-hour go-live - use launch-day-runbook; for the sales deck/talk track - use sales-enablement-kit; for the in-product activation flow - use plg-motion-designer.
- ▌ Plg Motion Designer · skillmedevUse when designing a product-led, self-serve activation motion for signups. Triggers on "design our PLG motion", "self-serve onboarding", "what is our aha moment", "define activation", "activation rate", "time-to-value", "onboarding funnel", "in-product nudges", "set activation milestones", "signup to value", "free-to-paid", "PQL". Defines the aha moment, the activation milestones to it, and the in-product nudges and metric gates between each step. Do NOT use for outbound/sales-led launch sequencing - use [[launch-plan-sequencer]] instead; for arming a human sales team with collateral, use [[sales-enablement-kit]] instead; for the page that captures the signup, use [[landing-page-copy]]; for pricing tiers and the paywall, use [[saas-pricing]] and [[pricing-strategy]].
- ▌ Press Release Writer · skillmedevWrites announcement press releases in proper wire format - inverted pyramid structure, a headline under 100 characters carrying the news verb, dateline conventions, quote construction rules (executive quote states vision, customer quote states outcome), and a boilerplate block. Use when a user says "write a press release for our launch", "we're announcing a funding round, draft the release", "turn this announcement into a press release", or "is this press release newsworthy enough". Do NOT use for orchestrating a Product Hunt launch - use product-hunt-launch instead - for running the launch day itself - use launch-day-runbook instead - or for tracking coverage after the release goes out - use media-monitor instead.
- ▌ Sales Enablement Kit · skillmedevUse when equipping a sales motion with the full set of assets reps actually carry into deals, produced as one coherent kit - a one-pager, a competitive battlecard, a demo script outline, and an objection-handling matrix. Triggers on "build the sales enablement kit for our new product", "equip our sales reps with enablement assets", "put together the sales collateral for our launch". Do NOT use for a single standalone battlecard or a one-competitor deep-dive - use competitive-intelligence instead; do NOT use when the category frame (for whom, unlike what) is not yet fixed - use positioning-statement first; do NOT use when the value ladder and proof points are not settled - use messaging-hierarchy first; do NOT use to sequence the rollout calendar - use launch-plan-sequencer; do NOT use to brief the team and run the checklist on launch day - use launch-day-runbook; do NOT use for a self-serve / no-rep-in-the-room motion - use plg-motion-designer instead.
- ▌ Launch Plan Sequencer · skillmedevUse when planning a product launch end-to-end and you need the full dated timeline. Triggers on "plan my launch", "launch plan", "how do I sequence a launch", "pre-launch checklist", "what happens before launch day", "launch timeline", "GTM launch plan", "coordinate a launch across channels", "who owns what for launch". Builds the pre-launch → launch-day → post-launch arc with a channel & asset checklist, owners, and dates. Do NOT use when you need the minute-by-minute run-of-show for the day itself - use launch-day-runbook instead. Do NOT use to write the core message - use positioning-statement and messaging-hierarchy. Do NOT use to design the self-serve adoption motion - use plg-motion-designer. Do NOT use to build the sales deck, battlecard, or demo script - use sales-enablement-kit.
- ▌ Positioning Statement · skillmedevUse when defining or sharpening what a product IS before writing copy or planning a launch. Triggers on "how do I position this", "what category are we in", "who is this really for", "positioning statement", "we sound like everyone else", "nobody gets what we do", "frame the product", "April Dunford positioning". Runs competitive alternatives → unique attributes → the value they enable → best-fit segment → market frame, producing one tight defensible paragraph. Do NOT use for the actual page/headline wording - use [[messaging-hierarchy]] instead; for price points - use [[pricing-strategy]] or [[saas-pricing]].