SKILLEMALL.ai
GitHub ↗ RU Sign in

BB session-search

Find Claude Code sessions tracked by the Agent Monitor by project (cwd), model, status, or date, then rank the matches by cost or recency. Pulls the session list and the distinct cwd / facet values so filters use real values rather than guesses. Use when locating a session — "find my EstateWise sessions", "which Opus runs errored this week", "most expensive sessions in /repo".

hoangsonww/Claude-Code-Agent-Monitor Agent Skills author: hoangsonww 2 files body ≈ 607 tokens Open the sourcegithub.com↗ analyzed 25 h ago

Find Claude Code sessions tracked by the Agent Monitor by project (cwd), model, status, or date, then rank the matches by cost or recency.

As a process B 68/100 · Nearly there — weak spots: when it triggers, failures and branches

ProcedureAI and agentsData and analyticsSoftware developmenttype 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
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
B
68/100
Nearly there
Failures and branches w 10
0
When it triggers w 12
20
Tools and files w 18
60
the three weakest of ten parameters · all ten

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: 2. 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 68/100

    • 0Failures and branches. Linear process with no failure handling
    • 20When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 100Steps. 5 steps
    • 100Inputs and preconditions. Inputs and preconditions are listed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 607 tokens
    • 100Running it twice. No mutating operations
    • 100Progress reporting. Reports progress

    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

    • +4Description does not say when NOT to use the skill (false activations)
    • +4No input/output examples
    • -4Absolute local paths (C:\Users, /home/…): not portable
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 3 example trigger phrases
    • +3Description length 379: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 5 items
    • +3Output format is stated explicitly

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