Agent skill
data-transformation
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
Install this agent skill to your Project
npx add-skill https://github.com/Jamie-BitFlight/claude_skills/tree/main/plugins/dasel/skills/data-transformation
SKILL.md
Data Transformation with Dasel v3
<when_to_use>
Activate this skill when:
- Modifying values in config files (YAML, TOML, JSON, XML, HCL, INI)
- Converting between data formats (JSON to YAML, TOML to JSON, etc.)
- Batch-updating array elements (prices, versions, flags)
- Appending, removing, or reshaping data structures
- Merging objects or constructing new structures from existing data
</when_to_use>
Safety Rules
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
Core Modification Syntax
In dasel v3, put and delete subcommands do not exist. All modifications use assignment expressions with --root to output the full document.
Set a Value
# 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"'
Set Nested Values
dasel -f config.yaml --root 'database.connection.host = "db.example.com"'
dasel -f config.yaml --root 'database.connection.port = 5432'
In-Place Modification (Safe Pattern)
# 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
Format Conversion
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
Array Operations
Append to Array
# 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}]'
Batch Update with each
# 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)'
Filter Then Transform
# Get only active users, then extract names
dasel -f data.json 'users.filter(active == true).map(name)'
Object Operations
Merge via Spread
# 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 }'
Field Deletion via Reconstruction
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 }'
Field Rename via Reconstruction
echo '{"old_name": "value"}' | dasel -i json --root '{ "new_name": old_name }'
Multi-Step Transformations
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'
Conditional Transformation
# Set value based on condition
dasel -f data.json --root 'if(count > 5) { status = "many" } else { status = "few" }'
Transformation Patterns
For detailed per-use-case transformation patterns (config updates, batch processing, format migration, data reshaping, error handling), see Transformation Patterns.
References
- Dasel v3 Documentation (fetched 2026-02-19)
- Dasel Spread Operator (fetched 2026-02-19)
- Dasel each() Function (fetched 2026-02-19)
- Dasel filter() Function (fetched 2026-02-19)
- Dasel CHANGELOG (fetched 2026-02-19)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ccc
This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the index', 'ccc', 'cocoindex-code'.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
delegate
Quick delegation template for sub-agent prompts. Use when assigning work to a sub-agent, before invoking the Agent tool, or when preparing prompts for specialized agents. Provides the WHERE-WHAT-WHY framework. For comprehensive delegation guidance, activate the agent-orchestration how-to-delegate skill.
swarm-spawning
Spawn agents and teammates in Claude Code swarms. Use when choosing between subagents vs teammates, selecting agent types (Explore, Plan, general-purpose, plugin agents), configuring spawn backends (in-process, tmux, iterm2), or setting environment variables for spawned agents.
knowledge-explorer
Manage the research/ knowledge base (KB) of tool and library research entries. Use when browsing KB topics, adding new research entries, updating existing entries with dated revisions, fetching GitHub repo metadata into a draft KB entry, or migrating old-format entries to skill-spec frontmatter. Triggers on tasks like "what do we have on X", "add this to the KB", "update the KB entry for Y", "fetch github info for owner/repo", or "migrate old entries".
design-anti-patterns
Enforce anti-AI UI design rules based on the Uncodixfy methodology. Use when generating HTML, CSS, React, Vue, Svelte, or any frontend UI code. Prevents "Codex UI" — the generic AI aesthetic of soft gradients, floating panels, oversized rounded corners, glassmorphism, hero sections in dashboards, and decorative copy. Applies constraints from Linear/Raycast/Stripe/GitHub design philosophy: functional, honest, human-designed interfaces. Triggers on: UI generation, dashboard building, frontend component creation, CSS styling, landing page design, or any task producing visual interface code.
Didn't find tool you were looking for?