plugins/dasel/skills/data-exploration/SKILL.md
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
npx skillsauth add jamie-bitflight/claude_skills data-explorationInstall 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>
Dasel auto-detects format from file extension. Override with -i <format> when reading from stdin or when extension is ambiguous.
Format identifiers: json, yaml, toml, xml, csv, hcl, ini
Follow this sequence when encountering an unknown structured data file. Each step narrows scope.
Dasel infers format from file extension. For stdin or non-standard extensions, specify explicitly:
cat mystery_file | dasel -i json 'keys($this)'
dasel -f config.yaml 'keys($this)'
Output: array of top-level key names. This is always the first exploration command.
For small files (configs, manifests), dump the full document:
dasel -f config.yaml
For large files, skip to Step 4.
Navigate level by level:
dasel -f config.yaml 'server'
dasel -f config.yaml 'keys(server)'
dasel -f config.yaml 'keys(server.logging)'
Recursive key discovery across all depths:
dasel -f config.yaml '..keys($this)'
Preview first few elements without loading entire array:
dasel -f data.json 'items[0:3]'
Single element inspection:
dasel -f data.json 'items[0]'
Determine the type of any node:
dasel -f data.json 'typeOf(settings)'
dasel -f data.json 'typeOf(items[0].count)'
Return values: "string", "array", "bool", "null", "int", "float"
Once path is known, extract specific values:
dasel -f config.yaml 'database.connection.host'
dasel -f data.json 'users[0].email'
Start at root, enumerate keys at each level before going deeper:
dasel -f file.json 'keys($this)' # Level 0
dasel -f file.json 'keys(metadata)' # Level 1
dasel -f file.json 'keys(metadata.labels)' # Level 2
When the file is too large for manual traversal, use search() with predicates:
# Find all objects containing a specific key
dasel -f data.json 'search(has("email"))'
# Find all objects with both "id" and "name" keys
dasel -f data.json 'search(has("id") && has("name"))'
# Find nodes where a value matches
dasel -f data.json 'search($this == 42)'
dasel -f data.json 'len(items)'
dasel -f data.json 'len(keys($this))'
Extract a field from all array elements, then deduplicate in shell:
dasel -f data.json 'items.map(category)' | dasel -i json '$this...' | sort -u
Find all values for a key name at any depth:
dasel -f data.json '..name'
Get first element of every nested array:
dasel -f data.json '..[0]'
For detailed per-format exploration commands, see Format-Specific Recipes.
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.