Claude Skills by SkillMedev

Designs 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 ...

Produces 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 ...

Produces 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 vi...

Writes 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...

Designs 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 fe...

Writes 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 Short...

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

Verifies that every citation is real, unretracted, and complete, rates source quality by evidence tier, and formats reference lists precisely in APA, MLA, Chicago, or IEEE. Use when someone asks "check my references", "format this bibliography in APA", "are these citations real", or "convert my reference list to IEEE". Do NOT use for checking whether the claims in the text are true - use fact-checker or claims-verifier instead. Do NOT use for writing the review itself - use literature-review ...

Verifies discrete factual claims against multiple independent sources and returns a calibrated verdict - Verified, Likely true, Likely false, Unverifiable, or False - with confidence and citations. Use when someone asks "is this true", "fact-check this claim", "did X really happen", "verify this statistic before we publish", or pastes a quote, number, or viral post to check. Do NOT use for tracing a citation chain back to its primary origin and appraising study methodology - use claims-verifi...

Produces 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 synth...

Writes a concise, evidence-based policy brief - problem, options compared on consistent criteria, and a recommendation - that a decision-maker can act on in minutes. Use when someone asks "write a policy brief", "summarize the evidence and options for this decision", "brief the minister/board/council on X", or needs a one-to-four-page document that turns research into a recommended action. Do NOT use for persuasive opinion pieces - use op-ed-writer instead; for long-form marketing documents, ...

Runs a PRISMA-compliant systematic review from PICO question and pre-registered protocol through search strings, two-stage screening, risk-of-bias appraisal, and GRADE-rated synthesis. Use when someone asks "run a systematic review", "build my search strategy and inclusion criteria", "screen these studies against a protocol", or "meta-analyze the evidence on X". Do NOT use for a thematic narrative review of a field without a registered protocol and exhaustive search - use literature-review in...

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

Writes pinning and characterization tests that lock in the current behavior of untested legacy code - bugs included - before a refactor, so any later behavior change trips an alarm. Use when someone says "I need a safety net before refactoring this", "this module has no tests and I have to change it", "capture what this function does today", or the correct behavior is simply whatever the code does now. Do NOT use for writing tests for new behavior built red-green - use tdd-expert instead; do ...

Proves 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.

Audits 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-tria...

Drives 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.

Ports a codebase across a breaking language or runtime version with compatibility shims, batched automated transforms, dual-runtime CI, and old-vs-new output diffing, ending in a flag-flip cutover with a rollback rule. Use when someone says "migrate us from Python 2 to 3", "we're jumping Node majors", "move to the next Java LTS", or any runtime upgrade where source must change to keep compiling or behaving correctly. Do NOT use for an application framework's major version (React, Rails, Sprin...

Finds 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 com...

Produces an incremental migration plan that runs a legacy and a new system side by side behind a routing seam, slicing and sequencing whole capabilities so the old system stays live until its last route is cut. Use when planning to replace or rebuild a large, business-critical system that must keep serving traffic throughout. Do NOT use when extracting a single service from a still-living monolith - use monolith-decomposer instead; for generic non-migration implementation planning, use the pl...

Drive development with strict Red-Green-Refactor discipline - write one failing test, write the minimum code to pass it, refactor on green - including test-list planning and a worked kata cycle. Use when someone asks "write this test-first", "do TDD on this feature", "help me practice red-green-refactor", "write a failing test for this bug", or wants tests to drive a new module's design. Do NOT use for adding tests to existing untested legacy code before a refactor - use characterization-test...