Menu
Use when searching non-code corpora: query JSON/YAML/config (jq, yq, gron), tabular data files (duckdb, sqlite-utils), or content inside PDFs/Office/archives (rga, pandoc, pdftotext).
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when creating or editing a plugin for a multi-host GitHub Copilot / APM / Claude Code marketplace — required manifests, the plugin.json ⇆ apm.yml mirroring rule, portable env-var and install conventions, component layout, and the catalog entry.
Use when every unit of a corpus must be accounted for rather than merely searched — auditing a document set, log archive, or file tree with provable coverage and gaps split into truly absent versus undecidable.
Use when searching source code: text/regex (ripgrep), structural/AST patterns (ast-grep, semgrep), symbol definitions/references/callers (LSP, GNU Global, ctags), when/why code changed (git history), structural rewrites (comby), or size/complexity (tokei, scc).
Use when deciding WHERE a piece of guidance should live — always-on memory (CLAUDE.md / AGENTS.md), a path-scoped rule, an on-demand skill, a subagent, an MCP server, or a deterministic hook — and how to keep the always-on budget small.
Use for semantic search over a markdown corpus when keywords aren't enough (you know the meaning, not the exact words), or hybrid semantic plus lexical search when both meaning and exact terms matter. Index once, then query.
Use when capturing, recalling, reviewing, or consolidating durable project memory across sessions, especially decisions, constraints, procedures, and episodes that must retain provenance and freshness.
| name | data-and-docs-search |
| description | Use when searching non-code corpora: query JSON/YAML/config (jq, yq, gron), tabular data files (duckdb, sqlite-utils), or content inside PDFs/Office/archives (rga, pandoc, pdftotext). |
| license | MIT |
| compatibility | Optional tools: jq, yq, gron, duckdb, sqlite-utils, rga (ripgrep-all), pandoc, pdftotext. |
| metadata | {"author":"Mark Beacom","version":"0.1.0"} |
| allowed-tools | Bash(jq:*) Bash(yq:*) Bash(gron:*) Bash(duckdb:*) Bash(sqlite-utils:*) Bash(rga:*) Bash(pandoc:*) Bash(pdftotext:*) Bash(rg:*) Bash(rtk rg:*) Read Glob Grep |
Search beyond source code.
This skill is portable across GitHub Copilot, APM, and Claude Code; keep the
references/ folder next to SKILL.md when copying it into a Copilot skill
location.
| Corpus | Use | Reference |
|---|---|---|
| JSON | jq, or gron + rg | jq-yq-gron |
| YAML / TOML / XML | yq | jq-yq-gron |
| CSV / Parquet / JSON at scale | duckdb, sqlite-utils | data-files |
| PDFs / Office docs / archives | rga, pandoc, pdftotext | docs |
Decision flow: known JSON path → jq | "grep this JSON" → gron \| rg |
YAML/TOML → yq | tabular/analytical → duckdb | inside PDFs/docs → rga.
gron file.json | rg pattern turns nested JSON into greppable lines — ideal
when you don't know the exact path. gron -u reverses it.rga is rg for non-text files; first run builds a cache, later runs are fast.
Scope with --rga-adapters and the same globs as rg.duckdb reads files directly:
duckdb -c "SELECT ... FROM 'data.parquet' ...".scripts/check-tools.sh and install what's
missing before relying on them.rtk is installed, prefix rtk rg … for compact output; the data tools
(jq/yq/gron/duckdb/rga/…) aren't rtk-wrapped — run them directly.
See the rtk note in code-search.