AF debugging-log-analyser
Parse error logs, stack traces, and crash reports into a structured root cause diagnosis. Use when an application is throwing exceptions, crashing, or producing unexpected errors and you need to understand why and what to fix. Produces a structured diagnosis with error classification, stack trace walkthrough, probable root cause with confidence level, affected code path, a concrete code-level fix suggestion, and ordered next debugging steps.
Parse error logs, stack traces, and crash reports into a structured root cause diagnosis.
As a process F 61/100 · Will not run — References files that are not bundled: ../../docs/craft/incident-response.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../docs/craft/incident-response.md
Process rating: all ten parameters 61/100
- 0Tools and files. 1 referenced file(s) missing: ../../docs/craft/incident-response.md
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 42 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1520 tokens
- 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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 445: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 42 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.