Agent skill

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

Stars 33
Forks 4

Install this agent skill to your Project

npx add-skill https://github.com/Jamie-BitFlight/claude_skills/tree/main/plugins/dasel/skills/data-exploration

SKILL.md

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:

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

Step 2 — Top-Level Keys

bash
dasel -f config.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:

bash
dasel -f config.yaml

For large files, skip to Step 4.

Step 4 — Nested Key Discovery

Navigate level by level:

bash
dasel -f config.yaml 'server'
dasel -f config.yaml 'keys(server)'
dasel -f config.yaml 'keys(server.logging)'

Recursive key discovery across all depths:

bash
dasel -f config.yaml '..keys($this)'

Step 5 — Array Sampling

Preview first few elements without loading entire array:

bash
dasel -f data.json 'items[0:3]'

Single element inspection:

bash
dasel -f data.json 'items[0]'

Step 6 — Type Inspection

Determine the type of any node:

bash
dasel -f data.json 'typeOf(settings)'
dasel -f data.json 'typeOf(items[0].count)'

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

Step 7 — Value Extraction

Once path is known, extract specific values:

bash
dasel -f config.yaml 'database.connection.host'
dasel -f data.json 'users[0].email'

Exploration Patterns

Breadth-First Exploration

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

bash
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

Search-Based Exploration (Large Files)

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

bash
# 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)'

Count Elements

bash
dasel -f data.json 'len(items)'
dasel -f data.json 'len(keys($this))'

Unique Value Discovery

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

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

Recursive Descent

Find all values for a key name at any depth:

bash
dasel -f data.json '..name'

Get first element of every nested array:

bash
dasel -f data.json '..[0]'

Format-Specific Recipes

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

References

Expand your agent's capabilities with these related and highly-rated skills.

Jamie-BitFlight/claude_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'.

33 4
Explore
Jamie-BitFlight/claude_skills

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.

33 4
Explore
Jamie-BitFlight/claude_skills

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.

33 4
Explore
Jamie-BitFlight/claude_skills

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.

33 4
Explore
Jamie-BitFlight/claude_skills

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".

33 4
Explore
Jamie-BitFlight/claude_skills

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.

33 4
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results