Agent skill

Landing Page GTM Copy

by ooiyeefei in ooiyeefei/ccc

Builds or rewrites SaaS landing pages by researching the real product, positioning it against alternatives and writing buyer-focused copy, then implementing it in the codebase.

MITAuto-check passedMarketing & SEO

Install Landing Page GTM Copy

skills CLI
$ npx skills add ooiyeefei/ccc --skill landing-page-gtm -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ooiyeefei/ccc landing-page-gtm --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ooiyeefei/ccc.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/landing-page-gtm .claude/skills/landing-page-gtm && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
landing-page-gtm
GitHub stars
495
Token cost
~1.8k tokens
SKILL.md length
783 words
Files
4 (incl. references)
Skills in repo
22
Repo updated
First seen
Licence
MIT

At a glance

Builds or rewrites SaaS landing pages by researching the real product, positioning it against alternatives and writing buyer-focused copy, then implementing it in the codebase.

  • Works in 6 steps: Research the Product → Competitive Positioning → Write Sales Copy → …
  • Building a new SaaS landing page or product page
  • SKILL.md covers Intake — Always Ask First, Workflow and Reference Files
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The skill starts with an intake: target URL or route, codebase path, the product or feature being sold, the buyer's role and pain, competitors, and constraints such as the design system or form provider. If the page already exists it is read first. Phase one studies the actual product, with the agent reading the code and recent git history and checking every claimed feature, reporting gaps as exists, partial or not found.

Next comes positioning: each section is framed as why this product rather than the others, without naming rivals, using a formula of the daily pain, what competitors do about it poorly and what you do differently. An anti-generic test rewrites copy that could sit unchanged on a competitor's site, for example asking what an AI-powered claim actually does. The copy phase then turns features into buyer language, with voice chosen by audience, and the work ends in frontend changes. Reference files cover copy formulas and page archetypes.

When your agent uses it

  • Building a new SaaS landing page or product page
  • Rewriting feature cards into customer-facing sales language
  • Checking that landing page claims match what the code actually does
  • Sharpening competitive positioning on a pricing or launch page

Example prompts

  • “Rewrite the feature cards on our pricing page so they sell outcomes instead of describing the tech.”
  • “Build a launch page for the new scheduling feature, and check every claim against the codebase first.”
  • “Update the hero section copy so it could not appear on a competitor's site.”

Requirements

  • Access to the product's codebase
  • A frontend project where the page lives

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Research the Product
  2. Competitive Positioning
  3. Write Sales Copy
  4. Design the Page
  5. Build and Ship
  6. Ship Checklist

What it can do on your machine

Read from SKILL.md and the folder at commit c0fd926. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Landing Page GTM Copy loads about 1.8k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 143 tokens; SKILL.md has 783 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~143
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ooiyeefei/ccc at commit c0fd926, republished under its MIT licence (© ooiyeefei). 783 words, ~1,782 tokens.

Download SKILL.mdSave it as .claude/skills/landing-page-gtm/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
landing-page-gtm
description
Build and update high-converting SaaS landing pages with GTM-aware marketing copy, competitive positioning, and sales psychology. Use when creating new landing pages, rewriting feature cards, updating marketing copy, launching product pages, or transforming technical features into customer-facing sales language. Triggers on "build landing page", "update feature cards", "rewrite marketing copy", "create product page", "launch page", "GTM", "sales copy", "competitive positioning", or when converting product features into conversion-focused web pages.

Landing Page GTM

Build conversion-focused landing pages that sell — not just describe. Combine product research, competitive positioning, sales copywriting, and frontend implementation into a single workflow.

Intake — Always Ask First

Before any work, collect these inputs:

InputQuestion
Target URL"What URL or route is this for?" (e.g., myapp.com/pricing)
Codebase path"Where's the source code?" (e.g., /home/user/project/src)
Product/feature"What product or feature is this page selling?"
Audience"Who's the buyer? (role, company size, pain level)"
Competitors"Who do they compare you against?"
Constraints"Existing design system, form provider, CTA destination?"

If the page already exists, read it first. Never propose changes to code you haven't read.

Workflow

Phase 1: Research the Product

Study the actual product before writing a single word of copy. Never invent features.

  1. Read the codebase — Search for the feature's implementation. Use git log to find recent changes.
  2. Validate claims — For every claimed feature, confirm it exists in code. Report gaps: "X exists. Y is partial. Z not found."
  3. Identify differentiators — What does this do that competitors genuinely don't? Architectural advantages > surface features.
  4. Find the self-improving angle — Any learning/adaptive behavior is marketing gold. Understand the mechanism so you can describe it without jargon.
Phase 2: Competitive Positioning

Frame every section as "why us, not them" without naming competitors.

Positioning formula:

Pain they feel daily
+ What competitors do about it (poorly)
+ What you do differently
+ Outcome they'll experience

Anti-generic test — If copy could appear on a competitor's site unchanged, rewrite it:

  • "AI-powered" → What does the AI actually DO?
  • "Smart automation" → What specifically gets automated?
  • "Easy to use" → Compared to what painful alternative?

