audit
/audit
Sprawdza i poprawia witrynę zbudowaną w GoHighLevel AI Studio: wydajność, Google, mapę witryny i formularze.
- Autor
- tenaciousduck ↗
- Repozytorium
- ai-studio-website-skill ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Sprawdza i poprawia witrynę zbudowaną w GoHighLevel AI Studio: wydajność, Google, mapę witryny i formularze.
Oryginalny opis (EN)
Use when checking, auditing, reviewing, fixing, speeding up or improving an existing website made in GoHighLevel (GHL, HighLevel, LeadConnector) AI Studio, the whole site or one area, but not re-checks after repairs (recheck) or terms, privacy, cookie notice or checkout wording (legal). Also use when a repo has .vibe/project.json or src/integrations/payments and the site is slow, isn't showing in Google, needs a sitemap, has a form not reaching GHL, or has fake reviews.
Jak działa
- Overview
- First, in every session
- Audit session (read-only)
- Repair session
- Common mistakes
Podgląd SKILL.md
---
name: audit
description: Use when checking, auditing, reviewing, fixing, speeding up or improving an existing website made in GoHighLevel (GHL, HighLevel, LeadConnector) AI Studio, the whole site or one area, but not re-checks after repairs (recheck) or terms, privacy, cookie notice or checkout wording (legal). Also use when a repo has .vibe/project.json or src/integrations/payments and the site is slow, isn't showing in Google, needs a sitemap, has a form not reaching GHL, or has fake reviews.
---
# Auditing AI Studio Websites
## Overview
Audits an existing AI Studio site, then repairs it in approved phases.
**Core principle:** measure first, change nothing until the owner picks repairs.
## First, in every session
1. Read the builder's settings (`.claude/ai-studio-setup.md` in the project, then `~/.claude/ai-studio-setup.md`) and `docs/STATUS.md`. If neither settings file exists, offer `/ai-studio-websites:setup`; if declined, use the defaults.
2. Show the audit opener from `../../shared/opener.md`. Follow `../../shared/sessions.md` for phases, waiting, branching, the dial and endings.
3. Check superpowers, as in step 2 of `../build/SKILL.md`. The rules in `../../shared/rules.md` bind every session here.
**One area named** ("my form isn't reaching GHL", "add a sitemap"): audit only that checklist area, read-only, with a short report. Repair it next session (or now, if the owner agrees it's small and clear), then offer a full audit once. New sites and features belong to the build skill.
## Audit session (read-only)
1. **Intake.** Ask only what code and the live site can't answer: what the site is for, who it serves and in which countries, whether it sells, which forms matter, whether there's an admin, what they most want improved. Never assume a country.
2. **Confirm the stack** against "The stack" in `../../shared/references/02-platform.md`. If it differs, say which checks may not apply.
3. **Run the checks** in `../../shared/references/audit-checklist.md`. Keep raw output in the scratchpad; report in plain English.
4. **Live form test, only after a yes.** First say: "A real contact will be created, and your workflows will run on it, including emails and any task for you." Use their address with `+sitetest1`. They submit it, following your short steps, then read the contact back in GHL (tags, fields, note, source, any task), tag it `sys:test-record` and delete it. Drive their signed-in browser, GHL or a connector only if they prefer. No yes: "checked in code only".
5. **Write the report** from `../../shared/references/report-template.md` to `docs/audit/YYYY-MM-DD-audit.md`. If the project is public (`gh repo view --json visibility`, else ask; unknown counts as public), save it in `.audit/`, add `.audit/` to `.gitignore`, telling the owner why: it lists weaknesses attackers could use.
6. **Walk through the top findings,** record the agreed repair order in `docs/STATUS.md`, and end as `sessions.md` says.
The audit writes only the report, `docs/STATUS.md` and that `.gitignore` line: no other edits, commits, form submissions (except the approved live test), purchases or database writes.
## Repair session
1. Read `docs/STATUS.md` and the report. First commit on the phase branch: `docs/STATUS.md`, any `.gitignore` change, and a report in `docs/audit/`.
2. Plan with `superpowers:writing-plans` beyond a few lines; execute with `superpowers:subagent-driven-development` at the dial's level.
3. Fix with the shared chapters and templates, citing the chapter. Visible change: mockups first, as `sessions.md` says. Legal repairs: end the session with the legal line, as `sessions.md` item 5 says. Where nothing should look different, compare before and after (rule 9 in `../../shared/rules.md`).
4. Review, merge per the setup file. The owner publishes; run the live check: the same tools on the live site, plus `curl -sI` for headers and generated files. If the findings came from an outside checker, ask the owner to re-run it.
5. Mark each finding fixed, with evidence. Update `docs/STATUS.md`; give the next session's line, after the last phase `Start a new session and say: "/ai-studio-websites:recheck"`.
Not legal advice. Never claim compliance.
## Common mistakes
| Thought | Reality |
|---|---|
| "Fix stuff as you go to save time", "only clear-cut fixes", "just a copy" | Decline in one sentence: nothing changes before the owner sees it all. A scratch copy is still repair. |
| "This lost sign-ups on another site" | Unverified until checked here. |
| "Noticed, separate from your question" | Single area: one line per urgent item. |
| Selling or Admin asked about | Not applicable, one line why. |
| Nine questions, or a closing plan | Ask only blockers; end with one next-session line. |
| Legal point stated as fact | Best practice or judgment call, plus "not legal advice". |
| "1-pixel placeholder" | Code can't measure it: check live, or list it under "What we couldn't check". |
| Editing `src/lib/tracking.ts` | AI Studio owns it; repairs build beside it. |
Pliki w paczce (2)
- SKILL.md 5 KB
- references/crm-guide.md 3 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · tenaciousduck/ai-studio-website-skill | 100 | MIT |
| marcel-bich/marcel-bich-claude-marketplace | 100 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| friendlyinternet/nuxt-crouton | 100 | MIT |
| userKael/rastro | 100 | MIT |
| Archont561/qgis-agent-harness | 100 | MIT |
| lilly-logic-labs/lll-skills | 100 | MIT |
| Come-In-Labs/agent-skills | 100 | MIT |
| minanyang/10x-agent | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 4ff9982b8f7b (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90legal
Sprawdza, pisze lub poprawia regulamin sprzedaży, politykę prywatności, informację o cookies i tekst płatności w witrynie GoHighLevel. - 85ghl-ai-studio
Czyta, audytuje, buduje i publikuje strony tworzone w GoHighLevel AI Studio, a także wskazuje, która część GHL obsługuje konkretną stronę. - 90ghl-to-mermaid-stinger
Zamienia eksport JSON konta GoHighLevel na pliki per workflow i diagramy Mermaid, dla snapshotów GHL, map automatyzacji i eksportów SuperSnapshot AI. - 100highlevel-ai-studio-stinger
Obsługuje HighLevel AI Studio: strony Vibe, Content AI, Funnel i Website AI oraz strony WordPress AI, w tym budowę, publikację i diagnostykę. - 100ghl-funnels-pages
Buduje lejki, strony i witryny GoHighLevel przez wewnętrzne API: tworzy lejek i kroki, układa treść z natywnych elementów, wiąże kalendarze i produkty, ustawia śledzenie i SEO oraz domenę. - 100google-search-console
Dodaje stronę do Google Search Console: weryfikuje właściciela, sprawdza mapę witryny i robots.txt, wysyła mapę i wyjaśnia raporty nieindeksowania.