← 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": "Run a pre-release check of a website the user owns with Sitelemetry security, performance and accessibility audits, plus technical SEO when the site is meant to be indexed, then summarise launch blockers versus warnings using only measured results. Use when the user is about to launch, deploy, go live, migrate or redesign a site and wants to know what must be fixed first.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 340
},
{
"relative_path": "assets/icon-large.png",
"size_in_bytes": 33181
},
{
"relative_path": "assets/icon-small.png",
"size_in_bytes": 7770
}
],
"name": "pre-launch-check",
"skill_md_contents": "---\nname: pre-launch-check\ndescription: Run a pre-release check of a website the user owns with Sitelemetry security, performance and accessibility audits, plus technical SEO when the site is meant to be indexed, then summarise launch blockers versus warnings using only measured results. Use when the user is about to launch, deploy, go live, migrate or redesign a site and wants to know what must be fixed first.\n---\n\n# Pre-launch check\n\n## Ground rules\n\n- Follow the user's explicit instructions over the defaults in this skill, including which audits to run. These rules always apply, even when the user asks otherwise: check 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 check sites the user owns or is authorized to test. If that is not clear, ask first.\n- Reply in the user's language. For the audit tools, set `lang` as described in the `website-audit` skill.\n- The security audit sends test requests to the site. Depending on the account and on ownership verification, these can include active checks such as port and injection probes. Built-in checks send read-style requests and benign probes that are not meant to change the site but can appear in its server logs or firewall alerts. Tell the user before running it on a site that has not been audited before.\n- Use only the scores, severities and findings the tools return. Never invent a score, a pass or a measurement.\n\n## 1. Confirm the scope\n\n- **Target**: the public `https://` URL of the site. A staging site must be reachable over public HTTPS; localhost, private addresses and hosts behind a VPN cannot be audited. A staging hostname is a separate host from the production one.\n- **Verification**: the security audit's protected checks need current ownership verification of that hostname (see the `domain-verification` skill). The performance, accessibility and SEO audits do not.\n- **Indexing**: ask whether the site should be indexed by search engines at launch. Include `audit_seo` only if it should. On a staging site that is deliberately `noindex`, indexation findings are expected; say so rather than listing them as blockers.\n- **Runs**: state which audits you will run and that each one uses the account's audit allowance, then start them without waiting for another reply. Mention `audit_full` only if the user asks for a single run, and note that its full scope needs current ownership verification of the hostname, which the separate performance, accessibility and SEO audits do not. `audit_full` measures performance on mobile unless you send `strategy: \"desktop\"`.\n\n## 2. Run the audits one at a time\n\nWhen the user names the audits, run exactly those. Otherwise use this order:\n\n1. `audit_security`\n2. `audit_performance` with `strategy: \"mobile\"` (add a `desktop` run only if the user asks)\n3. `audit_accessibility`\n4. `audit_seo`, if indexing is in scope. Leave `maxPages` at its default unless the user asks. A site that is not live yet usually has no Search Console data; the audit still runs without it. Send `includeSearchConsole: false` if the user does not want Search Console data used.\n\nFor each audit:\n\n- Wait for the result before starting the next. If a call times out, repeat the identical call once, as described in the `website-audit` skill. Never start a duplicate audit.\n- Keep the same `target` and `lang` on every call.\n- If the text begins \"Audit not started\", or `structuredContent.status` is `action_required`, no audit ran and no allowance was used:\n - A verification reason on `audit_security` (`target_verification_required`, `target_reverification_required` or `verification_scope_required`): record security as not measured, continue with the other audits, and point to the `domain-verification` skill.\n - `entitlement_required` or `usage_limit_reached`: note it neutrally with the link from the result text, record that audit as not run, and continue with the other audits.\n - Any other reason, for example a busy or temporarily unavailable service: wait a little and retry the same call once; if it is refused again, record that audit as not run and continue.\n- If a security result is partial because some checks need verification, record those checks as not measured.\n- On an error, note it and continue with the next audit.\n\n## 3. Classify the results\n\nKeep the severities the tools assign; do not re-grade them.\n\n- **Blockers**: critical and high findings.\n- **Warnings**: medium findings.\n- **Notes**: low and info findings.\n- **Not measured**: checks, areas or metrics that the results mark as unavailable, partial or failed, audits outside the connected account's access, and any audit that did not run. These are unknowns, not passes.\n\nWhen the same issue appears in two audits, list it once and name both.\n\n## 4. Report\n\nUse this structure:\n\n```text\nPre-launch check for https://example.com/ (date)\nAudits: security finished, performance (mobile) partial, accessibility finished, SEO not run (site not indexed yet)\n\nBlockers (2)\n1. [security, high] <title> at <affected location>: <fix>\n2. [accessibility, high] <title> at <affected location>: <fix>\n\nWarnings (3)\n...\n\nNotes (4): one line each, or a count if there are many\n\nNot measured\n- performance: <what was unavailable, from the result>\n\nScores returned: security <score> (<grade>), accessibility <score>\n```\n\nTake the affected location from the `Affected location:` line in a finding's `evidence`. Only list scores that the tools returned as numbers. A null score means the area was not measured.\n\nVerdict:\n\n- With blockers: \"Not ready yet: fix these N blockers first\", followed by the blockers in order of severity.\n- Without blockers: \"No blockers were found in the measured checks\", followed by the Not measured list. Never claim that the site has no issues or meets a standard; the audits cover specific automated checks.\n\nOffer the `fix-and-retest` skill for the blockers and, after fixes, a re-run of the same audits with the same arguments.\n"
}SHA-256 of public snapshot: c08cca7ed41eb5f56ceb0756b635df891c1e48166d839360d8c752dcafa54df1