CommunityProgramación y desarrollogithub.com

Referencia de dasel v3

Úsalo para consultar, modificar o convertir JSON, YAML, TOML, XML, CSV, HCL o INI con dasel v3. Referencia completa de selectores, funciones, condicionales, variables, operador spread, conversión de tipos y patrones específicos de formato.

¿Qué es Referencia de dasel v3?

Este skill proporciona una referencia completa de la sintaxis de dasel v3, un binario CLI único para consultar, modificar y convertir datos estructurados en múltiples formatos (JSON, YAML, TOML, XML, CSV, HCL, INI). Es útil para desarrolladores y usuarios de agentes de IA que necesitan reemplazar herramientas como `jq`, `yq` o `xmllint` con una sintaxis unificada. El skill documenta el uso básico con pipes, el manejo explícito de formatos (sin detección automática), los selectores (notación de puntos, índices de array, descenso recursivo, construcción de objetos, spread), funciones incorporadas (filter, map, search, sortBy, conversiones de tipo, codificación base64), la sintaxis de modificación inline con `--root`, variables especiales como `$root` y `$this`, condicionales, y los cambios incompatibles con v2. Incluye referencias a las fuentes oficiales y un informe de verificación de hechos. Compatible con Claude Code, Cursor y Codex.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Jamie-BitFlight/claude_skills/tree/main/plugins/dasel/skills/dasel-reference

Installed? Explore more Programación y desarrollo skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

Referencia de Sintaxis de dasel v3

Binario CLI único para consultar, modificar y convertir datos estructurados. Reemplaza jq + yq + xmllint con una sintaxis de consulta unificada en todos los formatos.

Versión estable al momento de la escritura (fecha: 2026-02-23): v3.2.3

Formatos Soportados

json, yaml, toml, xml, csv, hcl, ini

Uso Básico

# Consultar desde stdin (formato requerido)
echo '{"foo": "bar"}' | dasel -i json 'foo'

# Consultar desde archivo vía stdin
cat config.yaml | dasel -i yaml 'database.host'

# Modificar y mostrar documento completo
echo '{"port": 3000}' | dasel -i json --root 'server.port = 8080'

# Convertir formatos
cat data.json | dasel -i json -o yaml

Manejo de Formatos

dasel v3 NO detecta automáticamente el formato desde la extensión del archivo. No existe la bandera -f/--file. La entrada siempre se lee desde stdin. El formato debe especificarse explícitamente con -i y/o -o. Si solo se proporciona uno, el otro toma el mismo valor. Si no se proporciona ninguno, ambos toman por defecto json (configurable mediante ~/dasel.yaml con la clave default_format).

Fuente: internal/cli/query.go:10-11, internal/cli/run.go:37-43, internal/cli/config.go:19-21

Banderas Principales

-i, --in <formato>         Analizador de entrada (json, yaml, toml, xml, csv, hcl, ini)
-o, --out <formato>        Analizador de salida (toma por defecto el formato de entrada)
--root                     Mostrar documento completo después de la modificación
--var <nombre>=<valor>     Pasar variables a la consulta (repetible)
--compact                  Salida compacta (sin formato bonito)
--rw-flag <nombre>=<valor> Bandera de lectura/escritura (ej. --rw-flag csv-delimiter=;)
--read-flag <nombre>=<val>  Bandera de lectura (ej. --read-flag xml-mode=structured)
--write-flag <nombre>=<val> Bandera de escritura (ej. --write-flag csv-delimiter=;)
-c, --config <ruta>        Ruta del archivo de configuración (por defecto: ~/dasel.yaml)

Referencia Rápida de Selectores

