SKILLEMALL.ai
RU Sign in

AB distributed-debugging-debug-trace

You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices for development and production environments.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 2 files body ≈ 474 tokens Open the sourcegithub.com↗ analyzed 16 h ago

You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools.

As a process B 72/100 · Nearly there — weak spots: result and completion, failures and branches

PersonaSoftware 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
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
77
Run on models
none yet
Process rating
B
72/100
Nearly there
Failures and branches w 10
0
Result and completion w 14
40
When it triggers w 12
50
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: distributed-debugging-debug-trace (sickn33/agentic-awesome-skills)

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

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "date_added"

    Process rating: all ten parameters 72/100

    • 0Failures and branches. Linear process with no failure handling
    • 40Result and completion. Does not say what the result is
    • 50When it triggers. No condition that starts the skill
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 18 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 474 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

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 279: enough signal without eating the budget
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 18 items

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