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.
Analyze the message match between your ads and landing pages.
Install Ad To Landing Page Auditor
$ npx skills add gooseworks-ai/goose-skills --skill ad-to-landing-page-auditor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gooseworks-ai/goose-skills ad-to-landing-page-auditor --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/gooseworks-ai/goose-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ads/composites/ad-to-landing-page-auditor .claude/skills/ad-to-landing-page-auditor && 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 "ad-to-landing-page-auditor" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/ads/composites/ad-to-landing-page-auditor into .claude/skills/ad-to-landing-page-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ad-to-landing-page-auditor", 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/gooseworks-ai/goose-skills/tree/main/skills/ads/composites/ad-to-landing-page-auditorType 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 gooseworks-ai/goose-skills --skill ad-to-landing-page-auditor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gooseworks-ai/goose-skills ad-to-landing-page-auditor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ads/composites/ad-to-landing-page-auditor .agents/skills/ad-to-landing-page-auditor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ad-to-landing-page-auditor" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/ads/composites/ad-to-landing-page-auditor into .agents/skills/ad-to-landing-page-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ad-to-landing-page-auditor", 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 gooseworks-ai/goose-skills --skill ad-to-landing-page-auditor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gooseworks-ai/goose-skills ad-to-landing-page-auditor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ads/composites/ad-to-landing-page-auditor .cursor/skills/ad-to-landing-page-auditor && 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 "ad-to-landing-page-auditor" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/ads/composites/ad-to-landing-page-auditor into .cursor/skills/ad-to-landing-page-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ad-to-landing-page-auditor", 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/gooseworks-ai/goose-skills.git --path skills/ads/composites/ad-to-landing-page-auditor--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 gooseworks-ai/goose-skills --skill ad-to-landing-page-auditor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gooseworks-ai/goose-skills ad-to-landing-page-auditor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ads/composites/ad-to-landing-page-auditor .gemini/skills/ad-to-landing-page-auditor && 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 "ad-to-landing-page-auditor" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/ads/composites/ad-to-landing-page-auditor into .gemini/skills/ad-to-landing-page-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ad-to-landing-page-auditor", 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 gooseworks-ai/goose-skills ad-to-landing-page-auditorInstalls 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 gooseworks-ai/goose-skills --skill ad-to-landing-page-auditor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ads/composites/ad-to-landing-page-auditor .github/skills/ad-to-landing-page-auditor && 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 "ad-to-landing-page-auditor" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/ads/composites/ad-to-landing-page-auditor into .github/skills/ad-to-landing-page-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ad-to-landing-page-auditor", 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 gooseworks-ai/goose-skills --skill ad-to-landing-page-auditor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gooseworks-ai/goose-skills ad-to-landing-page-auditor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ads/composites/ad-to-landing-page-auditor .opencode/skills/ad-to-landing-page-auditor && 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 "ad-to-landing-page-auditor" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/ads/composites/ad-to-landing-page-auditor into .opencode/skills/ad-to-landing-page-auditor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ad-to-landing-page-auditor", 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
ad-to-landing-page-auditor- GitHub stars
- 1.2k
- Used in
- 1 other repo
- Token cost
- ~1.7k tokens
- SKILL.md length
- 597 words
- Files
- 2
- Skills in repo
- 273
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyze the message match between your ads and landing pages.
- Works in 5 steps: Intake → Ad Inventory → Landing Page Audit → …
- Tasks that involve Landing pages
- SKILL.md covers When to Use, Phase 0: Intake, Phase 1: Ad Inventory and Phase 2: Landing Page Audit, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ad To Landing Page Auditor is an agent skill from gooseworks-ai/goose-skills. Analyze the message match between your ads and landing pages. Checks if the promise in the ad copy carries through to the landing page headline, body, and CTA. Flags disconnects that kill conversion rates. Works with Google, Meta, and LinkedIn ads.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.meta.json`).
It sits in Frontend & Design, covering Landing pages and Conversion rate optimization. The repository describes itself as: Library of Growth & GTM skills + data APIs for Claude Code, Codex, Cursor to run ads, social, content, lead gen, seo and data scraping. The licence is MIT.
When your agent uses it
- Tasks that involve Landing pages
- Tasks that involve Conversion rate optimization
Example prompts
- “/ad-to-landing-page-auditor”
Workflow steps
5 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 c650c6d. 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 (its code samples are markdown).
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
Ad To Landing Page Auditor loads about 1.7k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 597 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 gooseworks-ai/goose-skills at commit c650c6d, republished under its MIT licence (© gooseworks-ai). 597 words, ~1,709 tokens.
Download SKILL.mdSave it as
.claude/skills/ad-to-landing-page-auditor/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- ad-to-landing-page-auditor
- description
- Analyze the message match between your ads and landing pages. Checks if the promise in the ad copy carries through to the landing page headline, body, and CTA. Flags disconnects that kill conversion rates. Works with Google, Meta, and LinkedIn ads.
- tags
- ads
Ad-to-Landing Page Auditor
The #1 reason ads get clicks but not conversions: the landing page doesn't deliver on the ad's promise. This skill audits the full click path — from ad copy to landing page experience — and flags every disconnect.
Core principle: A great ad with a mismatched landing page is worse than a mediocre ad with a matched one. Message match is the single biggest conversion lever most startups ignore.
When to Use
- "Why are my ads getting clicks but no conversions?"
- "Audit my ad-to-landing page flow"
- "Check message match on our campaigns"
- "My conversion rate is low — help me figure out why"
- "Review our landing pages for our ad campaigns"
Phase 0: Intake
- Ad copy — For each ad, provide:
- Headline(s)
- Body / description text
- CTA text
- Platform (Google Search / Meta / LinkedIn)
- Landing page URLs — The URL each ad points to
- Conversion goal — What should happen after someone clicks? (Demo / Trial / Purchase / Download)
- Known conversion rates? — Current click → conversion rate per ad/LP (if available)
If the user has a CSV export from their ad platform, parse that instead.
Phase 1: Ad Inventory
Parse the provided ads into:
| Ad ID | Platform | Headline | Body/Description | CTA | Landing Page URL | Conv Rate (if known) |
|---|
Phase 2: Landing Page Audit
For each unique landing page URL, fetch the page content:
fetch_webpage: [landing_page_url]If fetch_webpage is not available, use curl to retrieve the page HTML.
Extract and score:
2A: Content Elements
| Element | Found? | Content |
|---|---|---|
| Hero headline | [Y/N] | "[Text]" |
| Subheadline | [Y/N] | "[Text]" |
| Primary CTA | [Y/N] | "[Button text]" |
| CTA above fold | [Y/N] | — |
| Social proof | [Y/N] | [Logos / testimonials / metrics] |
| Benefit list | [Y/N] | [Key benefits listed] |
| Form / Sign-up | [Y/N] | [Field count: N] |
| Video | [Y/N] | — |
| Trust signals | [Y/N] | [Security badges, guarantees] |
2B: Message Match Scoring
For each ad → landing page pair, score on:
| Dimension | Score (1-10) | Criteria |
|---|---|---|
| Promise continuity | [X] | Does the LP headline deliver on the ad's promise? |
| Language match | [X] | Does the LP use the same words/phrases as the ad? |
| Visual continuity | [X] | Does the LP feel like a continuation of the ad? (Not assessable for search) |
| CTA alignment | [X] | Does the LP's ask match what the ad implied? |
| Specificity match | [X] | If the ad was specific ("for sales teams"), is the LP specific too? |
| Emotional match | [X] | If the ad used fear/urgency, does the LP carry that forward? |
Message Match Score: [Average/60]
Show full SKILL.md (212 more words)Show less
Scoring Guide
| Score | Rating | Meaning |
|---|---|---|
| 50-60 | Excellent | Strong match — LP delivers on every ad promise |
| 40-49 | Good | Minor disconnects but overall coherent |
| 30-39 | Needs work | Noticeable gaps — visitor has to hunt for relevance |
| 20-29 | Poor | Ad and LP feel like different products |
| Below 20 | Critical | Complete mismatch — fix immediately |
Phase 3: Conversion Friction Analysis
Beyond message match, assess landing page conversion friction:
| Friction Type | Check | Status |
|---|---|---|
| Load time | Does the page feel heavy/slow? (Asset count proxy) | [Fast/Slow/Unknown] |
| Form length | How many fields before conversion? | [N fields] — [Appropriate/Too many] |
| CTA clarity | Is there one clear CTA or competing actions? | [Clear/Cluttered] |
| Above-fold conversion | Can someone convert without scrolling? | [Yes/No] |
| Social proof placement | Is proof near the CTA? | [Yes/No] |
| Navigation distraction | Does the LP have full site nav? (Should be minimal) | [Minimal/Full nav] |
| Mobile experience | Any mobile-unfriendly elements? | [Good/Issues] |
Phase 4: Output Format
# Ad-to-Landing Page Audit — [Product/Client] — [DATE]
Ads audited: [N]
Unique landing pages: [N]
Platform(s): [Google / Meta / LinkedIn]
Overall message match: [Score/60] — [Rating]
---
## Executive Summary
[3-4 sentences: Overall finding, biggest disconnect, top recommendation, estimated conversion impact]
---
## Audit Results by Ad → Landing Page Pair
### Ad 1: "[Ad headline excerpt]"
**Platform:** [Google Search / Meta / LinkedIn]
**Ad copy:**
> Headline: "[text]"
> Body: "[text]"
> CTA: "[text]"
**Landing page:** [URL]
> LP headline: "[text]"
> LP subhead: "[text]"
> LP CTA: "[button text]"
**Message Match Score: [X/60] — [Rating]**
| Dimension | Score | Issue |
|-----------|-------|-------|
| Promise continuity | [X/10] | [Specific finding] |
| Language match | [X/10] | [Specific finding] |
| CTA alignment | [X/10] | [Specific finding] |
| Specificity match | [X/10] | [Specific finding] |
| Emotional match | [X/10] | [Specific finding] |
**Disconnect found:** [Specific description of mismatch]
**Recommended fix:** [Specific change to ad or LP]
### Ad 2: ...
---
## Landing Page Friction Report
### [Landing Page URL]
| Friction Point | Status | Impact | Fix |
|---------------|--------|--------|-----|
| [Friction] | [Red/Yellow/Green] | [High/Med/Low] | [Specific fix] |
---
## Priority Fixes
### Critical (Fix This Week)
1. **[Ad/LP pair]:** [Specific mismatch] → [Specific fix]
- Est. conversion impact: [X% improvement]
### Important (Fix This Month)
2. **[Issue]:** [Fix]
### Nice-to-Have
3. **[Issue]:** [Fix]
---
## Rewrite Suggestions
### For [Ad or LP with worst match]:
**Current ad headline:** "[current]"
**Suggested ad headline:** "[rewrite that matches LP]"
OR
**Current LP headline:** "[current]"
**Suggested LP headline:** "[rewrite that matches ad]"Save to ad-lp-audit-[YYYY-MM-DD].md in the current working directory (or user-specified path).
Cost
| Component | Cost |
|---|---|
| Landing page fetching | Free |
| Analysis | Free (LLM reasoning) |
| Total | Free |
Tools Required
- fetch_webpage or curl — for landing page analysis
- No API keys required
Trigger Phrases
- "Audit my ad-to-landing page match"
- "Why is my conversion rate so low?"
- "Check message match on our campaigns"
- "Do our landing pages match our ads?"
- "Run a CRO audit on our ad funnels"
© gooseworks-ai, 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 1 other file in skills/ads/composites/ad-to-landing-page-auditor of gooseworks-ai/goose-skills.
- SKILL.md
- skill.meta.json
Open the folder on GitHubat commit c650c6d
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gooseworks-ai/goose-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Ad To Landing Page Auditor 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 |
|---|---|---|---|---|---|---|
| Ad To Landing Page Auditor this skillgooseworks-ai/goose-skills | 1.2k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Landing Page Generatorbuildfastwithai/gen-ai-experiments | 785 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Landing Page Audit 39irinabuht12-oss/marketing-skills | 4.1k | — | ~1.6k | Automated safety check: Pass | None | |
| Landing CraftEliasOulkadi/shokunin | 114 | — | ~4.5k | Automated safety check: Pass | MIT | |
| Ads LandingAgriciDaniel/claude-ads | 9.9k | — | ~612 | Automated safety check: Pass | MIT | |
| Landing Page Conversion Auditgithub/awesome-copilot | 40k | 1 repos | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Landing Page Audit 39
irinabuht12-oss/marketing-skills
CRO analysis for landing pages evaluating headline clarity, CTA placement, trust signals, mobile friction, and conversion killers.
Landing Craft
EliasOulkadi/shokunin
Build conversion-optimized landing pages with CRO frameworks (Conversion Research, LIFT Model), scroll effects, A/B testing, personalization, form optimization, and Core Web Vitals (INP, LCP, CLS).
Ads Landing
AgriciDaniel/claude-ads
Audit paid-ad landing pages for message match, mobile experience, performance, accessibility, trust, forms, consent, tracking, security, and conversion friction.
- Official
Landing Page Conversion Audit
github/awesome-copilot
Audit a landing page, sales page or checkout page for conversion leaks and return a fix list ordered by expected revenue impact.
Redesign My Landingpage
instructa/agent-skills
Build, critique, and iterate high-converting marketing or product landing pages using React + Vite + TypeScript + Tailwind and shadcn/ui components, with all icons sourced from Iconify.
More from gooseworks-ai/goose-skills
All 273 skills in this repoReddit Post Finder
gooseworks-ai/goose-skills
Scrape and search Reddit posts using Apify. An agent skill from gooseworks-ai/goose-skills.
Create Image Fal
gooseworks-ai/goose-skills
Generate or edit an image via any FAL image model (nano-banana edit, gpt-image, flux, ...), ROUTED THROUGH THE fal-proxy so it bills the Ads agent.
Render Hook Replacement
gooseworks-ai/goose-skills
Replace an existing video's opening with a supplied clip or free kinetic text hook while retaining and verifying every original body frame, audio, captions and ending.
Blog Feed Monitor
gooseworks-ai/goose-skills
Scrape blog posts via RSS feeds (free, no API key) with Apify fallback for JS-heavy sites.
Competitor Post Engagers
gooseworks-ai/goose-skills
Find leads by scraping engagers from a competitor's top LinkedIn posts.
Render Chatgpt Chat
gooseworks-ai/goose-skills
Assemble a ChatGPT chat-reveal video ad from a thread + timeline JSON — one continuous Playwright recording of a ChatGPT mobile chat (user types with the iOS keyboard up → taps send → keyboard…
Related
Categories
Questions about Ad To Landing Page Auditor
What does Ad To Landing Page Auditor do?
Analyze the message match between your ads and landing pages. Ad To Landing Page Auditor is an agent skill from gooseworks-ai/goose-skills. Analyze the message match between your ads and landing pages.
When should I use Ad To Landing Page Auditor?
Ad To Landing Page Auditor fits situations like: tasks that involve Landing pages; tasks that involve Conversion rate optimization.
How do I install Ad To Landing Page Auditor in Claude Code?
Run `npx skills add gooseworks-ai/goose-skills --skill ad-to-landing-page-auditor -a claude-code`. Or copy the skill folder (skills/ads/composites/ad-to-landing-page-auditor in gooseworks-ai/goose-skills) into .claude/skills/ad-to-landing-page-auditor in your project. Claude Code loads it when a task matches its description.
How do I install Ad To Landing Page Auditor in Codex?
Run `npx skills add gooseworks-ai/goose-skills --skill ad-to-landing-page-auditor -a codex`. Or copy the skill folder (skills/ads/composites/ad-to-landing-page-auditor in gooseworks-ai/goose-skills) into .agents/skills/ad-to-landing-page-auditor in your project. Codex loads it when a task matches its description.
Can I use Ad To Landing Page Auditor 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 gooseworks-ai/goose-skills --skill ad-to-landing-page-auditor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ad-to-landing-page-auditor, .gemini/skills/ad-to-landing-page-auditor, .github/skills/ad-to-landing-page-auditor and .opencode/skills/ad-to-landing-page-auditor in your project.
What does Ad To Landing Page Auditor need to run?
SKILL.md names no scripts, command-line tools or credentials: Ad To Landing Page Auditor is instructions for the agent only.
Does Ad To Landing Page Auditor 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 Ad To Landing Page Auditor 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 Ad To Landing Page Auditor use?
Ad To Landing Page Auditor 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 Ad To Landing Page Auditor use?
About 1.7k tokens (SKILL.md is roughly 6.8k 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 Ad To Landing Page Auditor?
Skills that share tags, products or a category with Ad To Landing Page Auditor: Landing Page Generator (buildfastwithai/gen-ai-experiments, 785 stars), Landing Page Audit 39 (irinabuht12-oss/marketing-skills, 4.1k stars), Landing Craft (EliasOulkadi/shokunin, 114 stars) and Ads Landing (AgriciDaniel/claude-ads, 9.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ad To Landing Page Auditor?
gooseworks-ai (a GitHub organization) maintains it in gooseworks-ai/goose-skills, which has 1,240 GitHub stars. The repository holds 273 skills in this directory. The repository was last updated on October 8, 2026.
Source: gooseworks-ai/goose-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.