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.
Connection and schedule snapshots are synthetic. No Composio installation, authorization, Airtable read or Slack send occurred.
Original synthetic material. Try the input independently, then compare the reference results.
Original synthetic input
{
"synthetic": true,
"case": "composio-many-apps",
"data": {
"target_week": "2026-10-19/2026-10-26, end exclusive",
"connections": [
{
"toolkit": "Airtable",
"account": "editor@example.com",
"state": "ACTIVE"
},
{
"toolkit": "Slack",
"workspace": "Example content team",
"state": "EXPIRED"
}
],
"records": [
{
"id": "R01",
"title": "Email organization tutorial",
"date": "2026-10-20",
"status": "Ready to publish"
},
{
"id": "R02",
"title": "Inspection notes",
"date": "2026-10-22",
"status": "Draft"
},
{
"id": "R03",
"title": "Month-end review",
"date": "2026-10-28",
"status": "Ready to publish"
}
]
}
}Processing rules
Select only records inside the week with Ready to publish status. Connection state is not proof of table/channel permission or tool availability. Expired Slack means local draft only; do not bypass authorization. Airtable remains read-only; review final text and channel before delivery.
Complete reference results under this tutorial’s rules; nothing was written to a third-party service.Scroll horizontally within the table if needed.
| Item | Rule | Result | Current action |
|---|---|---|---|
| R01 | This week and ready | Selected | Include in checklist |
| R02 | This week but draft | Excluded | Do not change status |
| R03 | Ready but next week | Excluded | Do not move into current week |
| Slack | EXPIRED | Cannot send | Keep local draft and report blocker |
Ready this week: October 20 — Email organization tutorial [R01]. One item; not delivered.
Airtable ACTIVE does not establish table access. Expired Slack does not justify retrying a send through another path.
Cross-app schedule — synthetic exercise Window: October 19–26, end exclusive. R01 selected; R02 draft and R03 outside week excluded. Airtable snapshot ACTIVE, but no real table read. Slack EXPIRED; keep an unsent local draft. No schedule edits, plugin installation or account authorization.
Prepare the materials and check your tools
Start with the practice files
- Download connections and records; filter independently.
- October 19 inclusive, October 26 exclusive.
- Separate ACTIVE authentication from business permission.
Before using real services
- Verify plugin source, account and actual tools.
- Complete authorization yourself and keep keys out of prompts.
- Read one test row; review message and channel separately.
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 supplied connection states and Airtable records; select this week’s pending items and draft a Slack message.
Requires confirmation
Confirm account authorization, broader permissions and actual sending with the connected identity, target channel and complete message. Keep Airtable read-only.
Take over after a failure
Stop sending when authorization expires and have the user reconnect. After a timeout, inspect channel history and message ids before any resend.
Check tools and account identity
A connected app may be the wrong account and may lack target-specific access. Inspect capabilities without exposing credentials.
Inventory toolkit, account/workspace, state and unverified permissions from the snapshots. Read uploaded files only. Do not install, authorize or request secrets. Save capability.md.Two connection records.
ACTIVE is not all tools available; Slack EXPIRED stays visible.
Make filtering rules testable
Date and status must both match. Validate the file logic before touching a connected schedule database.
Filter the three records by target week and status. Explain every inclusion/exclusion. Do not promote drafts or move R03 into the week.Only R01 selected.
All three have outcomes and original statuses remain unchanged.
Read first, then build the checklist
Cross-app work needs a complete read before delivery. Keep title, date, count and source identity traceable.
Write the weekly checklist for R01 with date, title, record id and source scope. State this is a file exercise, not a real Airtable read. Keep missing fields unknown and save checklist.md.A one-record local checklist.
The count is 1 and the source remains R01.
Prepare delivery while retaining the connection blocker
A ready message is not a sent message. The expired Slack connection prevents delivery, not preparation.
Draft the full Slack message with the checklist and references. Mark EXPIRED and not sent. Do not reconnect, borrow another account or call sending tools. Return the draft and the exact user action needed.A draft and clear blocker.
No sent status or fabricated message id.
Validate live read and send separately
A successful connection does not prove a particular base or channel is readable. Check each target explicitly.
Inspect <Airtable base/table/view> read-only, at most 10 rows. After user reconnects Slack, inspect <workspace/channel> access. Preview final text and target; send once only with explicit approval and return the actual message id. Do not update Airtable.Read evidence and delivery status, or a blocker.
Airtable remains unchanged; sending requires a real returned identity.
Handle reruns and uncertain delivery
A timeout may occur after a successful send. Deduplicate by window, record identities and actual delivery state.
Draft a cross-app-checklist Skill with account checks, window/status rules, limits, references, delivery confirmation and deduplication. On uncertain send, read history before retrying. Propose a Routine only; expired access stops delivery and is reported.A reusable handoff method.
No repeat message for the same confirmed batch; failure is not no new content.
Find the evidence before choosing the next action
ACTIVE but the table is unreadable
Check target permissions and tool availability separately.
The schedule includes a draft
Reapply both time and status conditions.
Slack expired
Keep the file draft and let the user reconnect.
A send timed out
Check actual channel history/message identity before retrying.
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.
Connection and schedule snapshots are synthetic. No Composio installation, authorization, Airtable read or Slack send occurred.
- Composio: connected accounts ↗
Verify connected identity and authentication status; target-specific permissions still need separate checks.
- 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.