audit-website-quality

Audit a website or page against the full quality policy bank (SEO, accessibility, performance, responsive layout, security, content/anti-slop, link integrity, and structured data) and produce graded findings. Use when reviewing a site before launch, auditing an AI- or template-generated site, checking "is this site actually good", or diagnosing why a page ranks/converts/reads poorly. Works on any site regardless of how it was built. Triggers include "audit my site", "review this website", "is this page ready to ship", "check SEO and accessibility", "why does this site feel generic".

Aller à l'installation

Dépôt: ariaxhan/the-agent-library
Dernière activité de la source: 28 juin 2026 à 04:02
Langue détectée de SKILL.md: anglais
Étoiles: 1
Forks: 0

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/ariaxhan/the-agent-library --skill audit-website-quality

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers

2 fichiers

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

extract-invariants

Turn a borrowed metaphor, analogy, or cross-domain inspiration into a testable mechanism, or prove it is decoration and discard it. Use when a design leans on language from another field ("immune system", "evolution", "market", "quorum", "crystallization"), when someone proposes copying how another domain solves a problem, or when reviewing a system whose names sound deeper than its code. Produces either a named domain-free invariant with evidence and falsifiers, or an explicit rejection with the reason it failed.

2026-07-20

design-loud-failures

Design systems so a failure can never present as success. Use when building or reviewing pipelines, extractors, reconciliations, checkers, or any computation whose output humans act on; when missing inputs, unreadable files, or crashes could pass silently; when a tool "found" an explanation that feels too convenient; or on "make this fail loudly", "could this lie to us", "harden the failure paths". Produces named invariants, explicit skip and no-answer states, honest cause classes, and adversarial regression fixtures.

2026-07-10

debate-decisions

A compact decision protocol for non-trivial choices, reviews, governance calls, and live disagreement. Use implicitly at decision points, even when nobody says "debate", whenever a choice is high-impact, hard to reverse, policy-bearing, or has multiple plausible paths that evidence alone cannot settle. Skip for trivial, cheap-to-reverse, or deterministically decidable choices.

2026-07-07

Tout voir dans ce dépôt

Audit Website Quality

A website is judged on many axes at once, and AI- or template-generated sites tend to look finished while failing the boring, structural ones: weak SEO, broken accessibility, invented facts, layout that collapses on a phone. These are not matters of taste. They are validations: each one is either satisfied or it is not, and you can check it. Treat this as an inspection, not a vibe.

The deepest failure is content the page cannot back up: invented hours, hallucinated claims, generic AI copy. A good site only states facts that trace to a real source. Hold every page to that.

1. Map the surface first

Before checking anything, establish what you're auditing:

The pages/templates in scope and what each is for (convert, inform, rank, capture a lead).

How it's built and served (static, SSR, client-only SPA): this decides crawlability and performance lenses.

What's a real fact vs. filler copy. You'll need this for the content lens.

2. Run each lens

Check every lens that applies. Each produces pass/fail observations, not opinions.

Structure & semantics

Exactly one <h1> per page. Headings nest in order (no skipping levels for size). Landmark elements (header, nav, main, footer) present. Content is in semantic HTML, not a soup of s. Required and present and page-specific.

name

audit-website-quality

description