SKILLEMALL.ai

AB grafana

Operate, configure, provision, secure, and troubleshoot Grafana OSS, Enterprise, and Cloud, including dashboards, folders, data sources, annotations, alert rules, contact points, notification policies, silences, mute timings, service accounts, RBAC, plugins, APIs, and as-code workflows. Use for Grafana product work and Grafana-side integrations. Do not use for defining SLOs or paging policy, operating Prometheus/Loki/Tempo/InfluxDB backends, generic Docker/Kubernetes/Terraform/reverse-proxy work, plugin development, or authorized security assessments; use the corresponding specialist skill.

magnus919/agent-skills Agent Skills author: magnus919 MIT 11 files body ≈ 2 186 tokens Open the sourcegithub.com↗ analyzed 25 h ago

Operate, configure, provision, secure, and troubleshoot Grafana OSS, Enterprise, and Cloud, including dashboards, folders, data sources, annotations, alert…

As a process B 67/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice

ProcedureTerraformKubernetesDockerInfrastructureSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
93
Run on models
none yet
Process rating
B
67/100
Nearly there
Inputs and preconditions w 11
0
Running it twice w 4
30
Result and completion w 14
40
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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: 10. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 42): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 67/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 5 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 100Tools and files. No external tools needed
    • 100Steps. 15 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2186 tokens
    • 100Progress reporting. Reports progress
    • low No test case covers injection arriving through data

    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
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 597: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 15 items
    • +4Has examples (1 code blocks)
    • +4Reference files are cited in the instructions (7 of 7)
    • +1License stated

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