Security audit
Security checks for vulnerabilities and agentic risk
This is a straightforward DuckDB helper skill; it documents normal DuckDB file and database operations without hidden code or deceptive behavior.
Install only if you want Claude to help with DuckDB CLI work. Review commands before running them, especially ones that write output files, modify .duckdb databases, read local datasets, change ~/.duckdbrc, or open an external editor.
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
Copy SKILL.md to your Claude Code skills directory:
mkdir -p ~/.claude/skills/duckdb
cp SKILL.md ~/.claude/skills/duckdb/
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
Copy SKILL.md to your Claude Code skills directory:
mkdir -p ~/.claude/skills/duckdb
cp SKILL.md ~/.claude/skills/duckdb/
The manifest description says the skill triggers on generic terms including "sql", "query", and "data analysis". These phrases overlap with common user requests across many contexts and are not narrowly scoped to DuckDB CLI usage, increasing the chance of accidental activation.
The skill explicitly documents commands that write files and modify databases, but it does not warn users that these operations are state-changing or potentially destructive. In an agent context, this increases the chance that a model may suggest or execute a write operation on user data without clear confirmation, leading to accidental overwrite, corruption, or unintended persistence.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
duckdb -csv -c "SELECT * FROM 'data.parquet'" | head -20
duckdb -c "COPY (SELECT * FROM 'data.csv') TO '/dev/stdout' (FORMAT CSV)"
This markdown file describes example prompts such as "Convert this CSV to Parquet" and "Show me statistics for sales.csv" without clarifying whether they are merely examples after explicit /duckdb activation or also implicit triggers. Because these are common data-assistance requests, the README lacks negative examples or scope boundaries that would prevent unintended invocation in broader contexts.
The skill name duckdb-en suggests an English-only variant, but the document does not explain the locale constraint or offer language choice. If this naming reflects enforced English responses or usage, it may violate language/locale policy expectations without explicit opt-in or justification.
The markdown instructs users to open queries in an external editor and explains that the editor is chosen from environment variables. This can cause query contents to be opened in external programs, but the skill description provides no warning about that behavior or the need to trust the configured editor.
No suspicious patterns detected.