SkillMedev
- 854 skills
- 0 followers
- 24 repo stars
- 3 days ago last updated
- ▌ Goals Accountability 2 · skillmedevTurns vague intentions into SMART goals with both lagging targets and controllable leading indicators, then keeps them alive with a 10-minute weekly check-in template, an accountability structure (visible goals, public commitments, partner check-ins), and a quarterly reflection that converts the quarter into lessons. Use when someone says "help me set goals I'll actually stick to", "I set resolutions and abandon them by February", "build me a goal tracking system", or wants a weekly review cadence for personal targets. Do NOT use for company or team objective-setting - use okr-builder instead - or for building daily habits - use habit-builder instead.
- ▌ Idempotency Enforcer 2 · 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.
- ▌ Image License Rights · skillmedevDecides whether a specific image use is legally permitted, what the license obligates, and whether a model or property release is required - covering CC0 and Creative Commons variants, Unsplash/Pexels/Pixabay terms, royalty-free vs rights-managed, standard vs extended tiers, editorial-use-only, and AI-image caveats - and delivers a per-image license record. Use when someone asks "is this free for commercial use", "do I need to credit the photographer", "can I put this on merchandise", "what is royalty-free vs rights-managed", "is editorial-use-only a problem", or "do I need a model release", or is about to publish, advertise, or sell anything containing a stock image. Do NOT use to find or search for a photo - use stock-photo-finder instead; do NOT use to fetch images via an API with attribution rules - use stock-photo-api instead.
- ▌ Linkedin Post Writer 3 · skillmedevWrite LinkedIn posts built for the feed - a hook that survives the two-line truncation, scannable one-idea-per-line structure, a comment-bait close, and first-hour engagement moves. Use when someone asks "write a LinkedIn post about this", "punch up my LinkedIn hook", "why did my post get no reach", or "turn this win into a LinkedIn post". Do NOT use for Twitter/X threads - use tweet-thread-builder instead. Do NOT use for scheduling across a monthly calendar - use social-content-calendar instead.
- ▌ Meta Title Optimizer 2 · skillmedevWrites title tags and meta descriptions that survive SERP truncation, place the primary keyword early for relevance, and frame the snippet to win the click against competing results. Use when someone asks "write a title tag for this page", "why does this page rank but get no clicks", "is my title too long", "rewrite my meta description", or wants a snippet that stands out from the pattern on the results page. Do NOT use for broad on-page or technical SEO (headings, internal links, schema, crawlability, Core Web Vitals) - use seo-optimizer. Do NOT use for classifying what searchers want from a query - use search-intent-classifier. Do NOT use for finding what content the page itself is missing versus competitors - use serp-gap-analyzer.
- ▌ Mobile Perf Profiler 2 · skillmedevDiagnoses and fixes mobile jank, dropped frames, slow startup, and growing memory by capturing a trace or heap snapshot on a real device, isolating the single worst cost, fixing it, and re-measuring against the 16ms frame and cold-start budgets. Use when someone says "the app stutters when I scroll", "startup takes forever", "memory keeps climbing after navigating around", or the UI feels laggy on a real device. Do NOT use when the bottleneck is a website or web app (LCP, bundle size, slow endpoint or query) - use web-performance instead; for Compose recomposition fixes pair with jetpack-compose-builder; for Flutter widget architecture use flutter-widget-architect.
- ▌ Mutation Test Runner 2 · skillmedevRuns mutation testing on already-covered code and turns each surviving mutant into a specific missing assertion, exposing tests that execute code but verify nothing. Use when line coverage is high yet a bug slipped through, when reviewing a critical module (pricing, permissions, auth, state machines) before release, or when you are asked to run Stryker, PIT, mutmut, or cosmic-ray. Do NOT use when the goal is to find which code paths are untested at all - use coverage-gap-finder instead.
- ▌ Sales Enablement Kit 2 · 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.
- ▌ Soc2 Evidence Helper · skillmedevMaps engineering controls to SOC 2 Trust Service Criteria, builds a continuous evidence-collection plan with cadences per control family, and produces the control-to-evidence table auditors work from. Use when someone asks "what evidence do we need for SOC 2", "map our controls to the Trust Service Criteria", "how do we prepare for Type II fieldwork", "the auditor asked for access reviews", or is closing findings or standing up a compliance program. Do NOT use for building an incident postmortem - use postmortem-writer instead; do NOT use for finding and prioritizing actual vulnerabilities - use vulnerability-triage instead; this skill organizes proof that controls operate, it does not implement the controls.
- ▌ Sound And Music Sync 2 · skillmedevScore a video like an editor: beat-match cuts to the music, land SFX on transitions, pace the voiceover so it breathes, source royalty-free tracks safely, and duck the music so the VO sits clearly on top. Use when adding music, sound effects, or voiceover to a video, when asked to "sync cuts to the beat", "the music is drowning out the voice", "add whooshes on the transitions", "where do I get royalty-free music", "mix the audio", or "the VO feels rushed". Do NOT use when wiring audio into the Remotion timeline mechanically (Audio/staticFile/render) - that is remotion-compose and remotion-render; do NOT use when choosing the shot order or scene beats - use video-storyboard instead; do NOT use when tuning the visual look (color grade, lighting, contrast) - use motion-color-and-light instead.
- ▌ Support Ticket Reply 2 · skillmedevDrafts empathetic, accurate, action-first support replies structured to resolve the ticket in one touch - resolution first, context second, one unambiguous next step. Use when someone asks "help me reply to this customer", "draft a response to this ticket", "how do I tell a customer X", or is composing responses to customer issues, complaints, or feature requests. Do NOT use for emotionally charged conversations or refund decisions - use refund-deescalation instead; for building a reusable library of canned responses, use support-macro-library; for diagnosing why satisfaction scores are falling, use csat-root-cause.
- ▌ Term Sheet Explainer 3 · skillmedevDecodes every clause of a VC term sheet into plain English, marks each term founder-favorable, market-standard, or investor-favorable, and flags deviations in priority order. Use when a founder asks "what does liquidation preference mean", "is this term sheet normal", "explain participating preferred", "what is the option pool shuffle", or receives a term sheet and needs to understand it before responding. Do NOT use for planning counters, trades, and negotiation strategy - use term-sheet-negotiation instead; do NOT use for choosing between a SAFE and a priced round - use safe-vs-priced-round instead.
- ▌ Tweet Thread Builder 3 · skillmedevTurn one idea into a tight tweet thread - a hook that earns the click, one beat per post, and momentum to a single CTA. Use when someone asks "turn this into a thread", "write a thread about my launch", "why did my thread flop", or "give me hook options for this". Do NOT use for LinkedIn-format posts - use linkedin-post-writer instead. Do NOT use for adapting one finished piece across many platforms - use content-repurposing instead.
- ▌ Vulnerability Triage 2 · skillmedevPrioritizes vulnerability findings from scanners, pentest reports, and bug bounty submissions by real-world exploitability rather than raw CVSS, assigning internal severity tiers with fix SLAs. Use when someone asks "which of these CVEs do we fix first", "triage this scanner report", "is this CVSS 9.8 actually critical for us", or is facing a wall of security findings and needs an actionable queue. Do NOT use for enumerating threats in a design that has not shipped - use threat-model-stride instead; for an active exploitation incident in production, use sev-triage; for reviewing the code itself, use secure-code-review.
- ▌ Monolith Decomposer 2 · 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.
- ▌ Next On Vercel Perf 2 · skillmedevDiagnose and fix Core Web Vitals and page performance of a Next.js app on Vercel - measurement-first. Use when an LCP/INP/CLS score is bad, a page "feels slow", Lighthouse/PageSpeed/Speed Insights is red, the JS bundle is too big, images or fonts are janky, or you want Vercel-specific caching/edge wins. Triggers: "improve Core Web Vitals", "fix LCP", "reduce INP", "stop layout shift", "my Next.js page is slow on Vercel", "shrink my bundle", "next/image optimization", "font is causing CLS", "cache this page". Do NOT use to set up the deploy pipeline or rollbacks - use vercel-deploy-pipeline; for ISR/cache-component semantics and edge runtime choice - use vercel-edge-and-isr; for env/secrets - use vercel-env-management; for model/provider routing - use vercel-ai-gateway; for WAF/bot defense - use vercel-firewall-and-botid.
- ▌ Observability Stack 3 · skillmedevInstruments systems with the three pillars - structured logs, RED/USE metrics, and distributed traces - correlated by one trace ID, with cardinality budgets and symptom-based alerts. Use when someone asks "how should I instrument this service", "what metrics should I emit", "why is my metrics bill exploding", "set up OpenTelemetry for my stack", or "we can't tell which service is slow". Do NOT use for tuning an existing noisy pager or alert thresholds - use alert-tuning instead; for defining SLO error-budget policy, use error-budget-policy; for the incident process when alerts fire, use sev-triage and postmortem-writer.
- ▌ Plg Motion Designer 2 · 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]].
- ▌ Prospecting Metrics 2 · skillmedevUse when you need to turn outbound prospecting into a measurable, backsolvable funnel instead of guesswork - for quota planning, activity targets, funnel diagnosis, and A/B test sizing. Triggers include "how many emails do I need to send", "backsolve my quota", "what's a good reply rate", "how many meetings per 100 contacts", "my outbound isn't converting", "where is my funnel breaking", "is this A/B test significant", "how many contacts to hit pipeline target", "what activity do I need this week", and "what conversion rates should I expect for cold outbound". Workflow: define the canonical funnel, plug in your real (or benchmark) conversion rates, backsolve required weekly activity from a quota, diagnose which stage is broken, and size tests honestly. Do NOT use for writing the actual messages - use [[cold-email-craft]]; Do NOT use for designing the multi-step cadence itself - use [[outreach-sequence-designer]]; Do NOT use for fixing inbox placement - use [[cold-email-deliverability]].
- ▌ Refund Deescalation · skillmedevHandles angry customers and refund requests with a validate-own-act de-escalation sequence and a refund decision matrix that weighs refund cost against customer LTV and chargeback risk. Use when someone asks "this customer is furious, what do I say", "should I approve this refund", "how do I deny a refund without losing the customer", or a conversation is emotionally charged. Do NOT use for routine, non-charged ticket responses - use support-ticket-reply instead; for diagnosing systemic patterns behind falling satisfaction scores, use csat-root-cause.
- ▌ SQL Query Optimizer 2 · 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.
- ▌ Threat Model Stride 2 · skillmedevApplies STRIDE threat modeling to a feature or system design and produces a prioritized threat table with concrete mitigations ranked by exploitability and impact. Use when someone asks "threat model this feature", "what could go wrong with this design", "is this integration safe to build", or is reviewing auth flows, new data stores, webhook receivers, file uploads, or external integrations before the code is written. Do NOT use for prioritizing scanner or pentest findings on already-shipped code - use vulnerability-triage instead; for line-by-line security review of written code, use secure-code-review.
- ▌ Usability Test Plan 2 · skillmedevPlans a usability study - research questions, realistic task scenarios with success criteria, metrics (completion rate, time on task, SEQ, SUS), a recruiting screener, and moderated vs. unmoderated guidance. Use when someone says "plan a usability test", "write task scenarios for our prototype", "how many participants do we need", or is about to put an interface or prototype in front of users. Do NOT use for open-ended discovery interview guides - use interview-guide-builder instead; for analyzing quantitative A/B experiments, use ab-test-analyzer.
- ▌ Variant Copy Scaler 2 · 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.
- ▌ Vercel Edge And Isr · skillmedevChoose a rendering, runtime, and caching strategy on Vercel - Fluid Compute as the default runtime (Edge Functions are deprecated), ISR/PPR, Next.js 16 Cache Components ('use cache', cacheLife, cacheTag, updateTag, revalidateTag), and the Vercel Runtime Cache API (getCache, expireTag, invalidateByTag) with tag-based invalidation. Use when someone asks "should this page be static or server rendered on Vercel", "how do I set up ISR in Next.js", "revalidate this page on demand", or "why is my Vercel page serving stale content" - including streaming vs PPR decisions, caching an API response across regions, and migrating off unstable_cache. Do NOT use to set env vars (use vercel-env-management), wire git/preview/promote deploys (use vercel-deploy-pipeline), route LLM calls (use vercel-ai-gateway), or block bots/rate-limit (use vercel-firewall-and-botid). For pure Core-Web-Vitals/bundle tuning, hand to next-on-vercel-perf.
- ▌ API Client Generator 2 · 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.
- ▌ Clickhouse Analytics 2 · 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.
- ▌ Component API Design · skillmedevDesign clean, composable React/Vue component APIs with accessibility built in. Use when designing or reviewing a component's props, composition, events or accessibility, or when a component API has grown hard to use.
- ▌ Contract Test Writer 2 · skillmedevWrites consumer-driven contract tests at service and API boundaries - Pact consumer tests, provider verification, broker publishing, and can-i-deploy gates - so an incompatible change fails a build instead of breaking integrations in production. Use when someone asks "how do I stop the backend breaking my client", "set up Pact between these services", "a renamed field broke a consumer that unit tests passed", or two separately deployed services must stay in sync. Do NOT use for designing a new API contract from scratch or reviewing its design - use api-design instead; do NOT use for end-to-end user-journey tests - use e2e-scenario-author instead; do NOT use for calls inside a single deployable - write a unit test.
- ▌ Customer Success Qbr 2 · 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.
- ▌ Dead Code Eliminator 2 · 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.
- ▌ Async Communication 2 · skillmedevConverts 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.
- ▌ Bloodwork Explainer 2 · skillmedevTranslates 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.
- ▌ Changelog Generator 2 · skillmedevGenerate or update a repository CHANGELOG.md in Keep a Changelog format from git history - grouping commits since the last tag into Added/Changed/Deprecated/Removed/Fixed/Security, rewriting them as user-facing entries, and recommending the semantic version bump. Use when someone asks "generate a changelog from the git log", "update CHANGELOG.md for this release", "what version bump does this release need", or "turn these commits into release notes". Do NOT use for writing benefit-first product announcement changelogs for end users from release notes - use changelog-writer instead; this skill produces the versioned CHANGELOG.md file that lives in the repo.
- ▌ Color Accessibility 3 · skillmedevAudits and repairs color palettes against WCAG contrast thresholds - 4.5:1 for body text, 3:1 for large text and UI components, 7:1 for AAA - and makes them safe for color-blind users, delivering a verified pairing table. Use when someone asks "does this color pass contrast", "make my brand color accessible", "is this palette color-blind safe", "why did my contrast check fail", or is remediating color findings from an audit. Do NOT use to invent a brand palette from scratch - use color-palette-builder instead; for a full accessibility review beyond color, use accessibility-audit.
- ▌ Content Repurposing 2 · skillmedevFans one long-form pillar asset (video, podcast episode, or article) out into 10+ platform-native atomic pieces with a derivation map - clips, quote cards, threads, LinkedIn posts, newsletter and blog sections - each recast in the target platform's register and sequenced over the week. Use when someone says "turn this video into clips", "repurpose this podcast episode", "get more mileage out of this article", or "build a distribution plan from one piece of content". Do NOT use to re-express one finished post as the native equivalent of the same asset on each channel - use cross-platform-reformatter instead; do NOT use to mechanically crop, caption, and export a finished video for social feeds - use social-video-formatter instead; do NOT use to design the ongoing pillar-and-cadence publishing system itself - use creator-content-calendar instead.
- ▌ Coverage Gap Finder 2 · skillmedevProduces a risk-ranked list of untested critical paths and branches from a real branch-coverage report crossed with git churn, naming the specific missing cases and the smallest test that buys the most safety. Use when someone says "we have 85% coverage but I don't trust it", "what should we test next", "audit the suite before this release", or "which coverage gaps actually matter". Do NOT use to prove existing assertions are strong - covered-but-unasserted lines are mutation-test-runner's job; do NOT use to pin the current behavior of legacy code before a refactor - use characterization-test-writer instead. This skill decides what to test and in what order, not how well a test asserts or how to lock down legacy.
- ▌ Debt Payoff Planner 2 · skillmedevBuilds a sequenced multi-debt payoff plan - avalanche or snowball chosen by explicit decision rules - with the rollover schedule, total-interest math, and a debt-free date. Use when someone asks "which debt do I pay first", "avalanche or snowball", "how do I get out of credit card debt", or "when will I be debt-free". Do NOT use for sizing the cash cushion that prevents new debt - use emergency-fund-planner instead; for building the monthly budget that produces the extra payment - use budget-builder; for the overall save-vs-invest-vs-payoff ordering - use financial-planner.
- ▌ Design QA Checklist 2 · skillmedevRuns an ordered design QA pass over an implemented UI - layout, type, color, states, motion, content - against the design spec, with concrete tolerances and a filed defect list. Use when someone asks "QA this build against the designs", "does the implementation match Figma", "is this ready for design sign-off", or before releasing a UI change. Do NOT use for critiquing the design itself - use design-critique instead; for a full WCAG conformance audit, use accessibility-audit; for writing the spec the build is checked against, use design-handoff-doc.
- ▌ Design Token System · skillmedevBuild a three-tier token architecture (global, semantic, component) with theming. Use when setting up design tokens, adding themes or dark mode to a design system, or untangling hard-coded colors and spacing.
- ▌ Discovery Call Prep 2 · 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.
- ▌ E2e Scenario Author 2 · skillmedevConverts an acceptance criterion or user story into one maintainable Playwright or Cypress end-to-end test that reads like the journey it covers. Use when turning a Given/When/Then acceptance criterion or user story into a browser test, when asked to "write an E2E test for this AC", or when a feature's critical journey (login, checkout, signup) needs a single automated scenario. Do NOT use when writing general Playwright tests, configuring the runner, or fixing existing test flakiness - use playwright-testing or flaky-test-detangler instead.
- ▌ Employment Contract · skillmedevReviews an employment agreement clause by clause, flags deviations from market-standard terms - non-compete scope, IP assignment breadth, cause definitions, equity mechanics - and produces a review table with recommended asks, explicitly bounded as not legal advice. Use when someone asks "can you review my offer letter", "is this non-compete normal", "what does this IP assignment clause mean", "should I push back on this severance term", or has an employment agreement in hand before signing. Do NOT use for negotiating the compensation number itself - use salary-negotiation instead - or for drafting a company's terms of service or privacy policy - use terms-of-service instead.
- ▌ Error Budget Policy 2 · skillmedevDefines and applies an SLO error-budget policy that gates feature work versus reliability work based on remaining budget. Use when setting up SLOs or when high burn rate lacks a formal team response protocol.
- ▌ Experiment Tracking 2 · 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.
- ▌ Explain Plan Reader 2 · skillmedevRead a captured EXPLAIN ANALYZE plan, name the single bottleneck node, and prescribe a targeted fix for it. Use when a specific query is slow and you have (or can capture) its execution plan from Postgres or MySQL and need to know WHICH node is burning the time and why.
- ▌ Interview Synthesis 2 · skillmedevTurns raw interview notes into themed, evidence-tagged insights via a two-pass affinity-mapping procedure, with frequency and confidence ratings and stakeholder-ready quotes. Use when someone asks "synthesize these interviews", "what themes came out of our research round", "turn these transcripts into findings", or has finished a qualitative round and needs actionable output. Do NOT use for synthesizing published papers or mixed documents - use research-synthesis instead. Do NOT use for building the personas themselves - use user-persona instead. Do NOT use for consolidating hiring-interview scorecards - use interview-debrief-synthesizer instead.
- ▌ Lesson Plan Builder 2 · 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.
- ▌ Messaging Hierarchy 2 · 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.
- ▌ Mobile Offline Sync 2 · skillmedevBuilds local-first mobile storage with an optimistic local store, durable mutation outbox, per-entity conflict-resolution rules, incremental pull, and idempotent background retry. Use when someone says "the app has to work offline", "how do I sync Room or SQLite or Realm with the server", "what happens when two devices edit the same record", or offline edits must reconcile with the server later. Do NOT use for paginating, caching, and refreshing read-heavy server lists - use pagination-and-sync-engineer instead; and do NOT build offline write support for strong-consistency operations like payments or inventory counts - disable those offline.
- ▌ Manuscript Reviser 2 · skillmedevUse when revising fiction prose that ALREADY EXISTS - a second/third-draft pass on a chapter or scene, a continuity or POV-consistency check, fixing a scene that drags, cutting dead weight, or tightening overwritten prose at the line level. Do NOT use to draft a brand-new scene from nothing (use Fiction Scene Writer), to build or mimic an author's voice (use Ghostwriter), or for neutral encyclopedic prose (use Wikipedia Style Writer); to outline or re-architect the plot at the beat level, use Story Structure Architect.
- ▌ Mock Stub Designer 2 · skillmedevDesigns the minimal set of test doubles for a unit or integration test and decides, per dependency, whether to stub, fake, spy, mock, or exercise the real thing. Use when someone asks "should I mock this", "how do I test code that calls Stripe or S3 or the clock", "why do our tests pass while production is broken", or when a test touches an HTTP API, payment or email/SMS SDK, database, filesystem, system clock, or randomness. Do NOT use for fabricating valid domain fixture data (a User with defaults, an Order with line items) - use test-data-builder instead; for driving a red-green implementation loop, use tdd-expert.
- ▌ Mutual Action Plan 2 · 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.
- ▌ One Pager Designer 2 · skillmedevWrites a decision-driving one-pager - problem, evidence, impact, and a specific ask compressed into a single page readable in under three minutes. Use when someone asks "turn this into a one-pager", "write a brief for leadership", "I need a one-page pitch for this decision", or is preparing a document a busy reader must act on from one page. Do NOT use for a client-facing sales proposal with pricing and scope - use sales-proposal-writer instead; for condensing an existing long document use executive-summary; for multi-slide narratives use slide-deck-builder.
- ▌ Playwright Testing 2 · skillmedevWrites and reviews end-to-end Playwright tests that survive UI refactors and never fail on timing - resilient locators, web-first assertions, isolated state, and a flake policy with quarantine rules. Use when someone asks "write a Playwright test for this flow", "why is this e2e test flaky", "how do I wait for this element", "what selector should I use", or is setting up a Playwright suite and CI config. Do NOT use for consumer/provider contract tests of API boundaries - use contract-test-writer instead; for turning product requirements into an e2e scenario inventory before any code - use e2e-scenario-author instead; for systematically diagnosing an already-flaky suite - use flaky-test-detangler instead; for designing reusable test fixtures and factories - use test-data-builder instead.
- ▌ Rate Limit Handler 2 · 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.
- ▌ Redline Annotation 2 · skillmedevProduces precise redline annotations - spacing, sizing, type, color, radius, z-order, and behavior notes in a consistent, scannable notation - that engineers can build from without asking questions. Use when someone asks "redline this screen", "spec this component", "annotate the spacing for handoff", or is preparing design files for development. Do NOT use for the overall handoff document with flows, edge cases, and acceptance criteria - use design-handoff-doc instead; for animation timing and easing, use motion-spec; for breakpoint behavior, use responsive-spec.
- ▌ Salary Negotiation 2 · skillmedevPrepares and scripts salary and job-offer negotiations - market research, target/minimum/anchor numbers, BATNA strength, deflection and counter scripts, and total-compensation trades when base is capped. Use when someone asks "how do I negotiate my offer", "they asked my salary expectations, what do I say", "is this offer low", or "how do I counter without losing the offer". Do NOT use for writing resumes, cover letters, or managing the application pipeline - use job-application instead; for declining an offer gracefully, see offer-rejection-writer.
- ▌ Secure Code Review 2 · skillmedevReviews code for the security flaw classes that cause the most breaches - broken authorization and IDOR, injection, SSRF, mass assignment, and unsafe deserialization - and returns a short, focused findings list with concrete fixes. Use when someone asks "review this code for security issues", "is this endpoint safe", "check this PR for vulnerabilities", or is shipping auth logic, new API endpoints, file handling, or anything that touches untrusted input. Do NOT use for general code quality, style, or maintainability review - use code-review-checklist instead; for prioritizing findings a scanner already produced, use vulnerability-triage; for design-stage analysis before code exists, use threat-model-stride.
- ▌ Series A Readiness 3 · skillmedevAudits whether a seed-stage company clears the Series A bar - benchmark metrics, narrative, team, and data room - and produces a red/yellow/green readiness scorecard with a 90-day gap-closing plan. Use when a founder asks "am I ready for Series A", "what metrics do I need to raise an A", "what goes in a Series A data room", "should I raise now or wait two quarters", or is deciding when to open an A process. Do NOT use for a general pre-pitch hygiene check at any stage - use fundraise-readiness-audit instead - or for choosing which round to raise at all - use fundraising-stage-selector instead.
- ▌ Skill Pack Curator 2 · skillmedevDesigns the membership and structure of a skill pack - persona, member selection, install sequence, cross-links, and what to add or cut. Use when someone asks "which skills should go in this skill pack", "design the membership of a new skill pack", "decide which skills to add or cut from a pack", or is turning a vertical (an industry or role) into a coherent bundle. Do NOT use to grade or rewrite a finished pack to a quality bar (use skill-auditor) - this designs composition.
- ▌ Slide Deck Builder 2 · skillmedevStructure a persuasive slide deck - narrative arc, one-idea-per-slide discipline, and headlines written as takeaways not labels. Use when building any presentation that must move an audience to a decision.
- ▌ Stakeholder Update 2 · skillmedevWrites project stakeholder updates readable in under 60 seconds - honest RAG status, decisions made, explicit asks with owners and dates, next milestones - tiered to the audience. Use when someone asks "write my weekly project update", "how do I tell stakeholders we're at risk", "draft a status email for leadership", or "my updates get ignored, fix the format". Do NOT use for aggregating many teams' statuses into one engineering-wide report - use eng-status-rollup instead. For monthly investor letters with metrics and asks to VCs, use investor-update-writer; for customer-facing incident status, use status-page-update.
- ▌ Status Page Update 2 · skillmedevWrites customer-facing incident status updates for each lifecycle stage - investigating, identified, monitoring, resolved - with cadence rules and plain-language templates. Use when someone asks "write a status page update", "what do we tell customers about this outage", "draft the resolved notice", or during an active incident needing customer communication. Do NOT use for the internal post-incident analysis - use postmortem-writer once the incident is closed; for deciding severity and internal escalation flow use sev-triage; for summarizing an incident upward to executives use escalation-summary.
- ▌ Stock Photo Finder · skillmedevSource the right stock photograph for a brief by picking the best library and crafting the search. Use when you need a real photo or image for a hero, blog post, ad, slide, mockup, social post, or thumbnail and you are not sure where to look or what to search, or when someone says "find me a photo of...", "where do I get images for this", "I need a hero image", or "good free stock photos for X". It covers free libraries (Unsplash, Pexels, Pixabay), curated and boutique sources (Stocksy, Stills, Death to Stock), broad paid catalogs (Adobe Stock, Shutterstock, iStock), and editorial archives (Getty, AP, Reuters). Do NOT use to decide whether a license actually permits your use or whether you need a release -> use image-license-rights; do NOT use to fetch images programmatically in code -> use stock-photo-api; do NOT use to art-direct a cohesive set or fix a cliched look -> use visual-asset-curation.
- ▌ Stripe Integration · 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.
- ▌ Zone 2 Cardio Plan 2 · skillmedevUse when someone asks to build a steady-state cardio plan, train an aerobic base or Zone 2, structure easy or endurance weekly cardio, train by heart-rate zones, or improve resting heart rate, VO2, or endurance. Builds a heart-rate-zone aerobic training block with session structure, modality choice, and progression. General fitness guidance, not medical advice. Do NOT use to design a strength or lifting program (use Strength Training Plan), high-intensity interval conditioning, HIIT, or circuits (use Conditioning & HIIT Program), or a mobility/flexibility routine (use Mobility Routine).
- ▌ Ad Creative Testing 2 · skillmedevDesigns 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.
- ▌ Agent Orchestration 2 · 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.
- ▌ Vercel AI Gateway 2 · skillmedevRoute every LLM call through one unified API on Vercel - plain "provider/model" strings via the AI SDK, automatic provider routing and model fallbacks, observability and per-key cost tracking, and zero data retention. Use when you ask "how do I add an LLM to my Vercel app", "route OpenAI and Anthropic through one API", "add model failover / fallback", "track LLM cost and spend on Vercel", "set a budget per API key", "switch providers without changing code", "AI_GATEWAY_API_KEY", or "stop installing @ai-sdk/openai and @ai-sdk/anthropic separately". Do NOT use for general AI SDK app code (chat UI, tool calling, structured output) - that is the AI SDK itself; do NOT use for deploy config, env wiring, or edge/runtime choice - use vercel-deploy-pipeline, vercel-env-management, and vercel-edge-and-isr instead; do NOT use to rate-limit or block abusive AI traffic - use vercel-firewall-and-botid; and do NOT use for app-level latency/caching tuning of the route - use next-on-vercel-perf.
- ▌ Video Hook Writer 2 · skillmedevWrites the spoken line plus visual frame combination for the first 3 seconds of a short-form video, delivering labeled variants built from six proven hook formulas and matched to TikTok, Reels, or Shorts. Use when someone says "write a hook for this video", "my Shorts die in the first seconds", "give me openers for this TikTok", or "how should this Reel start". Do NOT use for the first line of a written post, thread, or caption - use social-hook-generator instead; do NOT use to build the full thread after the opener - use tweet-thread-builder instead; do NOT use for the 30-second intro of a long-form YouTube video - use youtube-script-writer instead; do NOT use to design the clickable image for a video - use thumbnail-concept instead.
- ▌ Win Back Campaign 2 · skillmedevDesigns segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says "our users went quiet", "design a win-back campaign", "how do I re-engage lapsed customers", "should we email people who haven't logged in for months", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.
- ▌ Apollo Prospecting 2 · skillmedevUse 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 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 intent data", "how do I prospect in Apollo". Do NOT use for designing the ICP (use [[icp-persona-builder]]), writing email copy (use [[cold-email-craft]]), SPF/DKIM/DMARC deliverability (use [[cold-email-deliverability]]), or reading funnel metrics (use [[prospecting-metrics]]).
- ▌ Audience Targeting 2 · skillmedevBuilds 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.
- ▌ Case Study Builder 2 · skillmedevTurn a customer win into a credible case study - interview-driven raw material, a challenge-solution-results arc, and a quantified results section with real customer quotes. Use when someone asks "write a case study from this customer call", "turn this win into a customer story", "what should I ask the customer in the interview", or "make our results section stronger". Do NOT use for collecting short standalone quotes or review snippets - testimonial capture is upstream raw material for this skill. Do NOT use for packaging finished case studies into battlecards and sales collateral - use sales-enablement-kit instead.
- ▌ Cash Flow Forecast 2 · 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.
- ▌ Customer Analytics 2 · skillmedevTurns transaction data into cohort retention, lifetime value, RFM segments, and churn predictions tied to concrete actions. Use when someone asks "what's our customer LTV", "build a cohort retention table", "which customers are about to churn", "how do repeat purchase rates look by cohort", or "who should we target with a win-back offer". Do NOT use for event-level product usage and feature adoption analysis - use product-analytics instead; for defining market segments for positioning and messaging - use segmentation-strategy instead; for designing the interventions that reduce churn once at-risk customers are identified - use churn-reduction instead; for step-by-step conversion drop-off - use funnel-analysis instead.
- ▌ Data Drift Monitor 2 · 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.
- ▌ Design Handoff Doc 2 · skillmedevWrites a complete design handoff document covering components, design tokens, interaction states, and edge cases for engineering implementation. Use when handing off a feature or screen to developers.
- ▌ Email Drip Builder 3 · skillmedevDesigns automated onboarding and activation drip sequences with behavior-gated sends, exit triggers on conversion, and per-email jobs and timing. Use when someone asks "build an onboarding email sequence", "design a drip campaign for new signups", "why isn't our onboarding flow activating users", or is extending an existing drip series. Do NOT use for recurring content newsletters - use email-newsletter-pro; for recovering abandoned checkouts use abandoned-cart-sequence; for re-engaging dormant users use win-back-campaign; for cold outreach to prospects use outreach-sequence-designer or cold-email-craft.
- ▌ Escalation Summary 2 · skillmedevWrites a tight escalation summary to engineering or management with a one-line headline, quantified customer impact, repro steps, prior attempts, and a single clear ask. Use when someone says "I need to escalate this ticket", "write this up for engineering", "this bug needs eng eyes", or a support issue must leave the queue for specialist action. Do NOT use for replying to the customer - use support-ticket-reply instead; do NOT use for assigning incident severity and coordinating an active outage - use sev-triage instead; do NOT use for the after-the-fact incident writeup - use postmortem-writer instead.
- ▌ Framework Upgrader 2 · 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.
- ▌ Hashtag Strategist 2 · 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.
- ▌ Help Documentation 2 · skillmedevWrites user-facing help-center articles - verb-first how-to guides, symptom-organized troubleshooting pages, and FAQs - with one task per article, exact UI labels, and a stated success result. Use when someone asks "write a help article for...", "document how users reset their password", "turn these support tickets into a troubleshooting page", or "our help center articles are confusing, rewrite this one". Do NOT use for internal team procedures and SOPs - use process-doc instead; for on-call operational runbooks, use runbook-writer; for internal knowledge-base articles aimed at support agents, use kb-article-writer.
- ▌ Jira Ticket Writer 3 · skillmedevWrites ready-to-build Jira stories with user-story summaries, Given/When/Then acceptance criteria, subtasks, and story-point guidance, checked against INVEST and a Definition of Ready. Use when someone asks "write a Jira ticket for this", "turn these meeting notes into a story", "are these acceptance criteria testable", "should I split this story", or "how many points is this". Do NOT use for configuring Linear teams, cycles, labels, or triage workflows - use linear-workflow instead. For deciding what fits in the sprint, use sprint-planning.
- ▌ Kinetic Typography 2 · skillmedevPut text in motion the right way - title cards, animated captions, lower-thirds, callouts, and word-by-word reveals - with a reading-time-per-word budget so copy holds long enough to read, plus enter/exit timing, weight and size transitions, and type hierarchy in motion. Use when someone asks to "animate this text", "make a title card", "animated captions/subtitles", "kinetic typography", "animate the headline", "lower-third", "word-by-word reveal", "text that pops in", or "how long should this line stay on screen". Do NOT use when the question is the cut, pacing, or easing curve of non-text motion - use motion-design-principles instead; do NOT use to plan which scenes or shots exist - use video-storyboard instead; do NOT use to resize or crop a caption track for a specific platform (9:16 TikTok, 1:1 feed) - use social-video-formatter instead; do NOT use for the color, contrast, or lighting of the type against its background - use motion-color-and-light instead.
- ▌ Longevity Protocol 2 · skillmedevAssembles an evidence-tiered weekly longevity routine across the four pillars with the strongest healthspan data - sleep, zone 2 aerobic work, strength training, and dietary pattern - plus stress and connection, delivered as a filled weekly template with honest evidence labels. Use when someone asks "build me a longevity routine", "what actually extends healthspan", "audit my health habits", or "is this supplement stack worth it". General wellness guidance, not medical advice. Do NOT use to program the individual pieces in depth - use zone-2-cardio-plan for the aerobic block, strength-training-plan for lifting, sleep-optimizer for sleep, nutrition-planner for macros; for HIIT/conditioning use fitness-program; for interpreting labs use bloodwork-explainer.
- ▌ Literature Review 2 · 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.
- ▌ Logo Brief Writer 2 · 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.
- ▌ Model Card Writer 2 · 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.
- ▌ Moodboard Builder 2 · 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.
- ▌ N Plus One Hunter · skillmedevDetect ORM loop-of-queries (N+1) patterns from query logs and eliminate them with batched eager loading, keeping the N+1s that are cheap. Use when a list endpoint is slow, a request issues many near-identical SELECTs differing only by an id, query logs show repeated SELECTs in a loop, or a tool like the bullet gem flags an N+1 in ActiveRecord, Prisma, SQLAlchemy, or Hibernate.
- ▌ Networking System 2 · skillmedevBuilds a repeatable professional networking system - a tiered contact tracker, give-first outreach and reconnect scripts, a follow-up cadence by tier, and a weekly relationship-hour routine - so staying in touch stops depending on willpower. Use when someone says "help me network for my job search", "how do I reach out to someone I admire", "I'm bad at keeping in touch with contacts", or wants a lightweight personal CRM habit. Do NOT use for sales prospecting sequences - use outreach-sequence-designer instead; for personalizing recruiting outreach, use candidate-outreach-personalizer.
- ▌ Nextjs 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.
- ▌ Nutrition Planner 2 · skillmedevSets personal nutrition targets - protein at 1.6-2.2 g/kg, a calorie budget from goal and activity, fiber and hydration floors - and a repeatable meal structure with a review-and-adjust protocol for fat loss, muscle gain, or maintenance. Use when someone asks "how much protein should I eat", "set my macros for a cut", "why has my weight stalled", or "build me a sustainable diet framework". General wellness guidance, not medical advice. Do NOT use to produce a specific week of recipes with a shopping list and prep schedule - use meal-planner instead (this skill sets the targets; meal-planner cooks to them); for the broader multi-pillar health routine, use longevity-protocol.
- ▌ Objection Handler 2 · 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.
- ▌ Partition Planner · skillmedevProduces a partitioning or sharding plan for an oversized table - range/list/hash strategy, partition-key choice, composite-key and pruning constraints, and a verdict on whether to partition at all. Use when one table has grown past tens of millions of rows or hundreds of GB, vacuum/autovacuum on it runs for hours, retention deletes are giant DELETEs, or you are deciding between range/list/hash partitioning or sharding a hot table. Do NOT use when the goal is choosing indexes for specific slow queries - use index-advisor instead.
- ▌ Postmortem Writer 2 · skillmedevWrites blameless incident postmortems with a log-reconstructed timeline, multi-causal contributing factors, and owned, dated action items. Use when someone asks "write the postmortem for yesterday's outage", "run a blameless retro on this incident", "turn these incident notes into a postmortem doc", or after any SEV1 or SEV2 event. Do NOT use for customer-facing incident updates while the incident is live - use status-page-update instead; for transferring context at a shift change, use oncall-handoff; for classifying and running a live incident, use sev-triage.
- ▌ Product Analytics 3 · skillmedevStands up product analytics from decision questions backward - a north-star metric with an input-metric tree, an object-action event taxonomy with a governed tracking plan, and the priority analyses to build first: activation funnels, cohort retention curves, and feature adoption correlated with retention. Use when someone asks "what events should we track", "set up our analytics taxonomy", "where do users drop off before first value", or "what's our activation moment". Do NOT use for growth-accounting decompositions of MAU changes - use growth-accounting instead - or for deep funnel diagnosis on existing data - use funnel-analysis instead.
- ▌ Serp Gap Analyzer 2 · skillmedevCompares a draft or outline against the pages already ranking for its target query and outputs the missing subtopics, entities, and questions as a prioritized gap table - each gap classified must-have, differentiator, or skip. Use when someone asks "compare my draft against the top ranking pages", "what is my draft missing compared to the pages that rank", "run a content gap analysis on my draft", or has a target query plus 3-5 ranking URLs and wants to close coverage gaps before publishing. Do NOT use for a page that already ranks and is decaying over time - use content-refresh-auditor. Do NOT use for rewriting sections into citable answer blocks for AI engines or featured snippets - use aeo-answer-blockifier. Do NOT use for grouping a keyword list into page-level topics - use keyword-cluster-builder.