← SitelemetryCONTENT HISTORY
WHAT CHANGED
Update to Sitelemetry
Snapshot Nov 18, 2026 · 18:11 UTC · version 2.5.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Sitelemetry and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Turn Sitelemetry audit findings into concrete fixes for the user's stack (nginx, Apache, Cloudflare, Vercel or Next.js, Netlify, WordPress), apply them with the user's approval or hand them over ready to use, then re-run the same audit on the same target and report honestly what is resolved, still open or not measured. Use after an audit when the user asks how to fix the findings, wants the changes made, or wants to confirm that a fix worked.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 349
},
{
"relative_path": "assets/icon-large.png",
"size_in_bytes": 33181
},
{
"relative_path": "assets/icon-small.png",
"size_in_bytes": 7770
},
{
"relative_path": "references/stack-snippets.md",
"size_in_bytes": 7084
}
],
"name": "fix-and-retest",
"skill_md_contents": "---\nname: fix-and-retest\ndescription: Turn Sitelemetry audit findings into concrete fixes for the user's stack (nginx, Apache, Cloudflare, Vercel or Next.js, Netlify, WordPress), apply them with the user's approval or hand them over ready to use, then re-run the same audit on the same target and report honestly what is resolved, still open or not measured. Use after an audit when the user asks how to fix the findings, wants the changes made, or wants to confirm that a fix worked.\n---\n\n# Fix and re-test\n\n## Ground rules\n\n- Follow the user's explicit instructions over the defaults in this skill. These rules always apply, even when the user asks otherwise: change and re-test only sites the user owns or is authorized to test; never ask for passwords, API tokens or other credentials; never recommend a different account level, mention costs or suggest changing the account; never invent scores, findings or other results.\n- Only change and re-test sites the user owns or is authorized to test.\n- Reply in the user's language. For the audit tools, set `lang` as described in the `website-audit` skill.\n- Base every fix on a returned finding: its evidence, impact and `remediation`. If you suggest something the audit did not report, label it as an extra suggestion.\n- Never say a fix worked until a re-test has measured it.\n\n## 1. Start from real findings\n\nUse the findings of an audit from this conversation. If there are none, run one first with the `website-audit` skill. For every finding, note its `findingKey`, severity, title and affected location (the `Affected location:` line in `evidence`, when present). Also note the exact tool and every argument of that run (`target`, `lang`, and any of `modules`, `maxPages`, `strategy`, `includeSearchConsole`, `searchConsoleDays`, `promptLimit`, `brand` or `competitors` that were used, with `competitors` in the same order). The re-test must repeat them.\n\n## 2. Identify the stack\n\nAsk the user, or infer it from the project when you can read its files. If the stack is unknown, write the fixes in stack-neutral terms first, in the same answer, and ask for the stack only to give exact snippets.\n\n| Signal | Stack |\n|---|---|\n| `nginx.conf`, `sites-available/`, `conf.d/` | nginx |\n| `.htaccess`, `httpd.conf`, `apache2.conf` | Apache |\n| Site proxied through Cloudflare, rules in the Cloudflare dashboard | Cloudflare |\n| `vercel.json`, `next.config.js`, `next.config.mjs`, `next.config.ts` | Vercel or Next.js |\n| `netlify.toml`, `_headers`, `_redirects` | Netlify |\n| `wp-config.php`, `wp-content/` | WordPress |\n\nWhen a CDN or proxy sits in front of the origin, it can add, replace or cache headers. Decide which layer owns each header and set it in one place.\n\n## 3. Write the fixes\n\nWork from critical to info. For each finding give:\n\n- what changes and where (file path or dashboard location);\n- the change for the user's stack, adapted to the site;\n- the risk and how to roll it back;\n- how to check it before re-testing, for example `curl -sI https://example.com/` for response headers.\n\nStarting points for common findings (security headers, HTTPS redirect, HSTS, server version disclosure, caching, compression and email DNS records) are in [stack snippets](references/stack-snippets.md). Load it when you write a fix for one of these; adapt the snippets to the site and do not paste them blindly.\n\nSafety rules:\n\n- **Content-Security-Policy**: start with `Content-Security-Policy-Report-Only`, check the browser console for violations, then enforce. A strict policy copied without testing breaks sites.\n- **HSTS**: start with a short `max-age`. Add `includeSubDomains` only when every subdomain serves HTTPS, and `preload` only when the owner decides to submit the domain to browser preload lists.\n- **DNS and email records** (SPF, DKIM, DMARC, CAA): the user changes these at their DNS provider. Start DMARC at `p=none` with reports before moving to `quarantine` or `reject`.\n- Never ask for or handle passwords, API tokens or hosting and DNS credentials.\n\n## 4. Apply or hand over\n\n- When you can read and edit the project's files: show the diff and apply it only after the user agrees. Do not deploy, restart services or change production settings on your own.\n- Without file access: give complete, copy-ready changes and the order to apply them in.\n- Ask the user to tell you when the changes are live. If the site uses a CDN or page cache, ask them to purge it so the re-test sees the new responses.\n\n## 5. Re-test the same way\n\n- Tell the user that the re-test is a new audit run and uses the account's audit allowance.\n- Call the same tool with the same `target` spelling and exactly the same arguments as the first run, including `lang`. A different scope or language makes the comparison invalid and counts as a separate audit.\n- Re-test only after the changes are live and at least about two minutes after the first run finished. An identical call made within about two minutes after the first run finished can return the earlier result instead of measuring again.\n- Handle errors, \"Audit not started\" prerequisites and slow audits as in the `website-audit` skill: one audit at a time, and repeat the identical call once if a call times out.\n\n## 6. Report before and after\n\nMatch findings across the two runs by `findingKey`.\n\n| Result | Rule |\n|---|---|\n| Resolved | In the first run, absent from the re-test, and the check was measured in the re-test |\n| Still open | Present in both runs |\n| New | Present only in the re-test |\n| Not measured | The check or area was unmeasured, unavailable or partial in the re-test (see `coverageStatus` and `auditDetails` when present, and for `audit_full` the areas in `pillars`, `failedPillars` and `complete`). Do not count it as resolved. |\n\nShow a table with the finding, severity, before, after and result. Report a score change only when both runs have a non-null score, and mention that scores can move for other reasons too, such as lab variance in performance measurements, a different number of pages or questions after the account's caps, or new Search Console data. If `findingsTruncated` was true in either run, say that the comparison covers only the returned findings.\n\nEnd with what is still open and the next step for each item.\n"
}SHA-256 of public snapshot: 0d6796a61f296df47b616abb5d8b70e076fbf5dbd06c57303762113cb6530e94