Bid Attachment Filename Rule Check
Check that the files listed in your submission instructions and folder are present.
Small business tender responses
US$11View skill
Tender Clarification Dependency Simulator
Trace the links between items in your proposed clarifications and requirement dependency map.
A downloadable skill for your AI agent.
Your result
Downstream sections to recheck before requesting changes.
Source references, missing information, and questions to review stay with the findings.
How to use it
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.
Provide your records
Proposed clarifications and requirement dependency map. Confirm the case and period you want to check.
Ask for the report
Copy the request below into your agent. Add the files and any task details it needs.
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 Tender Clarification Dependency Simulator skill. Review the attached records: proposed clarifications and requirement dependency map. Prepare this result: downstream sections to recheck before requesting changes. 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 follows the links you supply between items. Missing links and circular chains stay visible, so you can see what needs another check.
What you provide
Proposed clarifications and requirement dependency map.
Details it records
- Buyer requirement
- Prerequisite
- Proposed clarification
Read the full task logic
For this task, keep one review row for each response section + dependency node. Record buyer requirement, prerequisite, and proposed clarification. Keep the source location beside each value.
Trace each buyer instruction and supplied change through response, attachment, signature, price, and upload evidence.
Model response sections as nodes with requirement dependencies. Record proposed clarifications as unresolved changes, not approved amendments. Trace dependent sections for review and report questions that must be answered before changing the submission.
Do not infer compliance from a similar title. Use exact buyer rules, dates, file formats, and approval records.
Graph consistency does not establish full traceability, custody, quantity conservation, or dependency completion. Check those facts separately in the source-linked report.
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
| Sample record | node: node-A; parents: node-B |
|---|---|
| Sample record | node: node-B; parents: node-A |
What comes back
A difference needs review
- The links return to an earlier item and form a circular chain.
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": "response section + dependency node / SYNTHETIC-001", "node": "node-A", "parents": ["node-B"]} - source-r2 · records/r2
{"id": "r2", "key": "response section + dependency node / SYNTHETIC-001", "node": "node-B", "parents": ["node-A"]}
Checked values
- node: node-A; parents: node-B; record id: r1
- node: node-B; parents: node-A; record id: r2
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-resultExpected 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.
- A start guide to help you set up the skill.
- Task instructions that tell your AI what to check.
- Checking tools with worked examples.
- A report template with space for evidence and next actions.
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.
Collect the records
Start with proposed clarifications and requirement dependency map. Confirm the case, period, and source versions before the review.
Extract the task fields
Use tender, requirement, clarification, response section, submission version to keep records distinct. The agent records the original value, an exact quote, and the source location.
Trace the parent links
Follow the supplied parent links and report missing parents or cycles. Run the Python helper on the structured records. Check each finding against its source.
Complete the report
Prepare the task result: downstream sections to recheck before requesting changes. 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.