Skip to content
cccskills
FreePublished on GitHub

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

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md4.2 KB
  • references/format-recipes.md8.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Data Exploration with Dasel v3

<when_to_use>

Activate this skill when:

  • Exploring unfamiliar structured data files (config, API responses, datasets)
  • Discovering the schema or shape of a document before modifying it
  • Investigating nested config structures (Kubernetes manifests, CI pipelines, package files)
  • Sampling large arrays or deeply nested objects to understand content
  • Identifying data types before transformation or extraction

</when_to_use>

Supported Formats

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

Universal Exploration Workflow

Follow this sequence when encountering an unknown structured data file. Each step narrows scope.

Step 1 — Format Detection

Dasel infers format from file extension. For stdin or non-standard extensions, specify explicitly:

cat mystery_file | dasel -i json 'keys($this)'

Step 2 — Top-Level Keys

cat config.yaml | dasel -i yaml 'keys($this)'

Output: array of top-level key names. This is always the first exploration command.

Step 3 — Structure Preview

For small files (configs, manifests), dump the full document:

cat config.yaml | dasel -i yaml

For large files, skip to Step 4.

Step 4 — Nested Key Discovery

Navigate level by level:

cat config.yaml | dasel -i yaml 'server'
cat config.yaml | dasel -i yaml 'keys(server)'
cat config.yaml | dasel -i yaml 'keys(server.logging)'

Recursive key discovery across all depths:

cat config.yaml | dasel -i yaml '..keys($this)'

Step 5 — Array Sampling

Preview first few elements without loading entire array:

cat data.json | dasel -i json 'items[0:3]'

Single element inspection:

cat data.json | dasel -i json 'items[0]'

Step 6 — Type Inspection

Determine the type of any node:

cat data.json | dasel -i json 'typeOf(settings)'
cat data.json | dasel -i json 'typeOf(items[0].count)'

Return values: "string", "array", "bool", "null", "int", "float"

Step 7 — Value Extraction

Once path is known, extract specific values:

cat config.yaml | dasel -i yaml 'database.connection.host'
cat data.json | dasel -i json 'users[0].email'

Exploration Patterns

Breadth-First Exploration

Start at root, enumerate keys at each level before going deeper:

cat file.json | dasel -i json 'keys($this)'           # Level 0
cat file.json | dasel -i json 'keys(metadata)'         # Level 1
cat file.json | dasel -i json 'keys(metadata.labels)'  # Level 2

Search-Based Exploration (Large Files)

When the file is too large for manual traversal, use search() with predicates:

# Find all objects containing a specific key
cat data.json | dasel -i json 'search(has("email"))'

# Find all objects with both "id" and "name" keys
cat data.json | dasel -i json 'search(has("id") && has("name"))'

# Find nodes where a value matches
cat data.json | dasel -i json 'search($this == 42)'

Count Elements

cat data.json | dasel -i json 'len(items)'
cat data.json | dasel -i json 'len(keys($this))'

Unique Value Discovery

Extract a field from all array elements, then deduplicate in shell:

cat data.json | dasel -i json 'items.map(category)' | dasel -i json '$this...' | sort -u

Recursive Descent

Find all values for a key name at any depth:

cat data.json | dasel -i json '..name'

Get first element of every nested array:

cat data.json | dasel -i json '..[0]'

Format-Specific Recipes

For detailed per-format exploration commands, see Format-Specific Recipes.

References

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Add automated documentation updater to any Claude skill. Creates a Python sync script that downloads upstream docs, processes markdown for AI consumption, and maintains local cache with configurable refresh. Collects template variables, then delegates implementation through 5-phase workflow. Use when adding auto-updating reference documentation to plugins or skills.

The English summary is being prepared. Showing the original description.

Jamie-BitFlight/claude_skills67Updated Oct 18, 2026

SAM-style feature initiation workflow — discovery through codebase analysis, architecture spec, task decomposition, validation, and context manifest. Use when a user asks to add a feature, plan a feature, or convert an idea into an executable SAM plan.

The English summary is being prepared. Showing the original description.

Jamie-BitFlight/claude_skills67Updated Oct 18, 2026

Browser automation for AI agents using the agent-browser CLI and Playwright. Use when navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging into sites, or automating any browser task. Triggers on "open a website", "fill out a form", "click a button", "scrape data", "test this web app", "automate browser actions", or any programmatic web interaction request.

The English summary is being prepared. Showing the original description.

Jamie-BitFlight/claude_skills67Updated Oct 18, 2026

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.

The English summary is being prepared. Showing the original description.

Jamie-BitFlight/claude_skills67Updated Oct 18, 2026

Runs the description-drift experiment — spawns all Claude Code agents simultaneously to collect self-reported capabilities, then compares them against static frontmatter descriptions to reveal how reliable orchestrator routing based on descriptions actually is. Use when measuring description drift across the agent fleet, re-running the capability collection experiment, analyzing a specific agent's self-reported capabilities, or auditing whether frontmatter descriptions accurately reflect agent behavior.

The English summary is being prepared. Showing the original description.

Jamie-BitFlight/claude_skills67Updated Oct 18, 2026

Create or adapt Claude Code agent definitions. Use when creating an agent, changing subagent configuration, selecting agent scope, or designing a specialized delegation role.

The English summary is being prepared. Showing the original description.

Jamie-BitFlight/claude_skills67Updated Oct 18, 2026

See all skills by Jamie-BitFlight

Report a problem with this skill