ワンクリックで
parse-json
Inspect and extract data from unknown JSON files without fumbling
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Inspect and extract data from unknown JSON files without fumbling
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when someone is about to lose access to a machine (shared server, lab box, cloud/VM instance, expiring rental) and needs to preserve all their work before it's gone. Systematically finds everything that exists ONLY on that machine — unpushed commits, stashes, untracked/uncommitted files, dirty submodules, non-git dirs, loose files, and large gitignored artifacts — and backs it up to GitHub / HuggingFace / an off-machine archive, non-destructively. Triggers on "losing access to this machine", "back up everything before I lose the server", "migrating off this box", "decommission", "my instance expires".
Use when preparing a paper's camera-ready or arXiv release — de-anonymizing an accepted submission, packaging an arXiv tarball, checking dual-submission safety against a concurrent venue (e.g. a paper accepted at a workshop that's also under review at NeurIPS/ICML), or flagging reviewer-requested post-review additions. Encodes a byte-identity discipline (the public version changes ONLY author/venue metadata, never content), a numbers-from-scripts integrity gate, and the arXiv mechanics that actually bite.
Spin up one or more fresh-context subagents to critically evaluate a proposed theory, hypothesis, interpretation, or experimental design before committing to it. Use when the user says "have an agent critique this" / "get a second opinion on" / "is this design sound" / invokes /critique, or proactively before running any experiment or committing to a non-trivial theoretical claim.
Use when launching a multi-hour neural-network training, fine-tune, or other long GPU job autonomously from Claude Code and you need to catch failures (NaN, stuck-at-chance, dead process, throughput collapse, OOM) early instead of waking up to a wasted GPU window.
Use when the user asks to check, audit, or improve a website or web project for accessibility (a11y), WCAG compliance, screen reader support, keyboard navigation, color contrast, or alt text. Triggers a plan-mode investigation against the TeachAccess design and code checklists, then implements approved fixes.
Consolidate scattered research notes, logs, experiment outputs, and submodule docs into a single living research paper. Use when the user wants to pull together multiple source documents into one structured paper.
| name | parse-json |
| description | Inspect and extract data from unknown JSON files without fumbling |
| user_invocable | true |
When the user asks you to parse, inspect, or extract data from a JSON file (or when you encounter an unknown JSON file during work), follow this two-phase approach. Never guess the structure — always inspect first.
Run a single Python snippet that reveals the full structure:
python3 -c "
import json, sys
with open('FILE_PATH') as f:
data = json.load(f)
def describe(obj, path='root', depth=0, max_depth=3):
indent = ' ' * depth
if isinstance(obj, dict):
print(f'{indent}{path}: dict with {len(obj)} keys: {list(obj.keys())[:15]}')
if depth < max_depth:
for k in list(obj.keys())[:5]:
describe(obj[k], f'{path}[\"{k}\"]', depth+1, max_depth)
elif isinstance(obj, list):
print(f'{indent}{path}: list of {len(obj)} items')
if len(obj) > 0 and depth < max_depth:
describe(obj[0], f'{path}[0]', depth+1, max_depth)
else:
val = repr(obj)
if len(val) > 80: val = val[:80] + '...'
print(f'{indent}{path}: {type(obj).__name__} = {val}')
describe(data)
"
Only after structure is known, write extraction code using the actual keys and nesting. Use statistics.mean/stdev for aggregation. Print results in a clean tabular format.