ClawHub

Csv Parser Local

v1.0.0

Parse and generate RFC 4180 compliant CSV that works across tools.

⭐ 0· 80·1 current·1 all-time
by@panchenbo·fork of @ivangdavila/csv (1.0.0)
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
ℹ
Purpose & Capability
Name/description (RFC 4180 CSV parsing/generation) matches the SKILL.md content: guidance on quoting, delimiters, encoding, Excel quirks, etc. The skill requests no binaries, env vars, or installs — appropriate for a documentation/instruction-only skill. Minor inconsistency: the _meta.json ownerId ('kn73vp5r...') differs from the registry Owner ID ('kn7e537h...') listed in the package metadata; this is likely benign (typo or packaging mismatch) but worth verifying the source.
✓
Instruction Scope
SKILL.md contains only parsing/generation guidance and best-practices for CSV handling. It does not instruct the agent to read arbitrary system files, access credentials, or transmit data externally. The instructions are focused and do not grant broad discretionary actions.
✓
Install Mechanism
No install specification and no code files — instruction-only skill. Lowest-risk install profile because nothing is written to disk or fetched during install.
✓
Credentials
Requires no environment variables, credentials, or config paths. Requested access is proportional (none) to the described functionality.
✓
Persistence & Privilege
always:false and default autonomous invocation settings are used. The skill does not request permanent presence or elevated privileges; nothing in the package attempts to modify other skills or system-wide settings.
Assessment
This skill is instruction-only and appears internally consistent for CSV parsing/generation: safe to inspect and use. Before installing or trusting it: 1) verify the publisher/owner (the _meta.json ownerId differs from the registry Owner ID), 2) if you plan to run any code that uses these instructions, review that code (the skill itself contains no code), 3) avoid sending sensitive secrets or credentials as CSV content, and 4) test behavior on non-production/sample files first. If the publisher is unfamiliar, treat it as documentation rather than code and proceed cautiously.

Like a lobster shell, security has layers — review code before you run it.

latestvk9740tdzg2kphq1ccmj4bxfk5983jm1s

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

📊 Clawdis
OSLinux · macOS · Windows

Comments