School Office Repeated Form Request Map

Find possible duplicate entries in your request logs.

A downloadable skill for your AI agent.

Your result

Families receiving duplicate administrative requests.

Source references, missing information, and questions to review stay with the findings.

How to use it

  1. Add the skill to your AI

    Open your download and follow the start guide. Use an AI agent that can load skill files and run the included tools.

  2. Provide your records

    Request logs. Confirm the case and period you want to check.

  3. Ask for the report

    Copy the request below into your agent. Add the files and any task details it needs.

  4. Review and save

    Check the findings against the original records. Choose where to save the report and follow up on open questions.

Example request

Use the School Office Repeated Form Request Map skill. Review the attached records: request logs. Prepare this result: families receiving duplicate administrative requests. 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.

What it checks

It groups records with matching values. You review the proposed groups before deciding whether they describe the same event.

What you provide

Request logs.

Details it records

  • Form type
  • Request date
  • Separate request occurrence
Read the full task logic

For this task, keep one review row for each family + request signature. Record form type, request date, and separate request occurrence. Keep the source location beside each value.

Use school-approved rosters and checklists. Distinguish a payment from consent, attendance from booking, and a request from an approved arrangement.

Preserve pickup permissions and contact versions. Report missing evidence to staff rather than making participation decisions.

A repeated signature is a candidate duplicate. Legitimate repeat events can have the same content. Do not delete, merge, or accuse a party automatically.

Example result

This synthetic example shows the included check in use. Your agent uses its findings to complete your task report.

What you provide

Synthetic example records

Synthetic inputs for School Office Repeated Form Request Map
Sample recordform type: signature-A
Sample recordform type: signature-A

What comes back

A difference needs review

  • These records contain matching values. Check whether they describe separate events.

This result comes from the checking tool in your download.

Read the source records

These are synthetic records from the bundled example.

  • source-r1 · records/r1
    {"id": "r1", "key": "family + request signature / SYNTHETIC-001", "value": {"form type": "signature-A"}}
  • source-r2 · records/r2
    {"id": "r2", "key": "family + request signature / SYNTHETIC-001", "value": {"form type": "signature-A"}}

Checked values

  • records: 2; distinct values: 1
Run this example

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.

What is saved

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.

A readable check report
The local checking tool can save its findings as report.md.
A data copy
The same check can be saved as report.json for use in other tools. A local audit database is optional.

Tonotes does not receive your work documents through this website. Documents you share with an AI service follow that service's storage settings.

Your download

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.

Setup and file details

Use an agent that supports SKILL.md instructions and Python 3.10 or later with SQLite. Your AI-agent service is separate.

Start guide: 1 file
START-HERE.md explains setup and the expected example result.
Agent instructions: 1 file
SKILL.md defines this task and its completion checks.
Task references: 4 files
The task guide, input contract, tools guide, and research notes.
Python tools: 4 files
Check records, convert CSV input, and run the local checks.
Examples and templates: 8 files
The input schema, synthetic cases, expected report, and report template.
  1. Collect the records

    Start with request logs. Confirm the case, period, and source versions before the review.

  2. Extract the task fields

    Use student ID, event ID, form version, roster date to keep records distinct. The agent records the original value, an exact quote, and the source location.

  3. Find repeated records

    Group exact matching values and report duplicate candidates. Run the Python helper on the structured records. Check each finding against its source.

  4. Complete the report

    Prepare the task result: families receiving duplicate administrative requests. 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.