Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Data Analysis
Tachograph Triage & Root-Cause Prompts (UK)
Triages tachograph infringements, identifies common patterns, and outputs “what to check next” prompts and weekly review notes. USE WHEN doing weekly tacho/WTD reviews.
skill openclawclawhub Free
Triages tachograph infringements, identifies common patterns, and outputs “what to check next” prompts and weekly review notes. USE WHEN doing weekly tacho/WTD reviews.
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, references/common-infringement-patterns.md, assets/weekly-review-pack-template.md, assets/what-to-check-next-playbook.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- 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.
New install
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.
Upgrade existing
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- KOwl64
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
PURPOSE
Run a weekly review workflow that turns infringement outputs into clear triage notes, root-cause prompts, and “what to check next” steps.
WHEN TO USE
“Do a weekly tacho and WTD compliance review for these drivers.” “Triage these infringements and tell me what to check next.” “Summarise this PDF infringement report into actions and driver follow-ups.” DO NOT USE WHEN… You only need a single driver-facing message (use the infringement coach skill). You want general rule explanations without records.
INPUTS
REQUIRED: Driver list + date range Infringement summaries (CSV/PDF extract or pasted lines) OPTIONAL: Any known operational context (routes, delays, multi-drop, ferry/train, staffing) Prior RAG history EXAMPLES: “Drivers A–F, last week’s infringement PDF attached; need weekly pack.”
OUTPUTS
weekly-tacho-wtd-review.md (manager-facing) triage-actions-by-driver.md Success criteria: Clear “next checks” per infringement type Flags where investigation/discipline thresholds may be approaching (per your policy)
WORKFLOW
Confirm period and driver list. IF missing → STOP AND ASK THE USER. Normalise infringements into a per-driver list (facts only). Pattern scan using references/common-infringement-patterns.md. For each driver, generate: Likely root-cause prompts (questions to ask, operational checks) “What to check next” steps using assets/what-to-check-next-playbook.md Produce weekly pack using assets/weekly-review-pack-template.md. If RAG escalation depends on missing history → STOP AND ASK THE USER for counts/outcomes.
OUTPUT FORMAT
- # triage-actions-by-driver.md
- Period:
- Sources:
- ## Driver [X]
- Infringements (facts):
- …
- What to check next:
- …
- Root-cause prompts:
- …
- Proposed follow-up:
- Coaching / monitoring / investigation trigger (per policy)
SAFETY & EDGE CASES
If records appear incomplete (missing days, download gaps), flag as a risk/gap rather than guessing why. Avoid blame language; keep triage neutral.
EXAMPLES
Input: “Weekly review for 12 drivers” Output: weekly pack + per-driver triage actions and check-next prompts
Category context
Data access, storage, extraction, analysis, reporting, and insight generation.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
4 Docs
- SKILL.md
- assets/weekly-review-pack-template.md
- assets/what-to-check-next-playbook.md
- references/common-infringement-patterns.md