SkillMedev
- 361 skills
- 0 followers
- 1 day ago last updated
- ▌ Show Notes Writer · skillmedevProduces complete podcast show notes from a transcript or episode outline - a standalone summary block, timestamped chapters that name what happens, screenshot-worthy key takeaways, guest bio, curated links, and keyword placement for search. Use when someone says "write show notes for this episode", "turn this transcript into an episode description", "add chapters and timestamps", or "make this episode findable on Google". Do NOT use to fan the episode out into clips, quote cards, and social posts - use content-repurposing instead; do NOT use to write burned-in video captions from the transcript - use captions-from-transcript instead; do NOT use to pitch the show to other podcasts - use podcast-pitch instead.
- ▌ Thumbnail Concept · skillmedevProduces three distinct high-CTR YouTube thumbnail concepts per video - each a full spec with focal point, precise facial-expression direction, text overlay copy, color and background direction, and two paired title variants. Use when someone says "I need a thumbnail idea", "why is my CTR low", "help me pick a thumbnail and title", or is planning a video before filming and wants the click package designed first. Do NOT use for the spoken and visual opening seconds of the video itself - use video-hook-writer instead; do NOT use to write the full video - use youtube-script-writer instead; do NOT use for cropping, captioning, or exporting finished video files - use social-video-formatter instead.
- ▌ Video Hook Writer · 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.
- ▌ Content Repurposing · 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.
- ▌ Youtube Script Writer · skillmedevWrites retention-engineered long-form YouTube scripts on a hook/body/payoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says "script my next video", "my retention graph dies at the start", "tighten this draft", or "outline a video on X". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.
- ▌ Webinar Funnel Builder · skillmedevDesigns a complete webinar funnel - registration page promise, reminder email sequence timed against typical 35-45 percent show-up rates, webinar structure with a 70 percent teach / 30 percent offer split and the pivot script, replay window and urgency rules, and the post-webinar email sequence - with a funnel-metrics table of benchmark ranges. Use when a user says "help me build a webinar funnel", "our webinar show-up rate is terrible", "how do I structure the webinar so the pitch doesn't feel gross", "what emails should go out before and after the webinar", or "how long should the replay be available". Do NOT use for one-to-one sales demo calls - use demo-script instead - for general nurture sequences unattached to an event - use email-drip-builder instead - or for standalone landing page copywriting - use landing-page-copy instead.
- ▌ Creator Content Calendar · skillmedevDesigns a sustainable publishing system for a solo creator - 3-4 content pillars, a cadence set at the creator's consistent floor, a fixed pillar rotation, a 30-day idea bank, and a monthly audit loop - delivered as a weekly calendar skeleton. Use when someone says "help me plan my content", "I keep falling off my posting schedule", "I'm launching a channel, what should my cadence be", or "audit my stalled content strategy". Do NOT use for a brand or social team's multi-platform posting grid with per-channel cadences and campaign dates - use social-content-calendar instead; do NOT use to fan one finished pillar piece into derivatives - use content-repurposing instead; do NOT use to write the individual posts or scripts - use youtube-script-writer or linkedin-post-writer instead.
- ▌ Churn Reduction · skillmedevDiagnoses SaaS churn root causes through cohort analysis and a seven-category taxonomy, then builds segmented intervention playbooks ranked by frequency, revenue at stake, and addressability - including save-offer economics. Use when someone asks "why is our churn so high", "build a churn reduction plan", "should we offer discounts to cancelling customers", or when NRR/GRR is slipping and the team needs a diagnosis before prescriptions. Do NOT use for gym or fitness-studio member retention - use retention-and-churn-killer instead. Do NOT use for re-acquiring customers who already left - use win-back-campaign instead. Do NOT use for growing existing accounts - use expansion-revenue instead.
- ▌ Csat Root Cause Analysis · skillmedevAnalyzes CSAT and NPS verbatims to surface root-cause themes and prioritize fixes by frequency and impact. Use when interpreting customer satisfaction data to inform product or process decisions.
- ▌ Knowledge Base Article Writer · skillmedevTurns a resolved support ticket into a clear, searchable knowledge-base or help center article. Use when someone asks "write a KB article from this resolved ticket", "turn these resolved tickets into help center articles", or "write an internal knowledge base article for our support agents" - converting ticket resolutions into self-service documentation that deflects future tickets. Do NOT use for writing user-facing how-to guides from scratch - use help-documentation instead.
- ▌ Escalation Summary · 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.
- ▌ Refund And De Escalation · 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.
- ▌ Support Ticket Reply · 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.
- ▌ Support Macro Library · skillmedevDesigns a reusable macro and canned-response library that stays human and on-brand. Use when building, auditing, or expanding a support team's template playbook.
- ▌ Data Table Design · skillmedevDesigns presentation tables that read correctly at a glance - numeric alignment, consistent precision, deliberate sort order, unit-labeled headers, and well-placed totals - and delivers a before/after redesign of the reader's table. Use when someone asks "make this table more readable", "how many decimals should I show", "should totals go at the top or bottom", "this report table is a mess", or is preparing tabular data for an exec deck or published report. Do NOT use for designing database tables, keys, and normalization - use database-schema instead; for narrative structure around the numbers - use data-story instead; for assembling the full multi-section document - use formatted-report-writer instead.
- ▌ Executive Summary · skillmedevCompresses long reports, memos, and analyses into a decision-ready one-page summary (250-350 words) - bottom line up front, 3-5 evidence-backed key findings, a specific owned-and-dated recommendation, risks with mitigations, and the exact decision or resource being requested - plus a separate list of unverifiable claims to probe. Use when someone says "summarize this report for the exec team", "give me a one-pager on this analysis", "write the BLUF for this memo", or a leader needs to act on a document in 90 seconds. Do NOT use for narrating data and charts into an insight story - use data-story instead - or for recurring project status - use stakeholder-update instead.
- ▌ One Pager Designer · 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.
- ▌ Slide Deck Builder · 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.
- ▌ Formatted Report Writer · skillmedevProduces long-form business and consulting reports with a standalone executive summary, three-level heading hierarchy, and skimmability rules that let a busy reader navigate in under two minutes. Use when someone asks "write up this analysis as a report", "structure my strategy brief", "turn these findings into a client deliverable", or "make this document skimmable for executives". Do NOT use for presenting user-research findings to a product team - use research-readout instead; for a one-paragraph-to-one-page condensation of an existing document, use executive-summary; for slide-based delivery, use slide-deck-builder; for academic papers, use academic-essay.
- ▌ Document Template System · skillmedevBuilds a maintained library of reusable document templates for a team - frequency-based selection, four-part template anatomy, style and naming conventions, and a quarterly maintenance protocol. Use when someone asks "set up document templates for my team", "our docs are all formatted differently", "create a standard template for status reports or proposals", or "how do we keep templates from going stale". Do NOT use for designing Notion databases and their properties - use notion-database instead. For writing one specific process document rather than a template system, use process-doc; for visual brand rules, use brand-guidelines.
- ▌ Spreadsheet Model Builder · skillmedevStructures spreadsheet models a second analyst can audit - separated input/calc/output sheets, one-formula-per-row hygiene, built-in error checks, and a documented cover sheet. Use when someone asks "how should I structure this model", "clean up this spreadsheet before the board sees it", "why does my model break when I insert a column", or is building any forecast or calculator others will review. Do NOT use for the SaaS revenue logic itself - use revenue-modeling instead; for a full FP&A operating model use fpa-model; for personal or department budgets use budget-builder; for cash timing use cash-flow-forecast; for GAAP statement construction use financial-statement-builder.
- ▌ Job Application Writer · skillmedevTailors a resume and writes a cover letter for one specific job description - mirroring JD keywords for ATS parsing, reordering bullets by relevance, quantifying impact, and reporting which JD keywords matched and which are missing. Use when someone asks "tailor my resume to this job", "write a cover letter for this posting", "will my resume pass the ATS", or shares a job description alongside their resume. Do NOT use for writing or restructuring a resume without a target job - use resume-writer instead; for critique of an existing resume, use resume-reviewer.
- ▌ Cold Email Craft · skillmedevWrite short, personalized B2B cold emails and follow-up copy - under 90 words, one ask, personalization in the first line - with good/bad contrast pairs to calibrate. Use when someone asks "write a cold email", "why is nobody replying to my outreach", "draft a follow-up sequence", "make this email shorter", or is starting founder-led outbound. Do NOT use for sending infrastructure, domains, SPF/DKIM/DMARC, warmup, or spam placement - use cold-email-deliverability instead; for multi-channel cadence architecture use outreach-sequence-designer; for building and verifying the list use prospect-list-builder.
- ▌ Networking System · 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.
- ▌ Job Interview Prep · skillmedevPrepares a candidate for a specific job interview - company research checklist, a STAR story bank mined from their resume and mapped to common competencies, a questions-to-ask bank, salary-question deflection lines, and a mock-interview loop. Use when a user says "I have an interview next week, help me prepare", "help me practice answers for this interview", "what should I ask the interviewer", "build me STAR stories from my resume", or "they're going to ask about salary, what do I say". Do NOT use for negotiating after an offer arrives - use salary-negotiation instead - and do NOT use for fixing the resume itself - use resume-reviewer instead.
- ▌ Salary Negotiation · 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.
- ▌ Cover Letter Writer · skillmedevWrites a tailored cover letter from a resume and a job posting - mirrors the posting's top three requirements with resume evidence, opens with a company-specific hook, and stays under 300 words. Use when a user says "write me a cover letter for this job", "tailor my cover letter to this posting", "here's my resume and the job ad, draft a cover letter", or "why is my cover letter not getting responses". Do NOT use for writing or improving the resume itself - use resume-writer instead - and do NOT use for overall application strategy, targeting, or tracking - use job-application instead.
- ▌ Linkedin Post Writer · 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.
- ▌ Video Storyboard · skillmedevPlan a product demo, feature announcement, or launch video as a beat sheet and shot list BEFORE animating - hook in the first 3s, problem, reveal, proof, CTA - with target duration and pacing per scene type, output as a JSON scene plan that remotion-compose consumes directly. Use when someone says "storyboard my demo", "plan the video", "what scenes do I need", "plan my launch video", "map out the demo", or "break this feature into scenes" before any code. Do NOT use when the request is the animation mechanics - writing the .tsx, using interpolate/spring, registering the Composition - that is remotion-compose; do NOT use for the easing and choreography craft of a single scene - use motion-design-principles instead.
- ▌ Kinetic Typography · 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.
- ▌
- ▌ Product Demo Director · skillmedevDirect the craft of putting a real software UI on screen - cursor choreography, zoom/pan/callout language, screen-recording vs recreated-UI, and making state changes legible with highlights, focus pulls, and slow-downs. Use when filming or recreating an app for a product demo, feature walkthrough, onboarding clip, or release reel and asking "how do I show this click", "where should the camera zoom", "should I screen-record or rebuild the UI", "why does my demo feel confusing", "how do I make the state change readable", or "how do I move the cursor". Do NOT use for the underlying motion grammar (easing, timing) - use motion-design-principles; for the beat-by-beat plan - use video-storyboard; for animating words on screen - use kinetic-typography; for the color/light of highlights and glows - use motion-color-and-light; for sound design or a click/whoosh hit - use sound-and-music-sync; for reframing the demo to 9:16 or 1:1 - use social-video-formatter; for the React/MP4 mechanics of building it - use remotion-c
- ▌ Motion Color And Light · skillmedevChoose palette, contrast, and lighting for a moving video - not a static UI - so color survives H.264/VP9 compression, banding, and YouTube/Instagram/TikTok recompression across OLED, LCD, and projectors. Use when picking video colors, building a gradient mesh, adding glow/bloom/depth, setting a dark-background default, asking "why does my gradient band", "why is my neon muddy after upload", "is this contrast video-safe", or "what palette for my video". Do NOT use when laying out scene timing or beats - use video-storyboard instead. Do NOT use for motion-easing or animation-feel decisions - use motion-design-principles instead. Do NOT use to style or animate the on-screen text itself - use kinetic-typography instead (you give it the palette, it sets the type in motion). Do NOT use to structure a product walkthrough or decide what to show - use product-demo-director instead. Do NOT use for audio, beat-matching, or scoring - use sound-and-music-sync instead. Do NOT use to re-crop or re-spec a video for a platfo
- ▌ Social Video Formatter · skillmedevReframe and export a finished video for social platforms - 9:16 ↔ 16:9 cropping, burned-in captions, a platform-native first frame, loop design, and per-platform specs (aspect, length, safe areas) for TikTok, Reels, Shorts, X, and LinkedIn. Use when someone says "make this vertical", "crop to 9:16", "format for TikTok/Reels/Shorts", "add captions/subtitles", "why is my video cut off on mobile", "resize for Instagram", or "export for social". Do NOT use when the question is about the storyboard or shot order before any video exists (use video-storyboard); the animation craft of how elements move (use motion-design-principles); animated word-by-word caption styling (use kinetic-typography); palette, contrast, or lighting (use motion-color-and-light); directing the product-demo content and screen choreography (use product-demo-director); or scoring, beat-syncing, or audio (use sound-and-music-sync) - this is the craft layer that decides WHAT to format for the feed, then hands a concrete spec to remotion-compose
- ▌
- ▌ 1 1 Agenda · skillmedevStructures recurring manager-report 1:1s with a rolling shared agenda that balances check-in, blockers, two-way feedback, and career growth instead of status updates. Use when someone asks "what should I cover in my 1:1s", "build me a 1:1 agenda template", "my 1:1s have turned into status meetings", or is setting up 1:1s with new reports. Do NOT use for general meeting agendas - use meeting-agenda instead; for writing a formal review document, use performance-review-writer; for drafting a specific piece of feedback, use feedback-writer.
- ▌ Okr Builder · skillmedevDrafts a quarter's OKRs - an inspiring qualitative objective with 3-5 measurable key results, each with a baseline, target, and owner - plus the weekly confidence check-in and end-of-quarter grading cadence. Use when someone asks "help me write OKRs", "are these key results any good", "turn our goals into OKRs for next quarter", or "how do we score our OKRs". Do NOT use for building the full-year company plan that OKRs slot into - use annual-plan instead - or for personal goal-tracking with a check-in partner - use goals-accountability instead.
- ▌ Weekly Review · skillmedevRuns a timeboxed weekly review - empty every inbox to a decision, audit every open commitment, and pick the 3-5 outcomes that define next week. Use when someone asks "walk me through a weekly review", "help me plan my week", "my task system feels stale and I don't trust it", or "I keep dropping commitments". Do NOT use for setting up the underlying capture-and-organize system itself - use gtd-system instead - or for tracking long-horizon personal goals with an accountability loop - use goals-accountability instead.
- ▌ Feedback Writer · skillmedevDrafts specific, observable, kind workplace feedback using the SBI model - Situation, Behavior, Impact - for both praise and correction. Use when someone asks "help me give feedback to a teammate", "how do I tell my report they keep missing deadlines", "make this feedback less vague", or wants to reinforce a good behavior specifically. Do NOT use for formal performance review documents - use performance-review-writer instead; for feedback on student work, use student-feedback-writer; for mediating an active interpersonal dispute, use conflict-resolution.
- ▌ Stakeholder Update · 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.
- ▌ Async Communication · 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.
- ▌ Meeting Notes To Actions · skillmedevConverts raw meeting notes or transcripts into a four-part record - a 3-5 sentence summary, the decisions actually made, an action table with owner, verb-phrased action, due date, and status, and the open questions - without inventing owners, dates, or tasks. Use when someone pastes notes and asks "pull the action items out of this", "summarize this meeting", "who owns what from this transcript", or "what did we actually decide". Do NOT use for preparing the agenda before a meeting happens - use meeting-agenda instead - or for turning extracted actions into engineering tickets - use jira-ticket-writer instead.
- ▌ Pii Scrubber · skillmedevDetects and redacts personally identifiable information from text, logs, datasets, and LLM prompts using layered pattern, checksum, and NER detection, then picks the right redaction mode for each downstream use. Use when someone asks "scrub PII from these logs", "redact personal data before sending it to the LLM", "is this dataset safe to share", or is wiring up logging, analytics, or third-party exports that might carry user data. Do NOT use for leaked API keys, tokens, or credentials - use secrets-hygiene instead.
- ▌ Secrets Hygiene · skillmedevGuides detection, emergency rotation, and prevention of leaked secrets and credentials across source code, git history, CI pipelines, logs, and infrastructure config. Use when someone says "I think I committed an API key", "a secret leaked", "scan the repo for credentials", "how should we store secrets", or is setting up secrets management for an application, CI/CD, or Kubernetes. Do NOT use for detecting or redacting personal data like names, emails, or SSNs - use pii-scrubber instead; for routine non-secret environment configuration on Vercel, use vercel-env-management.
- ▌ Secure Code Review · 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.
- ▌ Threat Model Stride · 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.
- ▌ Soc 2 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.
- ▌ Vulnerability Triage · 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.
- ▌ Dependency Risk Audit · skillmedevAudits third-party dependencies for exploitable CVEs, abandonment, license exposure, and supply-chain hygiene, and delivers a ranked findings report with a remediation order. Use when someone asks "is this package safe to add", "audit our dependencies", "npm audit is screaming, what actually matters", "can we use this GPL library", or is preparing a security review or vendor questionnaire. Do NOT use for triaging vulnerabilities in first-party code or a full CVE queue - use vulnerability-triage instead; for reviewing the code you wrote for security flaws - use secure-code-review instead; for how secrets are stored and rotated - use secrets-hygiene instead; for assembling compliance evidence - use soc2-evidence-helper instead.
- ▌ User Persona Builder · skillmedevSynthesizes interview notes, surveys, support tickets, and analytics into evidence-based user personas that drive design decisions, with every claim traced to source data. Use when someone asks "build personas from our research", "turn these interview notes into personas", "how many personas do we need", or "are our personas evidence-based". Do NOT use for sales-targeting ideal customer profiles with filterable firmographics and buying committees - use icp-persona-builder instead. Do NOT use for extracting jobs-to-be-done from research - use jtbd-extractor instead.
- ▌ Jtbd Extractor · skillmedevExtracts Jobs To Be Done from qualitative research data - job stories in the "When I…, I want to…, so I can…" form, a forces-of-progress map (push, pull, anxiety, habit), and functional, emotional, and social dimensions, each backed by verbatim quotes. Use when someone says "extract the jobs from these interviews", "run a JTBD analysis on this diary study", "why do users switch to or from us", or has transcripts and wants solution-agnostic goals rather than feature requests. Do NOT use for clustering findings into themes across a study - use interview-synthesis instead; for building persona profiles from research, use user-persona; for planning the interviews themselves, use interview-guide-builder.
- ▌ Survey Designer · skillmedevDesigns unbiased surveys - question types, Likert and frequency scales, screener-to-demographics flow, and a cognitive pilot plan - that produce trustworthy quantitative data. Use when someone says "write survey questions about X", "review my survey for bias", "how long should this questionnaire be", or wants to quantify attitudes, behaviors, or satisfaction. Do NOT use for full study design with hypotheses, sampling method, and power analysis - use primary-research instead; for qualitative interview scripts, use interview-guide-builder; for segment profiles built from the results, use user-persona.
- ▌ Research Readout · skillmedevTurns synthesized research findings into a crisp stakeholder readout - so-what up front, 3-5 confidence-tagged findings each following the finding-evidence-implication rule, and owned recommendations. Use when someone says "present these research findings", "turn this study into a readout for leadership", "our research isn't landing with the product team", or needs a deck or brief that gets findings acted on. Do NOT use for building a narrative around quantitative metrics and charts - use data-story instead; for the upstream analysis that produces the findings, use interview-synthesis or research-synthesis; for slide craft itself, use slide-deck-builder.
- ▌ Interview Synthesis · 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.
- ▌ Usability Test Plan · 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.
- ▌ Interview Guide Builder · skillmedevWrites a non-leading user-research discussion guide with warm-up flow, open core questions, an attached probe bank, time budgets, and a pre-field bias audit. Use when someone asks "write my interview guide", "what should I ask users in discovery interviews", "review my questions for leading language", or is preparing generative or evaluative user interviews. Do NOT use for hiring-loop questions with competencies and scoring anchors - use interview-question-kit instead. Do NOT use for sourcing deep domain knowledge from subject-matter experts with laddering - use expert-interview instead. To analyze the notes afterward, use interview-synthesis.
- ▌ Jd Bias Scrubber · skillmedevAudits a job description for exclusionary, gendered, age-coded, ableist, and pedigree-gatekeeping language and returns a findings table with neutral rewrites and severity. Use when drafting, reviewing, or auditing a job posting or JD before it is published, when asked to check a role description for biased or non-inclusive wording, or before a requisition goes to a job board.
- ▌ Interview Question Kit · skillmedevGenerates a structured candidate-interview question set where every behavioral (STAR) and role-specific item maps to a defined competency and ships with strong/borderline/red-flag answer anchors plus delivery notes. Use when someone asks "write interview questions for this role", "build an interview loop", "turn this rubric into questions per interviewer", or is planning a hiring interview, building a question bank, or standardizing how a panel assesses candidates. Do NOT use to consolidate completed scorecards into a hire decision - use interview-debrief-synthesizer instead; do NOT use for user-research or customer discovery interviews - use interview-guide-builder instead; do NOT use to build the competency rubric or scorecard itself - use hiring-scorecard or screening-rubric-builder instead.
- ▌ Job Description Writer · skillmedevDraft an inclusive, role-relevant, level-calibrated job posting from a hiring manager's role brief. Use when an employer is writing or revising a job description, JD, or job posting - you have a role brief, leveling rubric, or comp band and need outcome-based requirements, plain compensation/logistics, and inclusive tone. Do NOT use when tailoring a candidate's resume or cover letter to a posting - use job-application instead.
- ▌ Offer And Rejection Writer · skillmedevDrafts unambiguous candidate offer letters and respectful, legally-careful candidate rejection notes for a human to review and send. Use when you are asked to write, draft, or word an offer letter, an offer email, or a candidate rejection/decline note - or to soften, tighten, or de-risk an existing draft of one. Do NOT use when writing performance feedback for a current employee - use feedback-writer instead.
- ▌ Onboarding Plan Builder · skillmedevProduces a 30/60/90-day onboarding plan for a specific role with phased milestones, first-week setup, observable success criteria, and ramp reviews. Use when a new hire has an accepted offer or start date, or when asked to write, draft, or improve a 30/60/90 / ramp / onboarding plan for a role. Do NOT use for the structure of ongoing recurring 1:1s - use 1on1-agenda instead.
- ▌ Screening Rubric Builder · skillmedevTurn a job description into a weighted, anchored rubric for the pre-interview resume/CV screen so applicants are filtered against the same job-relevant criteria, in writing, before opinions form. Use when you have a JD and an applicant pile and need to decide who advances to interviews, set up a fair resume screen, or replace gut-feel resume sorting with a defensible filter. Do NOT use when building the interview-loop scorecard interviewers fill in during or after interviews - use hiring-scorecard instead.
- ▌ Interview Debrief Synthesizer · skillmedevConsolidates multiple interviewer scorecards into a calibrated hire/no-hire summary that foregrounds evidence, surfaces disagreement, and flags bias risks for a human panel. Use when you have collected scorecards or written feedback from a completed interview loop and need to run the debrief, calibrate divergent ratings, or produce a defensible decision write-up. Do NOT use when you are preparing questions or rubrics before interviews - use interview-question-kit instead.
- ▌ Candidate Outreach Personalizer · skillmedevDrafts short, honest recruiting outreach and InMail messages to a passive candidate, anchored on one researched, candidate-published professional fact, for a human recruiter to review and send. Use when someone asks "write an InMail to this engineer", "personalize this sourcing message", "draft outreach from this profile", or is contacting a passive candidate about a specific role. Do NOT use for sales or founder cold email to prospects - use cold-email-craft. Do NOT use for designing the multi-touch cadence, channel mix, and follow-up timing around the message - use outreach-sequence-designer. Do NOT use for writing the job description itself - use job-description-writer.
- ▌ Lead Enrichment · skillmedevTurns a raw or partial prospect list into a send-safe dataset by filling missing fields (work email, direct or mobile phone, title, firmographics, technographics) through a per-field provider waterfall, verifying every email, and stamping freshness. Use when someone says "enrich this list", "find the email for these people", "verify these emails before we send", "what do I do with catch-all domains", "this list is a year old, is it still good", "dedupe and clean this CSV", or "why is my bounce rate spiking". Do NOT use for selecting WHO to target and building the list itself - use prospect-list-builder. Do NOT use for tool-specific credit mechanics and filter syntax - use apollo-prospecting. Pair with cold-email-deliverability for the inbox-protection side of verification.
- ▌ Apollo Prospecting · 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 Apollo filters and saved-search alerts, and running multi-step Apollo Sequences. Trigger on "Apollo", "Apollo.io", "set up Apollo filters", "Apollo saved search", "Apollo list", "Apollo sequence", "find emails in Apollo", "Apollo credits", "export from Apollo to my CRM", "Apollo Chrome extension", "Apollo intent data", "how do I prospect in Apollo". This skill assumes the strategy is already done in the methodology skills and shows how to operationalize it in Apollo. Do NOT use for designing the ICP itself - use [[icp-persona-builder]]. Do NOT use for writing the actual email copy - use [[cold-email-craft]]. Do NOT use for fixing domain authentication / SPF / DKIM / DMARC - use [[cold-email-deliverability]]. Do NOT use for reading funnel metrics conceptually - use [
- ▌ Icp Persona Builder · skillmedevTurns a vague "who we sell to" into a weighted, filterable ICP scorecard - firmographics, technographics, and time-bound triggers expressed as literal Apollo or Sales Navigator filter values, built from closed-won and churned evidence, with hard disqualifiers and A/B/C account tiering - plus a buying-committee persona map covering economic buyer, champion, technical user, and blocker with each role's pains. Use when standing up outbound - FIRST, before any list-building or outreach - and someone asks "who is our ICP", "what filters do I put in Apollo", "we're targeting everyone and closing no one", or "score this account against our ICP". Do NOT use for pulling the actual prospect list - use prospect-list-builder instead - or for the messaging one-liner - use positioning-statement instead - or for end-user research personas - use user-persona instead.
- ▌
- ▌
- ▌
- ▌ Cold Email Deliverability · skillmedevSets up and protects cold-outbound sending infrastructure - dedicated lookalike domains, SPF/DKIM/DMARC authentication, 2-4 week mailbox warm-up, 30-50 sends/day per-mailbox caps, and continuous bounce/complaint monitoring, with a runnable DNS audit script. Use when someone says "my emails are going to spam", "set up cold email infrastructure", "warm up a new domain", "configure SPF DKIM DMARC", "how many cold emails can I send per day", or "my domain got blacklisted". Do NOT use for protecting an opted-in marketing or transactional program on your primary domain - use email-deliverability instead; do NOT use for writing the email copy - use cold-email-craft instead; do NOT use for designing the multi-step cadence - use outreach-sequence-designer instead; do NOT use for sizing the list - use prospect-list-builder instead.
- ▌ Outreach Sequence Designer · skillmedevUse when you need to design the cadence/sequence structure that moves a cold prospect to a booked meeting across multiple channels - the orchestration of touches, not the copy of any one message. Trigger phrases "design an outreach sequence", "build a cold cadence", "how many touches should my sequence have", "multi-channel sequence", "what's a good follow-up cadence", "set up day-by-day steps", "how long should my sequence be", "add LinkedIn and calls to my email sequence", "design a breakup email sequence", "what's the spacing between touches". Workflow chooses channels and mix, sets length and step spacing, defines bump/follow-up logic, matches personalization tier to account tier, wires the "why now" signal hook, varies the message angle across steps, and sets exit/branch criteria. Do NOT use for writing the words of a single email - use [[cold-email-craft]]. Do NOT use for who to put in the sequence - use [[prospect-list-builder]]. Do NOT use for building the sequence inside a tool - use [[apollo-prospec
- ▌ Sev Triage · skillmedevClassifies incident severity (SEV1-4) using impact, scope, and urgency signals and decides who to page. Use when an alert fires or a report comes in and a severity call must be made quickly.
- ▌ Alert Tuning · skillmedevReduces alert noise by making alerts actionable, symptom-based, and tied to SLOs. Identifies and kills flappy, duplicate, and cause-based alerts. Use when alert fatigue is degrading on-call response quality.
- ▌ On Call Handoff · skillmedevProduces a complete on-call shift handoff note - shift summary, open incidents, watch items with paging thresholds, silenced alerts, in-flight changes, and escalation contacts - checked against a completeness checklist. Use when someone asks "write my on-call handoff", "what should I tell the next on-call", "my shift ends in an hour, help me hand over", or "make a handoff template for our rotation". Do NOT use for writing the incident postmortem after resolution - use postmortem-writer instead. For live severity assessment during an incident, use sev-triage; for external customer-facing incident comms, use status-page-update.
- ▌ Runbook Writer · skillmedevWrites an operational runbook for a service covering symptoms, diagnostic checks, mitigations, and escalation paths. Use when shipping a new service or when an existing service lacks incident procedures.
- ▌ Postmortem Writer · 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.
- ▌ Status Page Update · 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.
- ▌ Error Budget Policy · 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.
- ▌ Crisis Comms External · skillmedevDrafts and sequences external communications during an incident or crisis - a first statement within the hour, acknowledge-what-you-know-without-speculating discipline, a single-spokesperson rule, channel sequencing from status page to email to social, and a legal-review escalation boundary, with severity-tiered statement templates. Use when a user says "we have an outage and customers are asking questions", "we had a data breach, what do we say publicly", "draft a public statement about this incident", "the story is blowing up on social, how do we respond", or "when do we need legal to review this statement". Do NOT use for routine technical status posts during normal-severity incidents - use status-page-update instead - for the internal writeup after resolution - use postmortem-writer instead - or for calming one angry customer - use refund-deescalation instead.
- ▌ Second Brain · skillmedevSets up a PARA-based second brain in any notes app (Notion, Obsidian, Apple Notes, Logseq) - Projects, Areas, Resources, Archives buckets, a frictionless universal capture inbox, weekly organizing, wiki-link and map-of-content linking, progressive summarization for recall, and maintenance rituals. Use when someone says "help me set up a second brain", "my notes are a mess and I can never find anything", "how do I organize Obsidian with PARA", or captures ideas but never uses them. Do NOT use for designing the underlying Notion database properties and relations - use notion-database instead - or for a task-management workflow - use gtd-system instead.
- ▌ Study System · skillmedevConverts a syllabus or topic list into an evidence-based study plan - material atomized into testable units, a spaced-repetition flashcard schedule with expanding intervals, active recall and Feynman-technique prompts instead of rereading, interleaved weekly sessions, and a practice-testing cadence with an error log. Use when someone says "help me study for this exam", "build me a study schedule", "I keep rereading and forgetting everything", or wants to learn a curriculum efficiently. Do NOT use for acquiring a spoken language specifically - use language-learning instead - or for building everyday habits - use habit-builder instead.
- ▌ Habit Builder · skillmedevTurns a vague intention into a one-page habit plan - a specific implementation intention, a habit-stack anchor sentence, cue-craving-routine-reward loop mapping, environment design, a never-miss-twice tracking method, and weekly review questions. Use when someone says "help me build a habit", "I want to exercise more but can't stick with it", "why do my habits keep failing", or wants to break a bad habit by removing its cues. Do NOT use for goal-setting with an accountability structure - use goals-accountability instead; for a full training program, use fitness-program.
- ▌ Decision Making · skillmedevRuns a structured decision process for high-stakes choices - reversibility classification, weighted decision matrices, expected value with explicit probabilities, pre-mortems, second-order thinking, and 10/10/10 - and produces a documented recommendation plus a decision-journal entry. Use when someone asks "should I take this job or stay", "how do I decide between these two paths", "I keep going back and forth on a big decision", or "help me think through whether to relocate". Do NOT use for evaluating a specific large purchase like a house, car, or equipment - use big-purchase-decision instead.
- ▌ Deep Work Planner · skillmedevDesigns a daily schedule that protects deep work - classifies tasks as deep or shallow, places 2-4 focus blocks of 60-120 minutes at peak energy hours, batches shallow work into fixed windows, and defines each session with a goal, definition of done, distraction plan, and first action, plus startup/shutdown rituals and a weekly scorecard. Use when someone says "I can't get any focused work done", "plan my day around deep work", "how do I stop context switching", or wants to defend calendar time for demanding work. Do NOT use for processing an email backlog - use inbox-zero instead - or for a full task-capture system - use gtd-system instead.
- ▌ Journal Framework · skillmedevDesigns a sustainable daily journaling practice - morning pages, gratitude, intention setting, evening reflection, and weekly review - matched to the user's goal, with copy-paste templates and a rotating prompt library. Use when someone asks "help me start journaling", "give me journal prompts", "I keep abandoning my journal", or "build me a morning pages routine". Do NOT use for building a general habit or streak system - use habit-builder instead; do NOT use for organizing notes and knowledge into a retrieval system - use second-brain instead; for structured end-of-week planning reviews, see weekly-review.
- ▌ Stress Management · skillmedevBuilds a personalized one-page stress toolkit - mapped triggers, three rehearsed in-the-moment interventions, a recovery menu, and prevention habits - from a week of trigger tracking. Use when someone says "I'm constantly stressed", "I can't switch off after work", "help me deal with anxiety before meetings", or "I keep snapping at people". General wellness education, not medical or mental-health treatment. Do NOT use when the primary complaint is poor sleep - use sleep-optimizer instead; for building a single recurring habit, use habit-builder; for broader life direction and goals, use life-coach.
- ▌ Goals Accountability · 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.
- ▌ Test Data Builder · skillmedevBuilds realistic domain fixtures, factories, and edge-case datasets with the builder pattern and valid defaults, so each test owns exactly the data it asserts on. Use when someone asks "how should I set up test data", "my fixtures broke half the suite", "make a factory for this model", "why is this test flaky only in CI", or a test needs domain objects, seed data, or boundary inputs. Do NOT use when a test needs to fake a network call, database client, clock, or third-party SDK - use mock-stub-designer instead; do NOT use for designing the assertions or test cases themselves - use tdd-expert instead.
- ▌ Mock Stub Designer · 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.
- ▌ Playwright Testing · 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.
- ▌ Coverage Gap Finder · 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.
- ▌ E2e Scenario Author · 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.
- ▌ Contract Test Writer · 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.
- ▌ Flaky Test Detangler · skillmedevRoot-causes intermittently failing tests and eliminates the hidden dependency at its source instead of retrying around it. Use when a test passes locally but fails in CI, goes green on a CI re-run, fails roughly one run in ten, or is already tagged "flaky." Do NOT use when the task is to design the fake or stub that replaces a real dependency - use mock-stub-designer instead.
- ▌ Mutation Test Runner · 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.
- ▌ SEO Optimizer · skillmedevAudits and rewrites a page for organic search - title and meta lengths, heading hierarchy, intent match, internal links, schema markup, and Core Web Vitals - and returns a prioritized fix list. Use when someone asks "why isn't this page ranking", "audit my page for SEO", "rewrite my title and meta description", "does this need schema markup", or before publishing a page that must earn organic traffic. Do NOT use for grouping keywords into topical clusters across a site - use keyword-cluster-builder instead; do NOT use for planning a site-wide internal-link architecture - use internal-linking-mapper instead; do NOT use for restructuring content into AI-answer-ready blocks - use aeo-answer-blockifier instead; do NOT use for deep page-speed engineering - use web-performance instead.
- ▌ Serp Gap Analyzer · 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.
- ▌ Meta Title Optimizer · 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.
- ▌ Aeo Answer Blockifier · skillmedevRewrites a section or page into concise, self-contained answer blocks that AI answer engines and search snippets can lift and cite verbatim. Use when restructuring a blog post, FAQ, docs page, or landing copy to win a featured snippet or get quoted by AI Overviews, ChatGPT, or Perplexity, or when a draft buries its answer in setup. Do NOT use for keyword research, full-article drafting, or technical/crawlability SEO - use a dedicated SEO or copywriting skill instead.