Event Volunteer Arrival Coverage
Check your volunteer slots and check-ins for missing supporting records.
Event operations
Check your release forms and proposed recordings for missing supporting records.
A downloadable skill for your AI agent.
Unlinked permission evidence.
Source references, missing information, and questions to review stay with the findings.
Open your download and follow the start guide. Use an AI agent that can load skill files and run the included tools.
Release forms and proposed recordings. Confirm the case and period you want to check.
Copy the request below into your agent. Add the files and any task details it needs.
Check the findings against the original records. Choose where to save the report and follow up on open questions.
Use the Event Speaker Consent Asset Crosscheck skill. Review the attached records: release forms and proposed recordings. Prepare this result: unlinked permission evidence. Include a source reference for each finding. List missing information and questions that need my review. Ask me to confirm the scope and where to save the report before you start.
It lists the evidence each item needs, then looks for a matching record. Missing records and unclear matches stay in the report.
Release forms and proposed recordings.
For this task, keep one review row for each recording + permission. Record speaker ID, proposed use, and release scope. Keep the source location beside each value.
Map each vendor commitment to a timeline, resource, approval, and payment. Preserve setup, service, and removal windows separately.
Use approved venue limits and plans. A document comparison does not establish electrical, structural, or event safety.
A matching key proves only that a supplied record exists. Inspect its content and required fields before calling the requirement satisfied.
This synthetic example shows the included check in use. Your agent uses its findings to complete your task report.
Synthetic example records
| Starting record | One required supporting record |
|---|---|
| Observed | No records supplied |
A difference needs review
This result comes from the checking tool in your download.
These are synthetic records from the bundled example.
{"id": "e1", "key": "recording + permission / SYNTHETIC-001"}After purchase, extract the ZIP. Run these commands from the skill folder. Use a new output folder.
python3 scripts/checks.py
python3 scripts/audit.py assets/example.json \
--files-root assets/sample-files --output-dir example-result
Expected exit code: 1. Code 0 means no helper finding. Code 1 means a finding or review item. Code 2 means incomplete or invalid input.
The check uses the records you supply. Review each finding against the original documents.
Ask your agent to save the completed task report in a folder you choose. The report template includes the result, source references, missing information, and next actions.
Tonotes does not receive your work documents through this website. Documents you share with an AI service follow that service's storage settings.
US$11 includes one skill in a ZIP with 18 files. You receive the instructions and tools to run the task with your own records.
Use an agent that supports SKILL.md instructions and Python 3.10 or later with SQLite. Your AI-agent service is separate.
Start with release forms and proposed recordings. Confirm the case, period, and source versions before the review.
Use event, vendor, location, time slot, contract revision to keep records distinct. The agent records the original value, an exact quote, and the source location.
Compare required items with observed evidence using exact keys. Run the Python helper on the structured records. Check each finding against its source.
Prepare the task result: unlinked permission evidence. Include missing evidence, unresolved questions, and the next action for each open item.
Eight synthetic cases check the tool locally. Live-agent accuracy on real documents has not been tested.