landing-page-copy 100/100

Is landing-page-copy safe to install?

SaferSkills independently audited landing-page-copy (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/landing-page-copy/SKILL.md · 1 file

skills/landing-page-copy/SKILL.md2.3 KB · Markdown

name: landing-page-copy

description: >-

Writes a high-converting landing page — hero, subhead, problem, features-as-

benefits, social proof, pricing, FAQ, and CTA. Trigger on "write my landing page",

"homepage copy", "hero section", "make my copy convert", or "I need website copy

for my startup".

When to use

When a founder needs landing-page copy that converts a cold visitor into a signup, demo request, or purchase — clear, specific, and benefit-led.

Inputs to gather

Product, ICP, and the #1 pain it kills.
The single primary action you want visitors to take (signup / demo / buy / waitlist).
Any proof: logos, metrics, testimonials, waitlist count.
Pricing (if shown) and the top objections customers raise.

Process

Hero — outcome-led headline (the after-state, not the feature) + a subhead that

names the ICP and the mechanism in one line. Lead with clarity over cleverness.

Problem — 2-3 lines mirroring the pain in the ICP's own words so they feel seen.
Features as benefits — for each top feature write "X so you can Y"; the benefit

(Y) leads. 3-5 max.

Social proof — logos, a metric ("cut resolution time 40%"), or a punchy quote.

If pre-launch, use a waitlist count or a credible founder-story line.

Pricing — anchor to value; one tier highlighted; remove risk (free trial, no card).
FAQ — answer the 4-5 objections that actually block the CTA (security, lock-in,

"why not just use ChatGPT", migration effort).

CTA — one primary action, repeated 2-3x, written as a benefit ("Start resolving

tickets free"), never "Submit".

Output

A ready-to-paste page in sections, each labeled: [HERO] headline + subhead + CTA · [PROBLEM] · [BENEFITS] (3-5 blocks) · [SOCIAL PROOF] · [PRICING] · [FAQ] (4-5 Q&A) · [FINAL CTA]. Include 2 headline variants for A/B testing.

Quality bar & pitfalls

Good = a stranger gets "what it is, who it's for, why I'd act" in under 5 seconds.
One page, one primary CTA. Specificity beats adjectives ("40% fewer tickets" >

"revolutionary").

Address the "why not just use ChatGPT/Claude?" objection head-on — point at your moat.
Avoid: feature dumps, jargon, hero that describes the company instead of the customer's win.

landing-page-copy— agent skill

Is landing-page-copy safe to install?

When to use

Inputs to gather

Process

Output

Quality bar & pitfalls

Audit the pieces. Scan the whole. Decide.