Kill AI Slop
yetone/kill-ai-slop
Find and remove AI slop — the generic, machine-default visual and copy tics of vibe-coded products — from a web project.
A skill your agent uses when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services.
Install Landing Page
$ npx skills add boraoztunc/skills --skill landing-page -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install boraoztunc/skills landing-page --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/boraoztunc/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/landing-page .claude/skills/landing-page && rm -rf skills-srcUse ~/.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/
Install the "landing-page" agent skill from https://github.com/boraoztunc/skills/tree/main/landing-page into .claude/skills/landing-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "landing-page", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/boraoztunc/skills/tree/main/landing-pageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add boraoztunc/skills --skill landing-page -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install boraoztunc/skills landing-page --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boraoztunc/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/landing-page .agents/skills/landing-page && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "landing-page" agent skill from https://github.com/boraoztunc/skills/tree/main/landing-page into .agents/skills/landing-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "landing-page", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add boraoztunc/skills --skill landing-page -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install boraoztunc/skills landing-page --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boraoztunc/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/landing-page .cursor/skills/landing-page && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "landing-page" agent skill from https://github.com/boraoztunc/skills/tree/main/landing-page into .cursor/skills/landing-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "landing-page", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/boraoztunc/skills.git --path landing-page--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add boraoztunc/skills --skill landing-page -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install boraoztunc/skills landing-page --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boraoztunc/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/landing-page .gemini/skills/landing-page && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "landing-page" agent skill from https://github.com/boraoztunc/skills/tree/main/landing-page into .gemini/skills/landing-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "landing-page", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install boraoztunc/skills landing-pageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add boraoztunc/skills --skill landing-page -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/boraoztunc/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/landing-page .github/skills/landing-page && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "landing-page" agent skill from https://github.com/boraoztunc/skills/tree/main/landing-page into .github/skills/landing-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "landing-page", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add boraoztunc/skills --skill landing-page -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install boraoztunc/skills landing-page --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boraoztunc/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/landing-page .opencode/skills/landing-page && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "landing-page" agent skill from https://github.com/boraoztunc/skills/tree/main/landing-page into .opencode/skills/landing-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "landing-page", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
landing-page- GitHub stars
- 398
- Used in
- 2 other repos
- Token cost
- ~1.3k tokens
- SKILL.md length
- 687 words
- Files
- 2
- Skills in repo
- 52
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services.
- Works in 10 steps: Page purpose → Audience + context → Proof + assets → …
- Rewriting a high-converting landing page (single-offer page) for SaaS/apps/services
- SKILL.md covers Before you design/write, Core structure (what it should…, Layout types (pick one) and High‑conversion strategies…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Landing Page is an agent skill from boraoztunc/skills. Use when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services. Covers structure, layout patterns, conversion strategies, copywriting, SEO/AEO, and common pitfalls.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `REFERENCES.md`).
It sits in Frontend & Design, covering Landing pages, Copywriting and AI search optimization. The repository describes itself as: Claude Code skills for copywriting, SEO, design, and more. The licence is Apache-2.0.
When your agent uses it
- Rewriting a high-converting landing page (single-offer page) for SaaS/apps/services
- Tasks that involve Landing pages
- Tasks that involve Copywriting
Example prompts
- “/landing-page”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 645553c. 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 loads about 1.3k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 687 words of instructions outside code blocks.
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 boraoztunc/skills at commit 645553c, republished under its Apache-2.0 licence (© boraoztunc). 687 words, ~1,290 tokens.
Download SKILL.mdSave it as
.claude/skills/landing-page/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- landing-page
- description
- Use when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services. Covers structure, layout patterns, conversion strategies, copywriting, SEO/AEO, and common pitfalls.
Landing Page (High‑Conversion) — Web Design Skill
A landing page is not a homepage. A homepage serves multiple intents. A landing page wins one intent: one offer → one audience → one primary action.
Before you design/write
Gather (ask if missing):
1) Page purpose
- What is the ONE primary action? (trial, demo, buy, waitlist, download)
- What’s the offer? (exactly what do they get?)
- What counts as conversion? (click, signup, purchase)
2) Audience + context
- Who is the ICP?
- What problem are they trying to solve?
- Top 3 objections (why they don’t convert today)
- Traffic source: ads / search / social / email
- What do visitors already know when they land?
3) Proof + assets
- Any proof points: logos, testimonials, numbers, case studies
- Screenshots, demo video, product GIFs
- Guarantees / refund / cancellation terms
4) Constraints
- Brand voice: casual vs professional
- Design direction: minimal editorial vs playful 3D vs glass UI
- Mobile priority?
Core structure (what it should include)
Above the fold (must)
- Headline (outcome + audience)
- Subheadline (clarifies “how” + adds specificity)
- Primary CTA (clear verb + what they get)
- One proof signal (logo strip / stat / short testimonial)
- Hero visual (product screenshot/video) or a strong illustration
Mid page (argument)
- Problem → solution (1 section)
- Benefits (3–5, outcome-driven)
- How it works (3 steps)
- Social proof (testimonials/case study)
Bottom (objection handling)
- FAQ (6–12 Q/A)
- Risk reversal (trial, cancel anytime, guarantee)
- Final CTA (same as top)
Layout types (pick one)
A) Classic hero + sections (most common)
Best when:
- product is understandable with a hero screenshot
B) Long-form story (sales page)
Best when:
- you need to educate + overcome skepticism
C) Minimal conversion page
Best when:
- high-intent traffic (email → known users)
- short offer (download, waitlist)
D) Comparison landing page
Best when:
- search intent includes alternatives (“X vs Y”, “best for…”)—usually paired with SEO pages
High‑conversion strategies (practical)
1) Match message to source
If traffic is from ads:
- mirror the ad headline in the hero
- use the same promise and visual tone
2) Make the next step obvious
- one primary CTA
- avoid multiple competing CTAs above the fold
3) Write benefit-first
- Features: what it does
- Benefits: what that means for them
4) Use specificity
- ❌ “Save time and streamline”
- ✅ “Cut your weekly reporting from 4 hours to 15 minutes”
5) Reduce risk
Pick at least one:
- free trial
- free plan
- no credit card
- cancel anytime
- money-back guarantee
6) Objection handling is a section, not a footer
- add FAQ earlier if it’s a high-friction offer
- put proof right next to the claim it supports
Show full SKILL.md (273 more words)Show less
Copywriting templates
Headline formulas
- “{Outcome} without {pain}”
- “The {category} for {audience}”
- “Ship {result} in {time}”
Subheadline rules
- 1–2 sentences
- clarify what it is + who it’s for
CTA rules
- Verb + what they get
- Avoid weak CTAs: “Learn more”, “Submit”
Examples:
- “Start free trial”
- “Book a demo”
- “Get the checklist”
Benefit bullets
Format:
- Benefit — proof/detail
Example:
- Faster iteration — generate 3 layout variants in one click.
Section-by-section workflow (designer-friendly)
Work in this order:
- Hero
- Benefits
- How it works
- Proof
- FAQ
- Final CTA
Rule: don’t rebuild the whole page each time. Iterate section-by-section to keep control.
SEO + AEO checklist (when relevant)
When landing pages should NOT be indexed
- ad-only campaigns
- highly time-bound offers
Use:
noindex(or keep it behind a non-indexed path)
When they SHOULD be indexed
- evergreen offers
- search intent matches the promise
Add:
- clear title + meta
- internal links from homepage/feature pages
- FAQ in plain Q/A for AEO
Optional:
- FAQ schema (if appropriate)
Common pitfalls
- Too many CTAs above the fold
- Vague value prop (“streamline”, “optimize”)
- Big feature list with no outcomes
- Proof hidden at the bottom
- Mobile layout breaks readability
- No clear next step
Output format (when generating a landing page)
Return:
- Page outline (sections + order)
- Hero copy (headline, subheadline, CTA, proof line)
- Benefits section (3–5 bullets)
- How it works (3 steps)
- FAQ (6–12 Q/A)
- SEO/AEO (indexing recommendation + title/meta if indexed)
- Layout recommendation (A/B/C/D + why)
Quick questions (if user says “make a landing page”)
- What’s the ONE primary CTA?
- Who is the ICP and what’s the main pain?
- Any proof (numbers/testimonials/logos)?
- What’s the offer and risk reversal?
- Where is traffic coming from?
© boraoztunc, Apache-2.0. 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 1 other file in landing-page of boraoztunc/skills.
- SKILL.md
- REFERENCES.md
Open the folder on GitHubat commit 645553c
Used in 2 other repositories
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in boraoztunc/skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Landing Page 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Landing Page this skillboraoztunc/skills | 398 | 2 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Kill AI Slopyetone/kill-ai-slop | 1.3k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Landing Page Copywriterjulianromli/ai-skills | 191 | 2 repos | ~1.4k | Automated safety check: Pass | None | |
| Refero Designreferodesign/refero_skill | 299 | — | ~5.3k | Automated safety check: Pass | MIT | |
| Landing Page Generatorbuildfastwithai/gen-ai-experiments | 785 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Arabic Copy Localizergrowthack88/growth-marketing-os | 116 | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
Landing Page Copywriter
julianromli/ai-skills
Write high-converting landing page copy using proven frameworks like PAS (Problem-Agitate-Solution), AIDA, and StoryBrand.
Refero Design
referodesign/refero_skill
Primary/default skill for UI design, product design, web design, landing pages, dashboards, product screens, redesigns, visual polish, frontend/CSS styling, design systems, components, responsive…
Landing Page Generator
buildfastwithai/gen-ai-experiments
Builds a single self-contained HTML landing page from a template with copy frameworks, four themes and SEO meta, then runs bundled audit scripts for conversion and speed.
Arabic Copy Localizer
growthack88/growth-marketing-os
Marketing copy localization skill that converts English marketing copy (ads, landing pages, emails, CTAs) into native Egyptian Arabic عامية — or GCC dialect on request — with natural English…
Landing Page
emotixco/claude-skills-founder
Write landing page copy section by section, from hero to final call to action, including FAQ and SEO metadata.
More from boraoztunc/skills
All 52 skills in this repoGsap
boraoztunc/skills
GSAP animation reference for HyperFrames. An agent skill from boraoztunc/skills.
Hyperframes
boraoztunc/skills
Create video compositions, animations, title cards, overlays, captions, voiceovers, audio-reactive visuals, and scene transitions in HyperFrames HTML.
Remotion To Hyperframes
boraoztunc/skills
Translate an existing Remotion (React-based) video composition into a HyperFrames HTML composition.
Animejs
boraoztunc/skills
Anime.js adapter patterns for HyperFrames. An agent skill from boraoztunc/skills.
Beam Glow States
boraoztunc/skills
Create React loading, processing, selected, current, focus, and pressed states with the border-beam package's animated edge glow.
Minimal Zine Poster
boraoztunc/skills
Compile a theme, sentence, object, mood, article idea, or photo into a quiet Japanese/Korean zine-style editorial poster — tall aged paper, large negative space, one small image anchor, experimental…
Related
Categories
Questions about Landing Page
What does Landing Page do?
A skill your agent uses when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services. Landing Page is an agent skill from boraoztunc/skills. Use when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services.
When should I use Landing Page?
Landing Page fits situations like: rewriting a high-converting landing page (single-offer page) for SaaS/apps/services; tasks that involve Landing pages; tasks that involve Copywriting.
How do I install Landing Page in Claude Code?
Run `npx skills add boraoztunc/skills --skill landing-page -a claude-code`. Or copy the skill folder (landing-page in boraoztunc/skills) into .claude/skills/landing-page in your project. Claude Code loads it when a task matches its description.
How do I install Landing Page in Codex?
Run `npx skills add boraoztunc/skills --skill landing-page -a codex`. Or copy the skill folder (landing-page in boraoztunc/skills) into .agents/skills/landing-page in your project. Codex loads it when a task matches its description.
Can I use Landing Page 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 boraoztunc/skills --skill landing-page -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, .gemini/skills/landing-page, .github/skills/landing-page and .opencode/skills/landing-page in your project.
What does Landing Page need to run?
SKILL.md names no scripts, command-line tools or credentials: Landing Page is instructions for the agent only.
Does Landing Page 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 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 use?
Landing Page is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Landing Page use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Landing Page?
Skills that share tags, products or a category with Landing Page: Kill AI Slop (yetone/kill-ai-slop, 1.3k stars), Landing Page Copywriter (julianromli/ai-skills, 191 stars), Refero Design (referodesign/refero_skill, 299 stars) and Landing Page Generator (buildfastwithai/gen-ai-experiments, 785 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Landing Page?
boraoztunc (a GitHub user) maintains it in boraoztunc/skills, which has 398 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on August 15, 2026.
Source: boraoztunc/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.