Check the input, then compare the complete deliverables
Explore the original materials, item-by-item outcomes and full report below. Attempt the input independently before using the reference to find omissions or disagreements.
The fixture and reference report below are synthetic. A separate run on 2026-10-18 checked three public site URLs by HTTP, including an expected 404 control. See the verification record; browser rendering, business backends and Routines remain untested.
Original synthetic material. Try the input independently, then compare the reference results.
Home HTML
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><meta name="robots" content="noindex,nofollow"><title>Home — synthetic fixture</title><style>body{font:16px/1.9 system-ui,sans-serif;background:#faf9f6;color:#222321;max-width:760px;margin:48px auto;padding:0 22px}a{color:#ad421f}nav{display:flex;gap:24px}img{max-width:100%}.note{padding:16px;border:1px solid #ddd;background:white}</style></head><body><p class="note">shancha synthetic inspection fixture. Intentional faults; not a production site.</p><nav><a href="/en/recipes/website-daily-check/files/site-about.html">About</a><a href="/en/recipes/website-daily-check/files/site-pricing-missing.html">Pricing</a></nav><h1>A site waiting for inspection</h1><img width="80" height="80" alt="Fixture logo" src="/en/recipes/website-daily-check/files/site-logo.svg"><section id="features"><h2>Features</h2><p>Practice finding broken links, missing images and nonexistent anchors.</p></section><img alt="Intentionally missing banner" src="/en/recipes/website-daily-check/files/site-banner-missing.svg"></body></html>About HTML
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><meta name="robots" content="noindex,nofollow"><title>About — synthetic fixture</title><style>body{font:16px/1.9 system-ui,sans-serif;background:#faf9f6;color:#222321;max-width:760px;margin:48px auto;padding:0 22px}a{color:#ad421f}nav{display:flex;gap:24px}img{max-width:100%}.note{padding:16px;border:1px solid #ddd;background:white}</style></head><body><p class="note">shancha synthetic inspection fixture. Intentional faults; not a production site.</p><h1>About this exercise</h1><p>A page can open while its navigation targets are broken.</p><p><a href="/en/recipes/website-daily-check/files/site-index.html#features">Features: valid anchor</a></p><p><a href="/en/recipes/website-daily-check/files/site-index.html#contact">Contact: intentionally missing anchor</a></p></body></html>Access method
Open fixture pages on the machine running this preview. A cloud Bot reading site-fixture.json can analyze files and simulated responses; it must not claim to have requested your local server.
Complete reference results under this tutorial’s rules; nothing was written to a third-party service.Scroll horizontally within the table if needed.
| Item | Target | Observation | Evidence | Next |
|---|---|---|---|---|
| C01 | Home | HTTP200 | Page opens; inspect referenced targets | Status OK |
| C02 | About | HTTP200 | Page opens; inspect anchors | Status OK |
| C03 | Home → Pricing | Target HTTP404 | site-pricing-missing.html absent | Fix link |
| C04 | Home → Banner | Resource HTTP404 | site-banner-missing.svg absent | Supply image |
| C05 | About → Home #contact | Page200; anchor absent | No id="contact" on Home | Review navigation |
Both pages open; faults are in their referenced links, images and anchors.
Preserve source/target evidence. Editing addresses, assets and deployment are separate work.
Inspection report — synthetic fixture Scope:2 HTML pages and their explicit targets. 3 intentional issues: pricing 404, banner 404, missing contact anchor. Normal: both pages 200, logo exists, features anchor exists. HTTP success does not establish link/image/content health. Suggestions: verify pricing address, supply/remove the banner reference appropriately, correct contact navigation. No site edits or deployment; recheck identical targets after a separately authorized repair.
Prepare the materials and check your tools
Start with the practice files
- Download site-fixture.json before expected findings.
- Open the fixture on the machine serving this site.
- Inspect original resources before checking the reference.
Before using real services
- Specify a site/path you manage or are authorized to inspect.
- Exclude login, payments, submissions and state changes.
- Cloud localhost is not your Mac; use uploaded files or the same local machine.
Complete one file-based exercise first. For real services, verify the actual account, available tools and operation scope, then follow the acceptance check at each stage.
Download the original input and rules ↓Execution and takeover boundaries
The actions below require the agreed inputs, accounts and scope. Configuring a Routine does not expand that authorization.
Can run automatically
Inspect agreed URLs and paths read-only; record responses, links, screenshots and anomalies in a local report.
Requires confirmation
Confirm login, expanded crawling, form submissions, site changes, deployment, Routine frequency and notification destinations.
Take over after a failure
Separate network or login failures from site faults and preserve responses and stopping points. Pause recurring checks; validate manually after user takeover.
Define entry points, scope and stopping conditions
An unbounded site check can drift into admin pages, external sites or form submissions.
This fixture has two HTML pages and a few resources. Real checks should begin with a homepage and one core path.
Read site-fixture.json and create scope.md: entries, internal links, images, anchors and planned evidence. Separate file inspection from real HTTP checks. Do not access external sites, submit forms, log in or edit pages.A page/resource/anchor plan.
Scope does not expand; evidence origins are explicit.
Extract every referenced target from source
Keep the source page beside href/src. An anchor requires checking both the destination page and target id.
Simulated status is useful training data, not proof of a real request.
Using uploaded HTML/resource lists only, map href, src and fragment targets. Check resource presence and actual ids, retaining source snippets. Label results simulated; do not claim network requests or read expected-findings.csv yet.Source → target → evidence mapping.
Pricing, banner and contact can be located in source; external links are not followed.
Verify status and rendering where accessible
Cloud localhost points to the cloud machine. Failure to reach your Mac does not prove a public-site outage.
For real requests, record final URL, status, time and failure reason; retain auth/rate limits as unchecked.
Only in a confirmed accessible local environment, check scoped fixture targets read-only. Record HTTP status and browser evidence for missing image/anchor. Distinguish404, network, authentication and content errors with URLs/times. If inaccessible, analyze uploaded files and state the limit.Dated actual evidence or an access blocker.
HTTP200 is not site health; simulation and actual requests remain separate.
Report faults, impact and unchecked scope
A reader should reproduce each issue from the same source path.
No business data means no invented revenue loss; a static page does not establish backend health.
Write scope, normal items, issues, unchecked areas, evidence and recheck methods. Each issue needs source page, target, observation, possible impact and minimal suggestion. Do not estimate revenue loss or assert causes without evidence. Do not edit/deploy.A report with three intentional issues.
Each finding has an evidence type and reproducible target.
Review repair intent and recheck the same list
Confirm the correct pricing address, banner and contact purpose. Removing every broken reference may defeat the product requirement.
This tutorial stops at a repair plan; implementation and deployment need their own scope.
Propose minimum repairs with files/targets, missing correct addresses/assets and rechecks. Ask for missing evidence instead of deleting links or changing production. Implement only after later specific authorization and validate the same targets.Three repairs with matching rechecks.
Suggestions preserve the original purpose and are not called completed repairs.
Save the method and notify on differences
Fix frequency, time zone and targets after a manual check. Last run’s success is not this run’s result.
Distinguish new faults, persistent faults, recovery and failure to inspect.
Draft a site-check Skill with authorized scope, read-only checks, limits, timeouts/rate limits, evidence, diffs and recovery notices. Propose once-daily Routine with user-confirmed time zone only. Stay quiet unchanged; report inability to inspect. Do not edit, open PRs, deploy or contact Bots.A reusable inspection method and schedule proposal.
Each run has a new timestamp; no-change, failure and recovery differ.
Find the evidence before choosing the next action
Cloud localhost fails
Use uploaded fixtures or the machine running the server; do not call it a public outage.
Both pages return 200
Inspect referenced links, images and anchors.
401, 403 or verification page
Mark access-limited/unchecked without bypassing.
Many duplicate findings
Group by source/target and explain whether counts mean issues or references.
An old alert remains after repair
Recheck the same target and record recovery without rewriting history.
Check every item before finishing
These page-local checkboxes reset on refresh. Checking them does not verify a real service connection.
Checked 0 / 6 items
Download the inputs separately from the reference answers
Start with input and rules without showing the reference answers. After acceptance, save the report and complete prompt set.
site-fixture.json↓Reference findingsTwo pages and three intentional faults.expected-findings.csv↓Reference inspection reportScope, faults and rechecks.inspection-report.md↓Open fixture homeIntentional broken link and missing image.site-index.html↗Open fixture aboutValid and invalid anchor links.site-about.html↗Fixture logoExisting resource to compare with the missing banner.site-logo.svg↗All stage prompts6 instructions with acceptance checks.practice-prompts.txt↓Check documented capabilities and exercise results separately
Content updated: · Editing a page does not reverify its sources or live workflow.
Documentation review: Reviewed within the recorded scope ·
Reviewed HTTP status classes, read-only inspection and actual Routine tests. Status codes do not establish business correctness; schedules and dashboards remain untested.
Documentation review evidence and limits ↗
Live workflow verification: Partial verification · includes failed checks ·
Partial: Grok Bot made one-time HTTP reads of three real public URLs, returning 200/200/expected 404. The Gmail boundary anchor and three headings were checked. Requests and source inspection only; browser clicks, image rendering, backends, repairs and Routines remain untested. The negative control is not a production fault.
Last execution attempt: · An attempt date does not establish a passed verification.
The fixture and reference report below are synthetic. A separate run on 2026-10-18 checked three public site URLs by HTTP, including an expected 404 control. See the verification record; browser rendering, business backends and Routines remain untested.
- MDN: HTTP response status codes ↗
Distinguish successful responses, redirects and errors. The fixture faults are intentionally authored examples.
- Grok Bot: apps and the shared computer ↗
Check connected accounts, available tools, visibility and user takeover.
- Grok Bot: Skills and Routines ↗
Validate a manual run before saving a method or scheduling it.
Try another small batch of your own material
Retain original input and operation records. Verify that each result can be traced before adding connections or recurring runs.