SKILLEMALL.ai
GitHub ↗ RU Sign in

AB coding-agent-sessions

Finds, reads, and reconstructs coding-agent sessions across Codex, Claude, OpenCode, OMO/Senpi, and other local agent logs. Use when asked to find or search past sessions, transcripts, or subagent runs, or to recover what an earlier session did.

code-yeongyu/oh-my-openagent Agent Skills author: code-yeongyu NOASSERTION 33 files · 23 scripts body ≈ 2 740 tokens Open the sourcegithub.com↗ analyzed 11 d ago

Finds, reads, and reconstructs coding-agent sessions across Codex, Claude, OpenCode, OMO/Senpi, and other local agent logs.

As a process B 70/100 · Nearly there — weak spots: inputs and preconditions, running it twice

ProcedureSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
94
Run on models
none yet
Process rating
B
70/100
Nearly there
Inputs and preconditions w 11
0
Running it twice w 4
30
Tools and files w 18
60
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: oh-my-opencode

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • 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: 32. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 70/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 2 mutating operations with no state check
    • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 5 steps
    • 100Failures and branches. 2 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2740 tokens
    • 100Progress reporting. Reports progress
    • low The response is described with custom markup (5 tags): a typed call is more reliable

    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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 245: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 5 items
    • +3Output format is stated explicitly
    • +4Has examples (2 code blocks)
    • +4Reference files are cited in the instructions (5 of 5)
    • +3All 1 scripts are documented

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 94.

    In the sandbox The scripts kept to themselves

    The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.

    Запущено 12 скриптов, ещё 4 не поместились в лимит; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.

    Из них 11 не дошли до работы, и об их поведении мы ничего не узнали.

    scripts/find-agent-sessions.pyничего за пределами своей папки
    scripts/agent_sessions/aside_scanner.pyне запустился: ImportError: cannot import name 'MappingProxyType' from partially initialized module 'types' (most likely due to a circular import) (/work/s
    scripts/agent_sessions/claude.pyне запустился: ImportError: cannot import name 'GenericAlias' from partially initialized module 'types' (most likely due to a circular import) (/work/scrip
    scripts/agent_sessions/cli.pyне запустился: ImportError: cannot import name 'GenericAlias' from partially initialized module 'types' (most likely due to a circular import) (/work/scrip
    scripts/agent_sessions/codex.pyне запустился: ImportError: cannot import name 'MappingProxyType' from partially initialized module 'types' (most likely due to a circular import) (/work/s
    scripts/agent_sessions/file_scanners.pyне запустился: ImportError: cannot import name 'GenericAlias' from partially initialized module 'types' (most likely due to a circular import) (/work/scrip
    scripts/agent_sessions/jsonio.pyне запустился: ImportError: cannot import name 'GenericAlias' from partially initialized module 'types' (most likely due to a circular import) (/work/scrip
    scripts/agent_sessions/kiro_scanner.pyне запустился: ImportError: cannot import name 'GenericAlias' from partially initialized module 'types' (most likely due to a circular import) (/work/scrip
    scripts/agent_sessions/opencode.pyне запустился: ImportError: cannot import name 'GenericAlias' from partially initialized module 'types' (most likely due to a circular import) (/work/scrip
    scripts/agent_sessions/pi_family.pyне запустился: ImportError: cannot import name 'GenericAlias' from partially initialized module 'types' (most likely due to a circular import) (/work/scrip
    scripts/agent_sessions/scanners.pyне запустился: ImportError: cannot import name 'GenericAlias' from partially initialized module 'types' (most likely due to a circular import) (/work/scrip
    scripts/agent_sessions/sqlite_optional_scanners.pyне запустился: ImportError: cannot import name 'MappingProxyType' from partially initialized module 'types' (most likely due to a circular import) (/work/s

    29 Sept 2026