AF read-claude-code-history
Reads, searches, and exports local Claude Code history without resuming work. Covers recent session inventory, exact session timelines, verbatim human input including queued mid-turn prompts, full-event keyword search, hybrid recall when wording changed, end-state triage, and deleted-file recovery across active Claude homes plus registered archives. Use whenever the user asks what they or Claude said, wants a Claude Code session ID or original context, remembers prior work vaguely, needs an old file from a transcript, or must prove what a Claude session contained before continuing it. Also owns the only Kimi CLI surface, via its Kimi inventory and search flags. For Codex history use read-codex-history; when the request names no platform at all or spans providers, start at local-conversation-history.
Reads, searches, and exports local Claude Code history without resuming work.
As a process F 46/100 · Will not run — References files that are not bundled: scripts/**/*.py
How to improve
- The text references files that are not there: add them or drop the references.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 26. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/**/*.py - note
edit-residuethe text marks something as outdated (lines 220, 227, 304): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 46/100
- 0Tools and files. 1 referenced file(s) missing: scripts/**/*.py
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 60Failures and branches. 2 branches
- 70Execution cost. Instruction body is 4401 tokens
- 100Steps. 24 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (9 tags): a typed call is more reliable
- medium 6 test cases, all positive: not one "should refuse" or "should ask first"
- low No test case covers injection arriving through data
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 810: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 15 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 8 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.