Competitor dismissal patterns:

  • "Every [category] app claims [buzzword]. Most just [what they do]. We're different."
  • "Not [old approach]. Real [new approach] that [concrete outcome]."
  • "Other tools stay static. Ours [how it evolves]."
Phase 3: Write Sales Copy

Transform features into desire. Think like a buyer, not an engineer.

Voice by audience:

AudienceToneExample
SME ownerWarm, direct"Snap a receipt. Done."
Finance managerOutcome-driven"Every match shows you exactly why."
EnterpriseTrust-building"Control without complexity."
TechnicalPrecise, credible"Gets measurably smarter every week."

Copy rules:

  1. Lead with pain — "Stop filling forms one by one" > "Automated form filling"
  2. One sentence, one idea — Short. Punchy. Scannable.
  3. Concrete > abstract — "Reply in 10 seconds" > "Fast response times"
  4. "I want this" test — Read each card aloud. Does the buyer think "I need this"? If not, rewrite.
  5. End with outcome — "Never lose a sale to a slow reply" > "Uses NLP to generate responses"

Talking about AI/tech without jargon:

Technical realitySay instead
ML model retrains weekly"Gets smarter every week from your feedback"
Internal optimization frameworkNever mention. Say "learns from corrections"
LLM / GPT / Claude"AI assistant" or just "your assistant"
API integration"Connects to your existing tools"
Training data from user corrections"Every correction teaches it something new"
Accuracy gating prevents regression"Can only get better — never worse"
Explainable AI / reasoning traces"Shows you exactly why each decision was made"
Show full SKILL.md (301 more words)Show less
Phase 4: Design the Page

Conversion-focused page anatomy:

1. Hero         — Headline + subheadline + primary CTA
2. Pain Points  — 3-4 scenarios the buyer FEELS (red/warm tones)
3. Solution     — Transformation cards, not feature lists
4. Social Proof — Testimonials or metrics
5. How It Works — 3 steps max (reduce perceived complexity)
6. Pricing      — vs. status quo comparison, not just a table
7. FAQ          — Objection handling disguised as helpfulness
8. Final CTA    — Urgency + form (repeat primary CTA)

Not every page needs all sections. Match to product complexity:

  • New product launch: All sections
  • Feature card update: Cards + new section if needed
  • Product in portfolio: Cards in drawer/grid, link to dedicated page

CTA and forms:

  • Primary CTA at hero AND bottom — two chances to convert
  • Minimum fields. Each extra field kills ~10% conversion.
  • Lead capture minimum: name + email + company. Add phone only if product requires it.
  • Use existing form infra (Formspree, Resend, etc.) — don't add dependencies.
  • Add hidden _source field to distinguish which page the lead came from.

Early Access / Waitlist pattern:

  • Colored badge signals exclusivity (e.g., purple "Early Access")
  • Minimal inline form (2-3 fields) directly on the feature card
  • Lower friction than separate page — capture interest at moment of discovery
Phase 5: Build and Ship
  1. Match existing patterns — Read 2-3 existing pages. Match imports, layout, routing, design system.
  2. Reuse the design system — Existing UI components only. Don't introduce new frameworks.
  3. Mobile-first — Every section must work at 375px width.
  4. Register the route — Add to router with import.
  5. Type-check — Run type checker before committing. Zero new errors.
  6. Multi-codebase consistency — If product appears on multiple sites, update ALL with consistent messaging.
Phase 6: Ship Checklist

Before pushing:

  • Every feature in copy exists in actual product code
  • No jargon (scan for: API, SDK, LLM, model, algorithm, pipeline, container)
  • Every card passes the "I want this" test
  • CTA buttons work (scroll to form or link to sign-up)
  • Form submits correctly with _source field
  • Mobile responsive at 375px
  • Type-checks pass
  • All codebases updated if product is multi-site
  • Competitor copy test: could this appear on a competitor's site? If yes, rewrite.

Reference Files

© ooiyeefei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/landing-page-gtm of ooiyeefei/ccc.

  • SKILL.md
  • README.md
  • references/copy-formulas.md
  • references/page-archetypes.md

Open the folder on GitHubat commit c0fd926

Compare with similar skills

Landing Page GTM Copy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Landing Page GTM Copy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Landing Page GTM Copy this skillooiyeefei/ccc495—~1.8kAutomated safety check: PassMIT
Copynicepkg/ai-workflow285—~3.1kAutomated safety check: PassMIT
Marketing Campaignaffaan-m/ECC277k1 repos~1.3kAutomated safety check: PassMIT
Landing Page Optimizationmanojbajaj95/claude-gtm-plugin105—~1.9kAutomated safety check: PassMIT
Marketing OsYuzzyuk/marketing-os540—~2.5kAutomated safety check: PassMIT
Revenue Centric Designheliocosta-dev/revenue-centric-design740—~1.6kAutomated safety check: PassCustom licence

Similar skills

  • Copy

    nicepkg/ai-workflow

    Professional copywriter for SaaS and startups. An agent skill from nicepkg/ai-workflow.

    285 GitHub stars~3.1k tokensUpdated 8 mo ago
    Marketing & SEOAuto-check passed
  • Marketing Campaign

    affaan-m/ECC

    End-to-end marketing campaign planning and execution. An agent skill from affaan-m/ECC.

    277k GitHub starsUsed in 1 repo~1.3k tokens
    Marketing & SEOAuto-check passed
  • Landing Page Optimization

    manojbajaj95/claude-gtm-plugin

    A skill your agent uses when working on landing pages — creation, copywriting, design, optimization, or conversion rate improvement.

    105 GitHub stars~1.9k tokensUpdated 23 days ago
    Marketing & SEOAuto-check passed
  • Marketing Os

    Yuzzyuk/marketing-os

    A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.

    540 GitHub stars~2.5k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Revenue Centric Design

    heliocosta-dev/revenue-centric-design

    Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…

    740 GitHub stars~1.6k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Landing Page Copywriter

    julianromli/ai-skills

    Write high-converting landing page copy using proven frameworks like PAS (Problem-Agitate-Solution), AIDA, and StoryBrand.

    191 GitHub starsUsed in 2 repos~1.4k tokens
    Frontend & DesignAuto-check passed

More from ooiyeefei/ccc

All 22 skills in this repo
  • Turns meeting recordings into notes with a chain of custody from audio to claim, auditing transcripts for gaps and low-confidence numbers and names.

    495 GitHub stars~876 tokensUpdated 2 mo ago
    Auto-check passed
  • Builds marketing and explainer videos in Remotion from rendered scenes, with one real product capture as proof, and cuts them for each platform's formats.

    495 GitHub stars~2.9k tokensUpdated 2 mo ago
    Auto-check passed
  • Records a sharp product demo video by driving the real app with a browser agent, from storyboard to Xvfb capture and a narration script synced to the frames.

    495 GitHub stars~2.8k tokensUpdated 2 mo ago
    Auto-check passed
  • Generates architecture diagrams as .excalidraw files by analyzing a codebase, with optional PNG or SVG export through Playwright.

    495 GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Sets up GA4 on a website and wires one real conversion event end to end, verified in DebugView before any money goes into ads.

    495 GitHub stars~2.2k tokensUpdated 2 mo ago
    Auto-check passed
  • Meta Pixel Setup

    ooiyeefei/ccc

    Walks a site owner through installing the Meta Pixel, firing one conversion event and verifying it with the Pixel Helper before any ads run.

    495 GitHub stars~2.4k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Landing Page GTM Copy

What does Landing Page GTM Copy do?

Builds or rewrites SaaS landing pages by researching the real product, positioning it against alternatives and writing buyer-focused copy, then implementing it in the codebase. The skill starts with an intake: target URL or route, codebase path, the product or feature being sold, the buyer's role and pain, competitors, and constraints such as the design system or form provider. If the page already exists it is read first.

When should I use Landing Page GTM Copy?

Landing Page GTM Copy fits situations like: building a new SaaS landing page or product page; rewriting feature cards into customer-facing sales language; checking that landing page claims match what the code actually does; sharpening competitive positioning on a pricing or launch page.

How do I install Landing Page GTM Copy in Claude Code?

Run `npx skills add ooiyeefei/ccc --skill landing-page-gtm -a claude-code`. Or copy the skill folder (skills/landing-page-gtm in ooiyeefei/ccc) into .claude/skills/landing-page-gtm in your project. Claude Code loads it when a task matches its description.

How do I install Landing Page GTM Copy in Codex?

Run `npx skills add ooiyeefei/ccc --skill landing-page-gtm -a codex`. Or copy the skill folder (skills/landing-page-gtm in ooiyeefei/ccc) into .agents/skills/landing-page-gtm in your project. Codex loads it when a task matches its description.

Can I use Landing Page GTM Copy in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ooiyeefei/ccc --skill landing-page-gtm -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/landing-page-gtm, .gemini/skills/landing-page-gtm, .github/skills/landing-page-gtm and .opencode/skills/landing-page-gtm in your project.

What does Landing Page GTM Copy need to run?

SKILL.md names no scripts, command-line tools or credentials: Landing Page GTM Copy is instructions for the agent only. Our summary lists: Access to the product's codebase; A frontend project where the page lives.

Does Landing Page GTM Copy access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Landing Page GTM Copy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Landing Page GTM Copy use?

Landing Page GTM Copy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Landing Page GTM Copy use?

About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.

What are the alternatives to Landing Page GTM Copy?

Skills that share tags, products or a category with Landing Page GTM Copy: Copy (nicepkg/ai-workflow, 285 stars), Marketing Campaign (affaan-m/ECC, 277k stars), Landing Page Optimization (manojbajaj95/claude-gtm-plugin, 105 stars) and Marketing Os (Yuzzyuk/marketing-os, 540 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Landing Page GTM Copy?

ooiyeefei (a GitHub user) maintains it in ooiyeefei/ccc, which has 495 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on July 29, 2026.

Source: ooiyeefei/ccc on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.