Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Builds DVSA/Traffic Commissioner “show me” audit readiness checklists and evidence indexes. USE WHEN preparing for audits or operator licence scrutiny.
Builds DVSA/Traffic Commissioner “show me” audit readiness checklists and evidence indexes. USE WHEN preparing for audits or operator licence scrutiny.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Produce “show me” readiness materials: today’s checklist, an evidence index, and a gaps register aligned to operator-licence sensitivity and audit expectations.
“Prep me for a DVSA visit and give me a checklist for today.” “Create a customer audit response pack for [CUSTOMER] and list gaps.” “Build an evidence index for operator licence compliance.” “What should we have ready to show an auditor today?” DO NOT USE WHEN… The request is generic compliance chat with no artefact needed. Pure operations/customer service requests (routes/pricing/performance) not compliance-led.
REQUIRED: Audit context (DVSA visit / TC inquiry readiness / customer audit) and date Scope: which depot/operating centre/fleet, and period (e.g., last 28/90 days) OPTIONAL: Your internal SOPs/policies (paste text) and retention rules Prior audit findings/actions EXAMPLES: “DVSA site visit today at Depot X; need show-me checklist and evidence index.”
dvsa-visit-today-checklist.md audit-evidence-index.md (Excel-ready table) gaps-register.md Success criteria: Practical, checkable items Clear “where to find it” references Highlights operator licence sensitivities (without legal claims beyond your policy text)
Confirm audit type and scope. IF missing → STOP AND ASK THE USER for audit type, depot/fleet, and time period. Generate today’s “show me” checklist using assets/dvsa-visit-today-checklist-template.md. Build an evidence index (what, where stored, owner, retention, last updated) using assets/audit-evidence-index-template.md. Identify likely gaps: Mark unknowns as “Gap – confirm source/owner”. Output gaps-register.md via assets/gaps-register-template.md. Operator licence sensitivity: Add a short section referencing references/operator-licence-sensitivity-placeholders.md and map to your internal policies. If the user wants edits to existing files → ASK FIRST.
Don’t invent retention periods or legal duties; ask for internal policy text if needed. If asked for “is this legal?”, stop and request the precise records and desired output artefact.
Input: “DVSA visit today” Output: checklist + evidence index + gaps register for rapid action
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.