Tutorialthe whole build, step by step

Set up four Claude skills for your marketing

Create reusable instructions for ad reviews, creative refreshes, landing pages and site speed, then test them without publishing anything.

By Eric Snyder, founder 2 min readChecked on Oct 29, 2026
Save this guidereceiptsgroup.com/guides/four-marketing-skills
You needClaude Code access, a project folder and your own public website URL.
First testA fictional ad and a public PageSpeed report; no live ad connection required.
Running costYour Claude plan or API usage; your existing website and advertising tools are separate.
In this guide
  1. Start here: paste this into Claude Code
  2. Create the four instruction files
  3. Review ad copy
  4. Refresh tired creative
  5. Write GoHighLevel page sections
  6. Explain a PageSpeed report
  7. First test: no live accounts
  8. What it costs
  9. When it breaks
  10. Sources, checked Oct 29, 2026

A skill is a written-down job Claude follows. These are the four jobs behind the video. The starter instructions below let you build your own versions; they are not a download of my private skill folders. Start with site speed, because a new ad does not fix a slow page.

Checked on Oct 29, 2026

Start here: paste this into Claude Code

PromptWalk me through the setup
I run a home-service business and am not technical. Help me create four project-local Claude Code skills: meta-ads-analyzer, meta-creative-refresh, ghl-landing-page-builder and site-speed-analyzer. A skill lives at .claude/skills/<name>/SKILL.md and starts with YAML name and description. Use the starter instructions below, ask about my setup, show me the files, then test one at a time. Go one step at a time and wait for me. Explain technical words when you first use them. Ask about my business rather than guessing. Stop before spending money, publishing, contacting a customer or deleting anything. Use fictional examples for tests and never put credentials or customer details in a skill.

meta-ads-analyzer: Review the ad copy I provide. Identify the audience, offer and call to action. Quote each unclear, unsupported or misleading line and explain the problem. Give me a revised draft using only facts I supplied. Separate copy judgments from actual campaign performance. Never predict results or claim to diagnose fatigue from copy alone. Ask for missing business facts. Output: findings, revised copy, facts to verify. Do not publish or change an account.

meta-creative-refresh: Review an anonymized performance export that I supply, with its date range and metric definitions. Compare like-for-like periods and note budget, audience and tracking changes. Treat fatigue as a hypothesis, not proof from one metric. Explain missing evidence. Draft distinct new creative angles grounded in the offer and verified facts. For each, give a hook, concept, draft copy and what it tests. Never invent results or testimonials. Do not launch ads or change spend.

ghl-landing-page-builder: Ask for my offer, audience, verified proof, brand and desired action. Draft a mobile-first landing page as separate HTML sections intended for a GoHighLevel custom HTML element. Include clear headings and one main call to action. Make no unsupported claims. Do not add tracking, external form submissions or credentials. Explain where an existing form must be connected; do not invent an integration. Output the sections and a mobile preview checklist. Do not publish.

site-speed-analyzer: Ask what my page is for, which platform it uses, and who will fix it. Read the Google PageSpeed report or exported results I provide. Separate Lighthouse lab results from real visitor data. If data is absent, say so. Explain the main loading, responsiveness and layout issues in plain words. Rank fixes by evidence, impact and effort, with platform-specific guidance only when verified. Do not promise ranking or conversion improvements. Output a prioritized developer handoff and a retest plan. Do not edit the live site.

Create the four instruction files

Open Claude Code in the project where you keep your marketing work. The official skills documentation uses one folder per skill under .claude/skills/. Each folder contains SKILL.md. The name becomes its slash command. These files do not create access to Meta or GoHighLevel.

Review ad copy

markdown.claude/skills/meta-ads-analyzer/SKILL.md
---
name: meta-ads-analyzer
description: Use when asked to review ad copy for a local service business.
---

Review the ad copy I provide. Identify the audience, offer and call to action. Quote each unclear, unsupported or misleading line and explain the problem. Give me a revised draft using only facts I supplied. Separate copy judgments from actual campaign performance. Never predict results or claim to diagnose fatigue from copy alone. Ask for missing business facts. Output: findings, revised copy, facts to verify. Do not publish or change an account.
PromptTry the skill
/meta-ads-analyzer
Ask me for the inputs you need, then show a draft only.

