SKILLEMALL.ai
GitHub ↗ RU Sign in

AC clawdbot-logs

Analyze Clawdbot logs and diagnostics. Use when the user asks about bot performance, response times, errors, session stats, token usage, API costs, or wants to debug slow responses.

modbender/skill-library-mcp Agent Skills author: modbender MIT 3 files · 2 scripts body ≈ 548 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Analyze Clawdbot logs and diagnostics.

As a process C 59/100 · Has gaps — weak spots: inputs and preconditions, failures and branches

AnalyzerTelegramPersonal productivitySoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
90
Run on models
none yet
Process rating
C
59/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
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: 3. 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 59/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 60Tools and files. Uses tools (bash) 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
    • 75Steps. 3 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 548 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

    • +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 181: enough signal without eating the budget
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 3 items
    • +3Output format is stated explicitly
    • +4Has examples (9 code blocks)
    • +3All 2 scripts are documented

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