agentleFS
mrhinklemrhinkle/VibeCoding-a-Website/.claude/skills/audit-existing-site/SKILL.md

audit-existing-site

Skill17 starsChanged 8 months agoMITView on GitHub

Audit my website | Check my site's health | Review my WordPress site | Analyze Squarespace site | Audit Wix site | Check my custom site | Website SEO audit | Mobile-friendly check | Site speed check | Security audit | UX review | Accessibility check | Content audit | Copywriting review | Find problems with my site | How's my site doing | Score my website | What's wrong with my site | Site performance review | Is my site secure

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Alt text on images: Every image described for accessibility and SEO

    line 32
  2. Distinctive:

    Headline effectiveness: Do they hook? Is the benefit clear?

    line 38
  3. Distinctive:

    Touch target sizes: All buttons and links ≥44×44px (mobile standard)

    line 51
  4. Distinctive:

    Mixed content warnings: No HTTP assets loaded on HTTPS pages

    line 60
  5. Distinctive:

    No shame. Every site is a work in progress.

    line 114
  6. Distinctive:

    If you need those deeper audits, this is where VibeCoding shines—we can rebuild from the ground up with security and scalability baked in.

    line 128
  7. Distinctive:

    Paste your website URL: when prompted

    line 132

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Audit Existing Site

You already have a website—WordPress, Squarespace, Wix, custom build, doesn't matter. Before you think about rebuilding, let's see what you've actually got.

This skill analyzes your live website without requiring any repo access, GitHub connection, or code handoff. We fetch your site and run a comprehensive 4-part audit: SEO & AEO, Copy & Content, UX, and Security. You get a health score, quick wins, and a roadmap for improvement.

Think of this as a gateway skill. See the value? Then explore how VibeCoding could rebuild or enhance your site from the ground up.

What You Need

  • A live URL (your existing website, already published on the internet)
  • That's it. No repo access, no GitHub, no code to share.

The Audit Pipeline

We run 4 specialized audits in sequence, each targeting a different dimension of site health:

1. SEO & AEO Audit

Searches for technical and structural SEO signals:

  • Meta tags & title tags: Are they present, unique, and keyword-rich?
  • Open Graph / social sharing tags: Will your site look good when shared?
  • Heading hierarchy: H1 → H2 → H3 structure (no orphans, no skips)
  • Schema markup & JSON-LD: Rich snippets for Google
  • Mobile-friendliness signals: Viewport tags, responsive patterns
  • Page speed indicators: Core Web Vitals, load time estimates
  • Alt text on images: Every image described for accessibility and SEO
  • URL structure: Readable slugs, no parameters, proper trailing slashes

2. Copy & Content Audit

Reviews your actual words and messaging:

  • Headline effectiveness: Do they hook? Is the benefit clear?
  • CTA strength and placement: Are calls-to-action specific, urgent, and visible?
  • Readability score: Target is 6th–8th grade level. Shorter sentences win.
  • Value proposition clarity: Could a stranger understand your value in 5 seconds?
  • Microcopy review: Button labels, form fields, error messages, help text
  • Tone consistency: Is your voice uniform across pages?

3. UX Review

Examines user behavior and interface design:

  • Navigation depth: Can users find what they need in 3 clicks or fewer?
  • Mobile responsiveness: Does your site work on phones, tablets, desktops?
  • Visual hierarchy: Is the most important content the most prominent?
  • Touch target sizes: All buttons and links ≥44×44px (mobile standard)
  • Content readability: Line length (50–75 characters ideal), font size (16px+)
  • Common anti-patterns: Autoplaying video, pop-ups on load, unclear submit buttons, etc.

4. Security Surface Scan

Checks publicly visible security indicators:

  • HTTPS enforcement: Are all pages served over SSL/TLS?
  • Security headers: CSP, HSTS, X-Frame-Options, X-Content-Type-Options
  • Mixed content warnings: No HTTP assets loaded on HTTPS pages
  • Third-party script inventory: What external scripts are you running?
  • Cookie & privacy policy presence: Are legal requirements met?

What You Get

One consolidated, encouraging report:

  • Overall health score (0–100)
  • Individual category scores (SEO, Content, UX, Security)
  • Top 5 "Quick Wins": Highest-impact, lowest-effort fixes you can implement today
  • Full findings organized by severity:
    • 🔴 Critical: Security issues, broken functionality
    • 🟠 Major: Significant SEO or UX problems
    • 🟡 Minor: Good-to-fix issues
    • ⚪ Cosmetic: Polish and refinement
  • "What's Next" section: For each major issue, we link to VibeCoding skills that could address it

Example Report Structure

AUDIT REPORT: example.com
Generated: April 4, 2026

OVERALL HEALTH: 62/100 ⭐⭐⭐⭐
Your site is a solid starting point. These 5 quick wins could push you past 80.

CATEGORY SCORES:
  SEO & AEO:     58/100  🔍
  Copy & Content: 68/100  ✍️
  UX:            61/100  💻
  Security:      71/100  🔐

TOP 5 QUICK WINS:
1. Add missing meta descriptions (5 pages affected) — 10 min
2. Fix heading hierarchy on homepage — 15 min
3. Update CTA text for clarity — 20 min
4. Reduce line length on blog posts — 30 min
5. Enable HSTS header — 5 min (if you manage your own server)

[... full findings by category ...]

WHAT'S NEXT:
Can't do these yourself? Consider:
  • seo-content-builder — Write optimized blog posts
  • copy-optimizer — Rewrite headlines and CTAs
  • ux-designer — Redesign navigation and mobile layout
  • build-vibecoding-site — Start fresh with VibeCoding

Tone

We're encouraging, not alarming. "Your site scores 62/100—that's a solid starting point. Here are 5 changes that could push you past 80."

No shame. Every site is a work in progress. The goal is improvement, not perfection.

What This Audit CAN'T Check

Be transparent about limitations. A remote URL audit doesn't see:

  • Server-side code quality: Node, Python, PHP, database queries—we don't audit those
  • Database security: Schema, SQL injection risks, data encryption—out of scope
  • Backend dependencies: NPM packages, plugins, libraries—we don't inspect these
  • Full JavaScript execution: We analyze the HTML/CSS and limited JS, not dynamic state
  • Authenticated pages: We can't log in, so admin panels, member dashboards are invisible
  • Internal link structure: We sample public pages, not your entire sitemap
  • Performance under load: We test from one location, not across global networks

If you need those deeper audits, this is where VibeCoding shines—we can rebuild from the ground up with security and scalability baked in.

How to Use This Skill

  1. Paste your website URL when prompted
  2. We fetch and analyze (takes 2–5 minutes)
  3. You get a report with scores, quick wins, and next steps
  4. Decide: Fix these issues on your own, or explore building with VibeCoding

Next Steps

  • Quick fixes? Implement the quick wins yourself
  • Content audit? Try copy-optimizer to rewrite headlines and CTAs
  • Full redesign? Explore build-vibecoding-site to reconstruct with modern practices
  • More audits? Chain with security-deep-dive or seo-content-builder

Your site is an asset. Let's make it better.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.