AB log-analyzer
Securely analyze system and application logs with automatic sensitive data redaction. Supports OpenClaw gateway logs (journalctl), RAG indexing logs, and query logs. Finds errors, summarizes patterns, and searches across sources. Triggers on "check logs", "show errors", "analyze logs", "cosa è successo", "log errors", "any errors", "search logs". NOT for: reading arbitrary files, accessing logs outside whitelisted paths.
As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 65/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (log-analyzer) differs from the folder (lookupmark-log-analyzer)
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 5 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 336 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 424: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (1 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.