Pixel-CLI/pixel / .agents/skills/extract-probes
extract-probes
VerifiedMine this project's local agent transcripts for the tool sequences a brief probe could replace: /extract-probes, 'mine transcripts for probes', 'which tool sequences could the brief replace'. Ranks the most common pre-answer call sequences by question kind and maps each to an existing probe or a candidate.
Which tool sequences could the brief replace?
scripts/bench/extract-probes.py reads the transcripts this machine already holds and ranks what agents do before they
answer or edit. The ranking tells which probe to write next; the probe skill writes and proves it.
python3 -I scripts/bench/extract-probes.py [--since 30d] [--agent all|claude|codex|pi] [--top 20] [--kinds question|all|a,b]
Procedure
- Mine (the script, mechanical). Claude Code
~/.claude/projects/<slug>/*.jsonlfor this project and its worktrees; Codex~/.codex/sessions/**/rollout-*.jsonlwhosecwdis under the project (including its JSexectool, which batches shell commands). Pi has no reader yet and is skipped. Other readers worth reusing when widening this: thepixel-retroskill's transcript readers and the census-extract worktree'sextract.py/classify.py. - Segment: a user turn, then the tool calls before the first edit (
Edit,Write,apply_patch) or the end of the turn. Each call is normalised to a shape with paths reduced to roles:read(code|test|doc|config),grep,glob,bash:git-log,bash:--help,bash:pixel,tool:js, and so on. - Rank n-grams of 1 to 4 calls and the first six calls of a long turn by turns x calls saved, per question kind
(history, review, flow, config, tests, overview, lookup; the keyword heuristic of the brief).
--kinds alladds the task turns (other). - Map each row to the probe that covers it (
history-fallbackforgit log/show/diff,doc-sectionsfor documentation reads,config-registryfor config reads,name-filesfor listings) or mark it a candidate. - Validate a candidate with
scripts/bench/probe-loop.py --prompt "<a sample prompt of that cluster>": the current brief first, 1 live run, stop if it is already zero-call. Write the probe as a generic rule (theprobeskill's overfitting guard applies: no literal path or word from one session). - Report the ranked table: pattern -> turns -> calls it costs -> covering probe or candidate -> validation.
Privacy
Transcripts and prompts stay on this machine. The script keeps nothing: it prints counts and abstract shapes only, no prompt, path, command, output or secret, and writes no file. Do not paste a transcript, a prompt or a command from one into a PR, an issue or a probe; quote the shape and the count. If a secret shows up while debugging a reader, do not print it.
Limits
A keyword heuristic assigns the question kind, and most turns are tasks (other), not questions: the ranking says
what is common, not what is avoidable. Many bash:pixel rows are calls an installed brief already prompts. Treat
the table as a lead for probe-loop, which measures, not as a verdict.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |