skills/landing-page-copy/SKILL.md
Write full landing-page copy that converts — section by section. Use when asked to write a landing page, homepage copy, a product page, or copy for a marketing site. Produces complete copy for every section (hero, problem, solution, social proof, features-as-benefits, objections/FAQ, final CTA) with a clear single conversion goal and one primary call to action.
npx skillsauth add mohitagw15856/pm-claude-skills landing-page-copyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A landing page has one job: move a specific visitor to one action. Most pages bury the value, hedge the ask, and talk about themselves. This skill writes the whole page section-by-section around a single conversion goal — leading with the visitor's problem and the outcome, proving it, handling objections, and asking once, clearly.
Ask for these only if they aren't already provided:
value-proposition).Write copy (not just guidance) for each section:
1. Hero — a benefit-led headline (the outcome, not the feature), a one-sentence subhead that adds the how/for-whom, and the primary CTA button text. Offer 2 headline options.
2. Problem — name the visitor's pain so they feel understood (2–3 lines). Earns the read.
3. Solution — how you solve it, framed as their outcome. Lead with the transformation.
4. Social proof — placement + example copy for testimonials/logos/metrics (the strongest goes highest).
5. Features → benefits — 3–5, each as benefit headline + one line of how. Never a bare feature.
6. Objection handling / FAQ — the 3–5 real reasons they'd hesitate (price, trust, effort, fit), answered honestly.
7. Final CTA — restate the core benefit and repeat the same one ask. Add the risk-reducer (free trial, no card, guarantee).
Microcopy notes — button text (action + value, not "Submit"), and the one distraction to remove.
Conversion-copywriting practice — single conversion goal, problem-led structure, benefit-framing, objection handling, LIFT-style clarity.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.