SKILLEMALL.ai
GitHub ↗ RU Sign in

AB juniper-device-health

Juniper JunOS device health check and triage procedure. Use when troubleshooting Juniper MX, SRX, EX, QFX, or PTX platforms — assessing Routing Engine health, Packet Forwarding Engine state, chassis alarms, system resources, and environment. Covers dual-RE failover detection, alarm severity triage, PFE statistics analysis, and commit-correlated diagnostics. Procedure begins with RE mastership verification — health data from the wrong RE produces incorrect assessments.

ClawHub Agent Skills author: Vahagn Madatyan v1.0.0 MIT-0 4 files body ≈ 3 741 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 70/100 · Nearly there — weak spots: result and completion, when it triggers, running it twice

ProcedureInfrastructureData and analyticstype 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%
89
Run on models
none yet
Process rating
B
70/100
Nearly there
Result and completion w 14
0
When it triggers w 12
20
Running it twice w 4
30
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: 4. 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 70/100

    • 0Result and completion. Does not say what the result is
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 35 mutating operations with no state check
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 45 steps
    • 100Failures and branches. 3 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3741 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)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +3Description length 472: enough signal without eating the budget
    • +4Structure: 24 headings
    • +3Step-by-step instructions: 45 items
    • +4Has examples (10 code blocks)
    • +4Reference files are cited in the instructions (1 of 2)
    • +1License stated

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

    External checks

    ClawHub: suspicious
    This Juniper health-check skill is mostly a normal diagnostic guide, but it is labeled read-only while recommending actions that can change or delete data on network devices.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026