plugins/dasel/skills/data-transformation/SKILL.md
Use when modifying, converting, or transforming structured data with dasel v3 — in-place mutations, format conversion, batch operations, array manipulation, object construction, and merge patterns across JSON, YAML, TOML, XML, CSV, HCL, INI
npx skillsauth add jamie-bitflight/claude_skills data-transformationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
<when_to_use>
Activate this skill when:
</when_to_use>
NEVER redirect output to the same input file. This truncates the file before dasel reads it, resulting in data loss:
# WRONG — destroys input
dasel -f config.yaml --root 'port = 9090' > config.yaml
# CORRECT — write to temp, then rename
dasel -f config.yaml --root 'port = 9090' > config_tmp.yaml && mv config_tmp.yaml config.yaml
Always verify before overwriting. Preview the transformation output first, then redirect:
# Preview
dasel -f config.yaml --root 'server.port = 9090'
# Apply
dasel -f config.yaml --root 'server.port = 9090' > config_tmp.yaml && mv config_tmp.yaml config.yaml
</constraints>
In dasel v3, put and delete subcommands do not exist. All modifications use assignment expressions with --root to output the full document.
# Output full document with one field changed
dasel -f config.yaml --root 'server.port = 9090'
# Numeric, boolean, and string assignments
echo '{"count": 1}' | dasel -i json --root 'count = 42'
echo '{"enabled": false}' | dasel -i json --root 'enabled = true'
echo '{"name": "old"}' | dasel -i json --root 'name = "new"'
dasel -f config.yaml --root 'database.connection.host = "db.example.com"'
dasel -f config.yaml --root 'database.connection.port = 5432'
# Single field update
dasel -f config.yaml --root 'server.port = 9090' > config_tmp.yaml && mv config_tmp.yaml config.yaml
# Multiple fields — chain with semicolons
dasel -f config.yaml --root 'server.port = 9090; server.host = "0.0.0.0"' > config_tmp.yaml && mv config_tmp.yaml config.yaml
Pipe through dasel with different input/output format flags:
# JSON to YAML
cat data.json | dasel -i json -o yaml > data.yaml
# YAML to TOML
cat config.yaml | dasel -i yaml -o toml > config.toml
# JSON to XML
cat data.json | dasel -i json -o xml > data.xml
# TOML to JSON
cat config.toml | dasel -i toml -o json > config.json
# CSV to JSON
cat data.csv | dasel -i csv -o json > data.json
# Add element to end of array
echo '[1,2,3]' | dasel -i json --root '[$this..., 4]'
# Output: [1, 2, 3, 4]
# Append object to array
dasel -f data.json --root 'items = [$root.items..., {"name": "new", "value": 42}]'
# Multiply all prices by 1.1 (10% increase)
dasel -f data.json --root 'items.each(price = price * 1.1)'
# Set a flag on all elements
dasel -f data.json --root 'users.each(active = true)'
# Increment all values
echo '[1,2,3]' | dasel -i json --root 'each($this = $this + 1)'
# Get only active users, then extract names
dasel -f data.json 'users.filter(active == true).map(name)'
# Add new key to existing object
dasel -f base.json --root '{ $root..., "newKey": "value" }'
# Merge two objects
dasel -f base.json --root '{ $root..., "extra": true, "version": 2 }'
Since v3 has no delete command, remove fields by constructing a new object with only the desired keys:
# Keep only "name" and "email", drop everything else
echo '{"name":"a","email":"b","password":"c"}' | dasel -i json --root '{ name, email }'
echo '{"old_name": "value"}' | dasel -i json --root '{ "new_name": old_name }'
Use variable assignment and semicolons for complex operations:
# Store intermediate result in variable, then transform
dasel -f data.json '$active = users.filter(active == true); $active.map(name)'
# Multiple variables
dasel -f data.json '$a = items.filter(price > 100); $b = $a.map(name); $b'
# Set value based on condition
dasel -f data.json --root 'if(count > 5) { status = "many" } else { status = "few" }'
For detailed per-use-case transformation patterns (config updates, batch processing, format migration, data reshaping, error handling), see Transformation Patterns.
development
When an application needs to store config, data, cache, or state files. When designing where user-specific files should live. When code writes to ~/.appname or hardcoded home paths. When implementing cross-platform file storage with platformdirs.
testing
Enforce mandatory pre-action verification checkpoints to prevent pattern-matching from overriding explicit reasoning. Use this skill when about to execute implementation actions (Bash, Write, Edit) to verify hypothesis-action alignment. Blocks execution when hypothesis unverified or action targets different system than hypothesis identified. Critical for preventing cognitive dissonance where correct diagnosis leads to wrong implementation.
tools
Reference guide for the Twelve-Factor App methodology — 15 principles (12 original + 3 modern extensions) for building portable, resilient, cloud-native applications. Use when evaluating application architecture, designing cloud-native services, reviewing codebases for methodology compliance, advising on configuration, scaling, observability, security, and deployment patterns. Incorporates the 2025 open-source community evolution and cloud-native reinterpretations of each factor.
tools
Converts user-facing documentation (how-to guides, tutorials, API references, examples) in any format — Markdown, PDF, DOCX, PPTX, XLSX, AsciiDoc, RST, HTML, Jupyter notebooks, man pages, TOML/YAML/JSON configs, and plain text — into Claude Code skill directories with SKILL.md plus thematically grouped references/*.md files. Use when given a docs directory or mixed-format documentation to transform into an AI skill. Uses MCP file-reader server for binary formats.