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.
All platform numbers are synthetic. No platform page, dashboard or live Sheets account was accessed.
Original synthetic material. Try the input independently, then compare the reference results.
Original synthetic input
{
"synthetic": true,
"case": "sheets-audience-tracker",
"data": {
"previous": "2026-10-05T09:00:00+08:00",
"current": "2026-10-12T09:00:00+08:00",
"platforms": [
{
"id": "A01",
"platform": "X",
"metric": "followers",
"previous": 1000,
"current": 1040
},
{
"id": "A02",
"platform": "YouTube",
"metric": "subscribers",
"previous": 500,
"current": null,
"reason": "Page not obtained"
},
{
"id": "A03",
"platform": "Newsletter",
"metric": "subscribers",
"previous": 20,
"current": 0
},
{
"id": "A04",
"platform": "Blog",
"metric": "followers",
"previous_display": "1.1K",
"current_display": "1.2K",
"precision": "approximate"
}
]
}
}Processing rules
Retain platform, metric, observation time, raw display and precision. Calculate exact differences only with comparable exact values in both periods. Missing is not zero or the previous value. Rounded displays are not exact counts. Deduplicate by platform + metric + observation batch before writes.
Complete reference results under this tutorial’s rules; nothing was written to a third-party service.Scroll horizontally within the table if needed.
| Platform | Current result | Change | Evidence and next step |
|---|---|---|---|
| X | 1040 | +40 | Exact values; same metric |
| YouTube | Missing | Not calculated | Retain read failure; neither 500 nor 0 |
| Newsletter | 0 | -20 | Explicit synthetic zero, not missing |
| Blog | 1.2K, approximate | No exact difference | Preserve raw 1.1K → 1.2K |
X increases by 40; Newsletter decreases by 20. Each has two exact values with the same definition.
YouTube is missing; Blog is rounded. Neither belongs in an exact-change calculation.
Audience log — synthetic snapshots Batch: 2026-10-12 09:00 +08:00. X followers: 1040, +40 from October 5. YouTube subscribers: missing; no change calculated. Newsletter subscribers: 0, -20. Blog followers: displayed 1.2K; approximate, no exact increase inferred. All four have status records. Nothing appended to Sheets.
Prepare the materials and check your tools
Start with the practice files
- Download both snapshots and the rules.
- Calculate independently before reading the reference.
- Store data status separately from the value.
Before using real services
- Choose your own platforms and the exact sheet/tab.
- Handle login yourself; failed reads do not mean zero.
- Read existing keys before confirming an append and readback.
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
Organize platforms, metrics, observation times and precision from agreed snapshots; calculate changes only between comparable exact values.
Requires confirmation
Confirm live read scope, the target Sheet and write batch, overwriting existing rows and the Routine schedule.
Take over after a failure
Mark unread sources as missing rather than reusing old values. Inspect platform, metric and batch keys after uncertain writes; manually verify before retrying failed items only.
Align platforms, metrics and observation times
Followers, subscribers and paid subscribers are different measures. Establish the metric and observation times before comparing values.
Inventory the four platforms, metric names, two times and raw displays in source-data.json. Do not browse or fill current values. Save metric-index.md.A metric/time index.
Keep followers and subscribers distinct with both times explicit.
Assign exact, missing and approximate states
A status column prevents fabricated precision. Keep rounded strings as supplied so they remain useful without pretending to be exact.
Mark exact, missing or approximate. Keep unknown numbers null, YouTube’s reason, Newsletter’s exact 0 and Blog’s 1.2K string. Do not convert 1.2K into an exact 1200.Values with explicit status.
Missing is neither zero nor a carried-forward value.
Calculate changes only where comparable
Both periods must share a definition and precision. Percentage change additionally requires a nonzero base.
Calculate differences only for two exact values. Do not calculate percentages with a zero base. Show formulas and reasons for no calculation; do not total different platforms or fill missing values.X +40 and Newsletter -20.
YouTube/Blog have no exact change and a reason.
Prepare one reviewable observation batch
Batch identity distinguishes observations and prevents duplicate appends when retrying the same run.
Produce CSV with batch, platform, metric, raw display, numeric value, status, change and reason. Retain all four rows and mark not written. Compare with the reference; separate missing from decline.Four local rows and a weekly summary.
YouTube missing and Newsletter -20 are both present.
Read the target sheet before appending confirmed rows
Sheets append does not identify business duplicates. Check the tab and existing keys, then read back actual writes.
Inspect <sheet id/tab> for platform+metric+batch keys. Preview four proposed rows. After specific confirmation, append raw values, record the returned range and read it back. On ambiguous failure, check existing keys before retrying; do not overwrite history or reveal keys.Verified append evidence or an unwritten file.
A same-batch retry does not add another copy.
Read fresh status on every observation
A successful previous read is not a successful current read. Platform changes and expired access must remain visible.
Draft an audience-tracker Skill covering scope, definitions, batches, missing/approximate rules, calculations, deduplication and readback. Propose a Routine only. Stay quiet for no changes; report failed reads or changed definitions without rewriting old records.A reusable observation method.
A failed next run cannot reuse old counts as current.
Find the evidence before choosing the next action
The page only shows 1.2K
Retain the rounded display and precision; do not claim exact growth.
An unread value became zero
Separate value and status; zero requires an explicit source value.
The same week was appended twice
Check batch keys and read back after a timeout.
The platform changed its metric
Create a new definition version and stop direct comparisons across it.
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.
source-data.json↓Rules and scopeDefinitions, exceptions and delivery requirements.workflow-rules.md↓Item-by-item reference resultsCompare every input with its outcome.expected-results.csv↓Complete reference reportResults, evidence and missing information.reference-report.md↓All stage prompts6 instructions with expected outputs and 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: Unverified · no review date recorded
No case-specific documentation review is recorded. References below are provided for review and do not establish verification.
Live workflow verification: Unverified
Live accounts, external writes, scheduled execution and long-term operation are unverified. Synthetic exercises and page checkboxes do not establish live verification.
All platform numbers are synthetic. No platform page, dashboard or live Sheets account was accessed.
- Google Sheets: append values ↗
Appending does not deduplicate business records. Verify the target range and read back actual writes.
- 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.