SelectorSintaxisEjemplo
Notación de puntosfoo.bar.baz`cat f.json
Índice de array[0], [2]`cat f.json
Rebanada de array[0:3]`cat f.json
Descenso recursivo.., ..name`cat f.json
Todos los valores recursivos..*`cat f.json
Construcción de objetos{ clave1, clave2 }`cat f.json
Spreadobj...`cat f.json

Referencia Rápida de Funciones

19 funciones integradas en DefaultFuncCollection (fuente: execution/func.go:12-33) más la expresión compleja sortBy.

FunciónPropósitoEjemplo
filter(pred)Filtrar arraysusers.filter(active == true)
map(expr)Transformar arraysusers.map(name)
each(expr)Modificar cada elementoeach($this = $this * 2)
search(pred)Búsqueda recursivasearch(has("id"))
sortBy(expr)Ordenar arraysortBy($this, desc)
has(clave)Verificar si existe clavehas("name")
get(clave)Obtener valor en clave/índiceget("name")
contains(val)Verificar si la rebanada contiene el valorcontains(42)
len(expr)Longitudlen($this)
join(sep)Unir a cadenajoin(",")
sum(expr)Sumar array numéricosum($this)
add(args...)Sumar númerosadd(1, 2, 3)
max(args...)Valor máximomax(1, 5, 3)
min(args...)Valor mínimomin(1, 5, 3)
merge(args...)Fusionar mapasmerge(defaults, overrides)
keys(expr)Obtener claves del mapakeys($this)
reverse(expr)Invertir arrayreverse($this)
typeOf(expr)Obtener cadena de tipotypeOf($this)
toString(expr)Convertir a cadenatoString($this)
toInt(expr)Convertir a enterotoInt($this)
toFloat(expr)Convertir a flotantetoFloat($this)
base64e(cad)Codificar en Base64base64e("hola")
base64d(cad)Decodificar Base64base64d("aGVsbG8=")
parse(fmt, datos)Analizar datos en tiempo de ejecuciónparse("json", rawStr)
readFile(ruta)Leer contenido de archivoreadFile("config.json")
ignore()Excluir de la ramaignore()

Sintaxis de Modificación

v3 eliminó los subcomandos put y delete. Usa asignación con --root:

# Establecer un valor
echo '{"count": 1}' | dasel -i json --root 'count = 42'

# Asignación booleana
echo '{"enabled": false}' | dasel -i json --root 'enabled = true'

# Añadir a array
echo '[1,2,3]' | dasel -i json --root '[$this..., 4]'

# Eliminar clave (reconstruir sin ella)
echo '{"keep": "yes", "drop": "no"}' | dasel -i json --root '{ keep }'

Conversión de Formatos

# JSON a YAML
cat data.json | dasel -i json -o yaml

# YAML a TOML
cat config.yaml | dasel -i yaml -o toml

# TOML a JSON
cat config.toml | dasel -i toml -o json

Variables Especiales

  • $root -- referencia al documento raíz
  • $this -- referencia al nodo actual (dentro de each, map, filter, search)

Asignación de Variables

# Múltiples sentencias con punto y coma
cat data.json | dasel -i json '$active = users.filter(active == true); $active.map(name)'

Condicionales

echo '{"count": 7}' | dasel -i json 'if(count > 5) { "many" } else { "few" }'

Cambios Rupturistas en v3 respecto a v2

  • Subcomandos put y delete eliminados; usar asignación inline con --root
  • Bandera -f/--file eliminada; la entrada siempre viene de stdin mediante pipe
  • Sintaxis de consultas/selectores completamente renovada; la sintaxis v2 NO es compatible con v3
  • El framework CLI cambió de Cobra a Kong
  • La ruta del módulo Go cambió a github.com/tomwright/dasel/v3

Referencias Detalladas

Fuentes

  1. README de dasel: https://raw.githubusercontent.com/TomWright/dasel/master/README.md (obtenido 2026-02-19)
  2. Documentación de dasel: https://daseldocs.tomwright.me (obtenido 2026-02-19)
  3. Sintaxis de consultas: https://daseldocs.tomwright.me/syntax/query-syntax.md (obtenido 2026-02-19)
  4. Índice de funciones: https://daseldocs.tomwright.me/functions (obtenido 2026-02-19)
  5. CHANGELOG: https://raw.githubusercontent.com/TomWright/dasel/master/CHANGELOG.md (obtenido 2026-02-19)
  6. Lanzamientos: https://github.com/TomWright/dasel/releases (obtenido 2026-02-19)
  7. Análisis del código fuente: execution/func.go, internal/cli/query.go, internal/cli/run.go, internal/cli/config.go, execution/execute_binary.go, execution/execute_unary.go (analizado 2026-02-19)
  8. Verificación de hechos: FACT_CHECK_REPORT.md (2026-02-23)

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

Jamie-BitFlight/agentskill-kaizen-meta-docs

Agentskill kaizen plugin documentation index. Load when needing to read about cross-platform notes, improvement plans, or DuckDB integration.

Jamie-BitFlight/bash-51-features

Bash 5.1 release features and improvements with practical examples. Use when working with Bash 5.1 features, epoch time variables, redirection enhancements, or when user asks about Bash 5.1 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-52-features

Bash 5.2 release features and improvements with practical examples. Use when working with Bash 5.2 features, variable handling enhancements, readline improvements, or when user asks about Bash 5.2 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-53-features

Bash 5.3 release features and improvements with practical examples. Use when working with Bash 5.3 features, new command substitution, GLOBSORT, loadable builtins, or when user asks about Bash 5.3 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-development

This skill should be used when the user asks to "write a bash script", "create a shell script", "implement bash function", "parse arguments in bash", "handle errors in bash", or mentions bash development, shell scripting, script templates, or modern bash patterns.

Jamie-BitFlight/bash-lint

This skill should be used when the user asks to "lint bash script", "run shellcheck", "format shell script", "use shfmt", "fix shellcheck errors", or mentions shell script linting, formatting, code quality, or pre-commit hooks for bash.

Jamie-BitFlight/bash-logging

This skill should be used when the user asks to "add logging to bash script", "colorize output", "implement log levels", "CI/CD sections", "terminal colors in bash", or mentions logging functions, emoji output, collapsible CI sections, or shlocksmith.

Jamie-BitFlight/bash-portability

This skill should be used when the user asks about "POSIX compatibility", "portable shell scripts", "cross-shell compatibility", "bashisms", "shebang selection", or mentions writing scripts that work on different shells (bash, sh, dash, zsh) or different systems.

Jamie-BitFlight/bash-testing

This skill should be used when the user asks to "test bash script", "write shell tests", "use shunit2", "use shellspec", "create test suite for bash", or mentions unit testing, test frameworks, mocking, or test-driven development for shell scripts.

Jamie-BitFlight/brainstorming-skill

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or when users request help with ideation, marketing, and strategic planning. Explores user intent, requirements, and design before implementation using research-validated prompt patterns.

Jamie-BitFlight/clang-format

Configure clang-format code formatting. Use when: user mentions clang-format or .clang-format, analyzing code style/patterns, creating/modifying formatting config, troubleshooting formatting, brace styles/indentation/spacing/alignment/pointer alignment, or codifying conventions.

Jamie-BitFlight/commitlint

When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.

Jamie-BitFlight/conventional-commits

When writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating breaking changes. When generating changelogs from commit history.

Jamie-BitFlight/data-exploration

Use when exploring unknown structured data files with dasel v3 — discover schema, list keys, find nested values, sample arrays, identify data types across JSON, YAML, TOML, XML, CSV, HCL, INI formats

Jamie-BitFlight/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

Jamie-BitFlight/delegate

Decompose substantive work into phases, dispatch each phase to a sub-agent, and adjudicate what comes back. Use whenever a request asks for implementation, investigation, a fix, a review, or any change to files — including small ones — and whenever you are about to read source or run a diagnostic yourself instead of handing it off. Also use when a report from a sub-agent needs judging, when a phase needs re-dispatching, or when a user names one instance of a pattern. Does not apply when your own prompt begins "Your ROLE_TYPE is sub-agent." — then follow references/sub-agent-contract.md instead.

Jamie-BitFlight/enterprise-hibernate-hbm

Dasel v3 query patterns for Hibernate .hbm.xml mapping files — entity-table binding, Java property-to-column extraction, one-to-many set/list/bag relationship tracing, many-to-one foreign key discovery, batch scanning across 60+ HBM files. Use when querying Hibernate ORM class mappings, extracting schema metadata from Java persistence layer, or auditing entity-column relationships in enterprise legacy codebases.

Jamie-BitFlight/enterprise-installanywhere

Dasel v3 query patterns for InstallAnywhere .iap_xml installer definitions — use when querying action sequences, discovering variables, resolving platform conditions, navigating panels, or comparing installer variants. Files are 2.5+ MB, 65,000+ lines — too large for context reads, requires structural dasel queries.

Jamie-BitFlight/enterprise-maven-pom

Dasel v3 selector patterns for Maven POM XML files — use when querying dependency versions, filtering by groupId or scope, extracting module hierarchy from parent POMs, or detecting version conflicts across enterprise multi-module Java projects. Load this skill when working with pom.xml files using dasel.

Jamie-BitFlight/enterprise-spring-xml

Dasel v3 selectors for Spring bean factory XML — use when querying any Spring ApplicationContext XML for bean discovery, dependency wiring, JMS destination mapping, property injection extraction, or cross-bean reference tracing. Load this skill before writing dasel selectors against Spring bean XML files (applicationContext.xml, *_beans.xml, spring-*.xml).

Skills relacionados