Tachograph Triage & Root-Cause Prompts (UK)
v1.0.0Triages tachograph infringements, identifies common patterns, and outputs “what to check next” prompts and weekly review notes. USE WHEN doing weekly tacho/WTD reviews.
⭐ 1· 1.6k·0 current·0 all-time
by@kowl64
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (triaging tachograph infringements and producing weekly review notes) align with the SKILL.md and the bundled reference/playbook files. There are no unrelated credentials, binaries, or config paths requested.
Instruction Scope
Runtime instructions are narrowly scoped to normalising infringement records, pattern-scanning against the included checklist, producing per-driver prompts and a weekly pack, and stopping to ask when data is missing. The instructions do not direct the agent to read unrelated system files, access external endpoints, or exfiltrate data.
Install Mechanism
No install spec or code files — instruction-only. Nothing is downloaded or written to disk by an installer in the skill bundle.
Credentials
The skill declares no required environment variables, credentials, or config paths. The workflow expects user-supplied infringement data (CSV/PDF extracts) which is appropriate for the stated purpose.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent presence or attempt to modify other skills or system settings. Autonomous invocation is allowed by platform default but the skill itself does not request elevated persistence.
Assessment
This skill is an instruction-only template for triaging tachograph infringements and appears internally consistent. Before using it: (1) Validate outputs on sample, non-sensitive data to confirm the triage logic matches your policies; (2) Do not feed full PII-laden PDFs or personnel records into any third-party agent unless you trust the execution environment and have appropriate data-protection approvals; (3) Ensure any RAG/escalation thresholds referenced are configured to match your organisation’s policy (the skill flags where history is missing but relies on you to supply counts/outcomes); (4) If a future version adds code, external endpoints, or requests environment credentials, stop and reassess — that would materially change the risk profile.Like a lobster shell, security has layers — review code before you run it.
latestvk972gj7akdd78aw9hytchwpan57zc54x
License
MIT-0
Free to use, modify, and redistribute. No attribution required.