KaryawanSurgaKaryawanSurga/tokensaver-plugin/skills/json-lens/SKILL.md

json-lens

Skill1 starsChanged 45 days agoMITView on GitHub

Inspect and query large JSON and JSONL files. Use when exploring data exports, event streams, fixtures, or config files that are too large to read, or when only a few values are needed from a document.

In this repository9 other files it gives its agents.
- commitsmithSkill
- context-budgetSkill
- gatewaySkill
- injection-guardSkill
- log-tailSkill
- repo-mapSkill
- secret-scanSkill
- tokensaverSkill
- web-snapshotSkill

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Look at big JSON without loading big JSON: structure summaries and jq-like queries with compact, budgeted results.
line 15
Very specific:
Call inspect_json before writing any parser.
line 26
Distinctive:
Write a query from what the structure shows.
line 27
Very specific:
Use comma-separated paths (.id, .name) to project several fields at once.
line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

JSON lens

Look at big JSON without loading big JSON: structure summaries and jq-like queries with compact, budgeted results.

MCP tools

Tool	Use it for
`inspect_json`	Shape first: types, keys, array lengths, samples.
`query_json`	Pull values: `.users[*].name`, `.items[0]`, `.a	length`.

Workflow

Call inspect_json before writing any parser.
Write a query from what the structure shows.
Use comma-separated paths (.id, .name) to project several fields at once.
Pipes: keys, length, type. Results are capped by limit and token budget.

CLI fallback

npx -y mcp-json-lens inspect ./data.json
npx -y mcp-json-lens query ./data.json --expr '.users[*].name'
npx -y mcp-json-lens query ./events.jsonl --expr '.level, .user' --limit 10

JSONL queries report line numbers per match.

Tips

The loader caps file size and line counts; huge files fail fast with a clear message instead of hanging.
Mislabeled files (JSONL saved as .json) are detected automatically.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free