dock-assignment-pass-pdf
Skill14 starsChanged 10 days agoMITView on GitHub
Render the completed truck loading-dock assignment as a driver-facing one-page PDF.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- rubric-scoringSkill
- required-fields-progressSkill
- category-subcategory-resolverSkill
- html-report-generationSkill
- dataverse-mcp-saveSkill
- file-usecase-extractionSkill
- confirmation-final-qaSkill
- usecase-strengthening-gapsSkill
- prorated-refund-calculatorSkill
- points-reconciliationSkill
- slip-pdf-generatorSkill
- membership-card-pngSkill
- legal-compliance-reviewSkill
- internal-consistency-reviewSkill
- generating-podcast-scriptSkill
- spreadsheet-data-analysis-reportingSkill
- polished-report-builderSkill
- newsletter-style-email-composerSkill
- loading-dock-selectorSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill only after the agent has presented the completed loading-dock recommendation and the driver has explicitly asked for a PDF …
- Very specific: line 14
Always run the bundled dock_assignment_pass.py script.
- Distinctive: line 32
Use the accepted driver-facing content retained for the active loading plan.
- Very specific: line 44
Never pass or display ready_for_pickup, a Drive Priority Pass ID, tier_code, pass display name, email, occupied_by, other docks, raw tool …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Loading-Dock Assignment Pass PDF
Use this skill only after the agent has presented the completed loading-dock recommendation and the driver has explicitly asked for a PDF copy. The skill renders that completed assignment. It does not inspect other docks, classify weather, calculate queues, apply Drive Priority Pass priority, or select, reserve, confirm, or guarantee a dock.
Always run the bundled dock_assignment_pass.py script. Never hand-draw the PDF or
replace the script with generated rendering code.
Inputs
Pass the shipment reference and every nonempty driver-facing loading-plan attribute exactly once:
--shipment-referencefor the PDF header and Code 128 barcodecustomer_message.planas--plancustomer_message.weatheras--weathercustomer_message.assignmentas--assignmentcustomer_message.whyas--whycustomer_message.queueas--queue- optional nonempty
customer_message.etaas--eta - optional nonempty
customer_message.priority_passas--priority-pass --out wandelay_dock_assignment_pass.pdf
Use the accepted driver-facing content retained for the active loading plan. Preserve every verified fact and causal relationship. When required to keep the PDF on one page, summarize only the wording; do not remove or change verified facts, causal relationships, the assignment, queue, ETA, or Priority Pass outcome. Do not supplement, reinterpret, or recalculate any section. The PDF renders the nonempty sections in this order: Plan, Weather, Assignment, Why, Queue, ETA, Priority Pass.
The PDF contains the shipment reference as a scannable Code 128 barcode and uses a compact one-page layout with the existing bold title, labels, and section-heading treatment.
Never pass or display ready_for_pickup, a Drive Priority Pass ID,
tier_code, pass display name, email, occupied_by, other docks, raw tool
output, canonical state, decision-evidence JSON, cargo, or invented weather.
Example
python3 dock_assignment_pass.py \
--shipment-reference ORD-10502 \
--plan "Your loading plan for WanDelay Miami Distribution Center is ready for shipment ORD-10502." \
--weather "Rain and strong winds are expected around arrival." \
--assignment "Proceed to Dock 2." \
--why "Dock 2 provides the best available weather protection and queue." \
--queue "There are two trucks ahead, with an expected wait of one minute." \
--eta "You expect to arrive in 20 minutes, leaving a 19-minute buffer." \
--priority-pass "No queue reduction was applied." \
--out wandelay_dock_assignment_pass.pdfThe script prints:
WROTE wandelay_dock_assignment_pass.pdfReturn only the generated PDF file to the driver. Do not add a separate recommendation paragraph on a successful flow.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

