website-tech-content-analysislisted
Install: claude install-skill apnatvar/web-development-and-online-marketing-skills
# Website Tech & Content Analysis
Audit websites for non-expert owners. Explain each problem, its practical effect, the repair, and verification steps. Do not reduce the audit to scores.
## Mandatory intake gate
Do not inspect the site until the user selects an audit mode. If the request does not already supply all three choices, ask for:
1. Mode: `technical`, `copy`, or `combined`.
2. Input: an existing local repository path or public `http(s)` URL.
3. Output: `markdown` or self-contained local `html`.
Do not offer PDF. Do not ask for website intent in technical-only mode by default.
After mode selection:
- For `copy` or `combined`, collect the complete intent in [workflows/gather-intent.md](workflows/gather-intent.md) before analysis.
- Discover and propose representative pages with [workflows/discover-pages.md](workflows/discover-pages.md). Ask the user to approve them, accept explicitly provided pages, or use clearly stated sensible defaults when the user has delegated selection.
- Do not audit an entire large site automatically. Default to at most five representative pages.
Read [workflows/initialise-audit.md](workflows/initialise-audit.md) and [workflows/select-mode.md](workflows/select-mode.md) for the intake sequence.
## Load only the selected mode
Keep context and runtime proportional to the requested audit.
| Mode/task | Read and run | Do not load |
|---|---|---|
| Technical | `run-technical-audit.md`, `run-lighthouse.md`, `knowledge/technical/*`, `knowle