Refresh tired creative

markdown.claude/skills/meta-creative-refresh/SKILL.md
---
name: meta-creative-refresh
description: Use when asked to refresh tired creative for a local service business.
---

Review an anonymized performance export that I supply, with its date range and metric definitions. Compare like-for-like periods and note budget, audience and tracking changes. Treat fatigue as a hypothesis, not proof from one metric. Explain missing evidence. Draft distinct new creative angles grounded in the offer and verified facts. For each, give a hook, concept, draft copy and what it tests. Never invent results or testimonials. Do not launch ads or change spend.
PromptTry the skill
/meta-creative-refresh
Ask me for the inputs you need, then show a draft only.

Write GoHighLevel page sections

markdown.claude/skills/ghl-landing-page-builder/SKILL.md
---
name: ghl-landing-page-builder
description: Use when asked to write gohighlevel page sections for a local service business.
---

Ask for my offer, audience, verified proof, brand and desired action. Draft a mobile-first landing page as separate HTML sections intended for a GoHighLevel custom HTML element. Include clear headings and one main call to action. Make no unsupported claims. Do not add tracking, external form submissions or credentials. Explain where an existing form must be connected; do not invent an integration. Output the sections and a mobile preview checklist. Do not publish.
PromptTry the skill
/ghl-landing-page-builder
Ask me for the inputs you need, then show a draft only.

Explain a PageSpeed report

markdown.claude/skills/site-speed-analyzer/SKILL.md
---
name: site-speed-analyzer
description: Use when asked to explain a pagespeed report for a local service business.
---

Ask what my page is for, which platform it uses, and who will fix it. Read the Google PageSpeed report or exported results I provide. Separate Lighthouse lab results from real visitor data. If data is absent, say so. Explain the main loading, responsiveness and layout issues in plain words. Rank fixes by evidence, impact and effort, with platform-specific guidance only when verified. Do not promise ranking or conversion improvements. Output a prioritized developer handoff and a retest plan. Do not edit the live site.
PromptTry the skill
/site-speed-analyzer
Ask me for the inputs you need, then show a draft only.

First test: no live accounts

PromptReview a fictional ad
/meta-ads-analyzer
Example (made up): a local roofing company offers a roof inspection. Draft ad: "Guaranteed cheapest roof in town. Call now." Review the copy, flag unsupported promises, and rewrite without inventing proof. Do not publish.

A useful review flags both the guarantee and the unproven price comparison. For site speed, run your public page at PageSpeed Insights and give the skill the report URL. If it cannot read the report, paste the report data; it must not guess a score.

What it costs

PartCost and limit
Instruction filesNo separate skill license is required to write these starter files.
Claude CodeIncluded with supported paid Claude plans; Pro is $20 billed monthly on the official pricing page checked October 29, 2026. Usage limits apply. API billing is separate.
Existing toolsWebsite hosting, GoHighLevel, ad spend and any connector are separate. No new subscription or live connector is needed for the fictional-copy test.

When it breaks

The slash command does not appear
Check the exact path .claude/skills//SKILL.md and YAML name/description, then start a new session in that project.
Claude cannot see live ad performance
Instructions are not an integration. Supply an anonymized export. A live connection is optional and needs its own authorization.
The page sections do not publish themselves
Have your developer review them in the GoHighLevel builder and connect your existing form. Preview on a phone before publishing.
A PageSpeed score changes
Lab tests vary. Retest the same URL and distinguish lab results from the rolling real visitor report.
Claude says you hit a usage limit
Wait for the account reset or review the plan options. Repeated prompts do not remove the limit.

Now you have a setup you can test on your own work. Want help setting this up? Receipts Group builds these systems.

Checked on Oct 29, 2026 against

Every claim about a third-party tool in this guide (plans, prices, menu paths, commands, limits) was checked against these official pages on Oct 29, 2026. These screens change often: if something looks different, trust the page over this guide.

Rather skip the setup?

Want help setting this up?

Receipts Group builds these systems. Thirty minutes with Eric tells you which piece is worth building first, or that none of them are. The guides stay free either way.

Keep going

more free guides