{
  "schemaVersion": "1.0",
  "item": {
    "slug": "drivers-hours-wtd-infringement-coach-uk",
    "name": "Drivers’ Hours & WTD Infringement Coach (UK)",
    "source": "tencent",
    "type": "skill",
    "category": "效率提升",
    "sourceUrl": "https://clawhub.ai/KOwl64/drivers-hours-wtd-infringement-coach-uk",
    "canonicalUrl": "https://clawhub.ai/KOwl64/drivers-hours-wtd-infringement-coach-uk",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/drivers-hours-wtd-infringement-coach-uk",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=drivers-hours-wtd-infringement-coach-uk",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md",
      "references/rag-escalation-rule.md",
      "assets/corrective-action-plan-template.md",
      "assets/driver-note-template.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "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."
        },
        {
          "label": "Upgrade existing",
          "body": "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."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-23T16:43:11.935Z",
      "expiresAt": "2026-04-30T16:43:11.935Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
        "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/drivers-hours-wtd-infringement-coach-uk"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/drivers-hours-wtd-infringement-coach-uk",
    "agentPageUrl": "https://openagent3.xyz/skills/drivers-hours-wtd-infringement-coach-uk/agent",
    "manifestUrl": "https://openagent3.xyz/skills/drivers-hours-wtd-infringement-coach-uk/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/drivers-hours-wtd-infringement-coach-uk/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "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."
      },
      {
        "label": "Upgrade existing",
        "body": "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."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "PURPOSE",
        "body": "Turn tacho/WTD infringement evidence into a friendly, professional 1-page driver note plus corrective actions and a review date, applying the company RAG escalation rule."
      },
      {
        "title": "WHEN TO USE",
        "body": "“Explain this tacho infringement to the driver and draft the message.”\n“Check this shift pattern for EU Drivers’ Hours and WTD risk.”\n“Do a weekly tacho and WTD compliance review for these drivers.” (driver-facing outputs needed)\n“Draft a coaching note for repeated breaks/rest issues.”\n“Summarise these infringements into actions and review dates.”\n\nDO NOT USE WHEN…\n\nGeneric questions like “What are the drivers’ hours rules?” with no driver context or artefact needed.\nGeneric HR/disciplinary process requests not tied to a specific compliance case.\nFuel-saving/defensive driving tips unrelated to compliance deliverables."
      },
      {
        "title": "INPUTS",
        "body": "REQUIRED:\n\nDriver identifier (name/ID) and role (e.g., HGV/PCV), and period covered (start/end dates)\nInfringement list (from .ddd/CSV/PDF summary) including dates/times and type\nWorking time context (duty/shift length, POA if recorded, breaks) if WTD-relevant\n\n\nOPTIONAL:\n\nPrior RAG history (count of ambers/reds in last X weeks/months per your policy)\nAny driver explanation already given\nRelevant internal SOP excerpt (paste text) for local rules\n\n\nEXAMPLES:\n\n“Driver A, week 2026-01-05 to 2026-01-11: 2x insufficient break, 1x daily rest short by 45 mins…”"
      },
      {
        "title": "OUTPUTS",
        "body": "driver-infringement-note.md (max ~1 page): explanation + expectations + support\ncorrective-action-plan.md: actions, owner, due dates, review date\nSuccess criteria:\n\nTone: friendly & professional (UK spelling)\nNo assumptions: facts are attributed to provided records\nIncludes a clear review date and next steps"
      },
      {
        "title": "WORKFLOW",
        "body": "Validate inputs\n\nConfirm: driver ID, date range, infringement types, and source (PDF/CSV notes).\nIF any are missing → STOP AND ASK THE USER for the missing items.\n\n\nSummarise facts only\n\nList infringements in plain English (what happened + when), without blame.\nIF records conflict (e.g., two sources disagree) → STOP AND ASK THE USER which source is authoritative.\n\n\nClassify severity for RAG\n\nApply the company rule in references/rag-escalation-rule.md.\nIF RAG status depends on missing prior history → STOP AND ASK THE USER for counts/previous outcomes.\n\n\nDraft the driver-facing note (max 1 page)\n\nUse assets/driver-note-template.md.\nInclude: what the rule expects, what the record shows, why it matters, and what to do next time.\n\n\nPropose corrective actions\n\nUse assets/corrective-action-plan-template.md.\nActions must be specific, practical, and measurable (e.g., break planning, reminder prompts, route/shift adjustments).\n\n\nSchedule review\n\nChoose a review date proportional to risk:\n\nGreen/Amber: typically next weekly review window\nRed: sooner review + manager check-in (and potential investigation trigger per your policy)\n\n\n\n\nOutput pack\n\nProduce the two .md artefacts with consistent filenames.\nIF the user asks to edit existing files → ASK FIRST before making edits."
      },
      {
        "title": "OUTPUT FORMAT",
        "body": "# driver-infringement-note.md\nDriver:\nPeriod covered:\nSource records:\n\n## What we saw in the record (facts)\n- [date/time] — [plain English infringement]\n- …\n\n## What the rules require (plain English)\n- …\n\n## What to do next time (practical steps)\n- …\n- …\n\n## Support we can offer\n- …\n\n## Status and next review\nRAG status:\nNext review date:\nManager/Compliance follow-up:"
      },
      {
        "title": "DEPENDENCIES",
        "body": "None required beyond the provided extracts/summaries.\nIf the user provides files (.ddd/CSV/PDF), rely on the user’s summary unless your environment includes a trusted parser."
      },
      {
        "title": "SAFETY & EDGE CASES",
        "body": "Never accuse or assume intent; stick to evidence.\nIf there is any possibility of an employment action (discipline), recommend using the investigation skill pack and keep this note factual/coaching-focused.\nDon’t invent legal thresholds; only explain what’s in the provided evidence + internal policy text."
      },
      {
        "title": "EXAMPLES",
        "body": "Input: “Explain insufficient break x2 and rest shortage x1 for Driver A”\n\nOutput: driver-infringement-note.md + corrective-action-plan.md with review date next week\n\n\nInput: “Repeated break issues; prior 3 ambers”\n\nOutput: Note + actions; status indicates escalation path per RAG rule; recommends investigation workflow if needed"
      }
    ],
    "body": "Drivers’ Hours & WTD Infringement Coach (UK)\nPURPOSE\n\nTurn tacho/WTD infringement evidence into a friendly, professional 1-page driver note plus corrective actions and a review date, applying the company RAG escalation rule.\n\nWHEN TO USE\n“Explain this tacho infringement to the driver and draft the message.”\n“Check this shift pattern for EU Drivers’ Hours and WTD risk.”\n“Do a weekly tacho and WTD compliance review for these drivers.” (driver-facing outputs needed)\n“Draft a coaching note for repeated breaks/rest issues.”\n“Summarise these infringements into actions and review dates.”\n\nDO NOT USE WHEN…\n\nGeneric questions like “What are the drivers’ hours rules?” with no driver context or artefact needed.\nGeneric HR/disciplinary process requests not tied to a specific compliance case.\nFuel-saving/defensive driving tips unrelated to compliance deliverables.\nINPUTS\nREQUIRED:\nDriver identifier (name/ID) and role (e.g., HGV/PCV), and period covered (start/end dates)\nInfringement list (from .ddd/CSV/PDF summary) including dates/times and type\nWorking time context (duty/shift length, POA if recorded, breaks) if WTD-relevant\nOPTIONAL:\nPrior RAG history (count of ambers/reds in last X weeks/months per your policy)\nAny driver explanation already given\nRelevant internal SOP excerpt (paste text) for local rules\nEXAMPLES:\n“Driver A, week 2026-01-05 to 2026-01-11: 2x insufficient break, 1x daily rest short by 45 mins…”\nOUTPUTS\ndriver-infringement-note.md (max ~1 page): explanation + expectations + support\ncorrective-action-plan.md: actions, owner, due dates, review date\nSuccess criteria:\nTone: friendly & professional (UK spelling)\nNo assumptions: facts are attributed to provided records\nIncludes a clear review date and next steps\nWORKFLOW\nValidate inputs\nConfirm: driver ID, date range, infringement types, and source (PDF/CSV notes).\nIF any are missing → STOP AND ASK THE USER for the missing items.\nSummarise facts only\nList infringements in plain English (what happened + when), without blame.\nIF records conflict (e.g., two sources disagree) → STOP AND ASK THE USER which source is authoritative.\nClassify severity for RAG\nApply the company rule in references/rag-escalation-rule.md.\nIF RAG status depends on missing prior history → STOP AND ASK THE USER for counts/previous outcomes.\nDraft the driver-facing note (max 1 page)\nUse assets/driver-note-template.md.\nInclude: what the rule expects, what the record shows, why it matters, and what to do next time.\nPropose corrective actions\nUse assets/corrective-action-plan-template.md.\nActions must be specific, practical, and measurable (e.g., break planning, reminder prompts, route/shift adjustments).\nSchedule review\nChoose a review date proportional to risk:\nGreen/Amber: typically next weekly review window\nRed: sooner review + manager check-in (and potential investigation trigger per your policy)\nOutput pack\nProduce the two .md artefacts with consistent filenames.\nIF the user asks to edit existing files → ASK FIRST before making edits.\nOUTPUT FORMAT\n# driver-infringement-note.md\nDriver:\nPeriod covered:\nSource records:\n\n## What we saw in the record (facts)\n- [date/time] — [plain English infringement]\n- …\n\n## What the rules require (plain English)\n- …\n\n## What to do next time (practical steps)\n- …\n- …\n\n## Support we can offer\n- …\n\n## Status and next review\nRAG status:\nNext review date:\nManager/Compliance follow-up:\n\nDEPENDENCIES\nNone required beyond the provided extracts/summaries.\nIf the user provides files (.ddd/CSV/PDF), rely on the user’s summary unless your environment includes a trusted parser.\nSAFETY & EDGE CASES\nNever accuse or assume intent; stick to evidence.\nIf there is any possibility of an employment action (discipline), recommend using the investigation skill pack and keep this note factual/coaching-focused.\nDon’t invent legal thresholds; only explain what’s in the provided evidence + internal policy text.\nEXAMPLES\nInput: “Explain insufficient break x2 and rest shortage x1 for Driver A”\nOutput: driver-infringement-note.md + corrective-action-plan.md with review date next week\nInput: “Repeated break issues; prior 3 ambers”\nOutput: Note + actions; status indicates escalation path per RAG rule; recommends investigation workflow if needed"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/KOwl64/drivers-hours-wtd-infringement-coach-uk",
    "publisherUrl": "https://clawhub.ai/KOwl64/drivers-hours-wtd-infringement-coach-uk",
    "owner": "KOwl64",
    "version": "1.0.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/drivers-hours-wtd-infringement-coach-uk",
    "downloadUrl": "https://openagent3.xyz/downloads/drivers-hours-wtd-infringement-coach-uk",
    "agentUrl": "https://openagent3.xyz/skills/drivers-hours-wtd-infringement-coach-uk/agent",
    "manifestUrl": "https://openagent3.xyz/skills/drivers-hours-wtd-infringement-coach-uk/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/drivers-hours-wtd-infringement-coach-uk/agent.md"
  }
}