← Back to Skills Marketplace
98
Downloads
1
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install driver-card-tachograph
Description
Parses EU Digital Tachograph driver card (.ddd) files, converts to JSON, imports data into SQLite, and exports driving info and violations to CSV.
README (SKILL.md)
driver-card-tachograph
Parses EU Digital Tachograph driver card files (.ddd) and imports data into a SQLite database.
Description
Processes EU Digital Tachograph files (.ddd):
- .ddd files: Binary driver card dumps
- Parser:
dddparser(EU certified) - Database: SQLite with 13 tables
Certificates
See references/certificates.md for details on EU JRC public keys and signature verification.
Commands
| Command | Description |
|---|---|
./scripts/process.sh |
Full workflow (recommended) |
./bin/dddparser -card -format -input \x3Cfile.ddd> -output \x3Cfile.json> |
.ddd → JSON |
./scripts/import.py \x3Cfile.json> |
JSON → SQLite |
./scripts/export.py |
SQLite → CSV |
Directory Structure
driver-card-tachograph/
├── SKILL.md
├── bin/dddparser # Parser
├── scripts/
│ ├── import.py
│ ├── export.py
│ └── process.sh
├── references/
│ ├── build.md # Build guide
│ └── certificates.md # Certificate details
└── data/ # Runtime
Requirements
- Go 1.21+ – to build the parser
- Python 3 – standard library (sqlite3, json, csv)
Build dddparser
See references/build.md for the build guide.
.ddd Files
- Location:
data/inbox/ - Extension:
.ddd(case-insensitive) - Min size: 1KB
Workflow
./scripts/process.sh
- Take .ddd from
inbox/ - Parse to JSON (
parsed/) - Import to SQLite (
json/→ DB) - Archive to
archive/
Usage Guidance
This skill appears to do exactly what it says: parse .ddd files, import into SQLite, and export CSVs. Before installing and running it:
- Verify the dddparser binary source: the build guide clones https://github.com/traconiq/tachoparser. Review that repo and the built binary for trustworthiness before copying it into the skill's bin/ directory.
- The skill operates on local files and the local SQLite DB only (no network exfiltration is present in the scripts), but double-check any build-time network activity (git clone) and only use trusted releases.
- Be aware of retention behavior: archives are kept for 10 years and summaries for 1 year; cleanup.py will delete files accordingly. Ensure this retention matches your data‑handling and privacy policies.
- process.sh can send alert emails if MAIL_TO is set and mail is available; this environment variable is optional but not listed in metadata — if you do not want emails, leave MAIL_TO unset or remove that section.
- Confirm runtime environment: Python 3 is required and the dddparser binary must be present (the package does not include the compiled binary). Run the scripts in a controlled workspace (least privilege) and inspect logs/summaries after initial runs.
If you want, provide the dddparser repository link or the built binary hash and I can help inspect the upstream code or compare checksums.
Capability Analysis
Type: OpenClaw Skill
Name: driver-card-tachograph
Version: 1.0.0
The skill bundle contains several critical security vulnerabilities that could lead to arbitrary code execution. Specifically, `scripts/process.sh` is vulnerable to Python/shell injection because it interpolates the `$JSON_OUTPUT` variable (derived from potentially untrusted filenames) directly into a `python3 -c` command string. Additionally, `scripts/export.py` and `scripts/health_check.py` utilize dangerous string formatting for SQL queries rather than parameterized inputs. While the bundle appears to serve its stated purpose of tachograph data parsing, these flaws represent a significant attack surface. The build documentation also points to an external third-party repository (github.com/traconiq/tachoparser.git) for the core binary dependency.
Capability Assessment
Purpose & Capability
The skill claims to parse .ddd driver card dumps, import to SQLite and export CSV — all included scripts (process.sh, import.py, export.py, health_check.py, cleanup.py) implement those behaviors. The SKILL.md and references explain building a third‑party dddparser from GitHub, which matches the declared need for a parser binary. No unrelated binaries or credentials are requested.
Instruction Scope
Runtime instructions operate on local directories (data/inbox, data/parsed, data/json, data/archive, summaries) and the local SQLite DB. The scripts do file I/O, parsing, DB writes, CSV export, health checks and archive cleanup — all within the stated scope. They do not contact remote endpoints at runtime or read unrelated system files. One minor point: process.sh optionally uses the MAIL_TO environment variable to send email alerts (if configured), which is reasonable but not declared in requires.env.
Install Mechanism
There is no automated install spec; the build guide asks you to git clone and build a dddparser from https://github.com/traconiq/tachoparser (a GitHub repo). Cloning and building third‑party code is expected for this parser, but you should review and verify that repository and the produced binary before running it in your environment. The build host (GitHub) is a standard release source; no obscure download URLs are used in the provided instructions.
Credentials
The skill requests no environment variables or credentials in registry metadata. The runtime scripts do, however, optionally reference MAIL_TO for alert emails and rely on system tools (mail) if you configure that — MAIL_TO is not declared as a required env var but is optional. No secrets (API keys, AWS creds, tokens) are requested or used. Database and file paths are local to the project directory.
Persistence & Privilege
The skill is not always-enabled and does not require special platform privileges. It creates and modifies files inside its project workspace (data/, summaries/, logs/), archives original .ddd files, and deletes aged files per configured retention. These are normal actions for this kind of tool; the 10-year archive deletion and 1-year summary retention are long but documented and consistent with stated legal retention requirements.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install driver-card-tachograph - After installation, invoke the skill by name or use
/driver-card-tachograph - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of driver-card-tachograph.
- Parses EU Digital Tachograph driver card files (.ddd) to JSON.
- Imports parsed tachograph data into a structured SQLite database.
- Supports exporting driving activity data to CSV.
- Includes analyzer functions for driver hours, violations, and vehicle usage.
- Provides a script for the full workflow from file ingest to database import and archiving.
- Documentation covers requirements, workflows, commands, and certificate handling.
Metadata
Frequently Asked Questions
What is Driver Card Tachograph?
Parses EU Digital Tachograph driver card (.ddd) files, converts to JSON, imports data into SQLite, and exports driving info and violations to CSV. It is an AI Agent Skill for Claude Code / OpenClaw, with 98 downloads so far.
How do I install Driver Card Tachograph?
Run "/install driver-card-tachograph" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Driver Card Tachograph free?
Yes, Driver Card Tachograph is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Driver Card Tachograph support?
Driver Card Tachograph is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Driver Card Tachograph?
It is built and maintained by Sanweb (@sanwebgit); the current version is v1.0.0.
More Skills