SKILLEMALL.ai

CD aiops-agent

AI驱动的智能运维系统,实现主动预警、智能诊断和自动化治理

Not recommendedcritical or high security findings
modbender/skill-library-mcp Agent Skills author: modbender MIT 80 files · 1 script body ≈ 494 tokens Open the sourcegithub.com analyzed 2 d ago

AI驱动的智能运维系统,实现主动预警、智能诊断和自动化治理

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
66/100
safety, quality, tests
Safety 60%
76
Quality 40%
52
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Exfiltration
If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 7

  • high Exfiltration exfil-webhook-url docs/CONFIGURATION.md:432
    Webhook / callback URL commonly used for exfiltration (verify the destination)
    WEBHOOK_URL=https://hooks.slack.com/services/xxx
Medium and low: 6
  • low Exfiltration read-dotenv docs/CONFIGURATION.md:66
    Reads a .env file
    cp .env.example .env
  • low Exfiltration read-dotenv docs/IMPLEMENTATION.md:502
    Reads a .env file
    cp .env.example .env
  • low Exfiltration exfil-webhook-url docs/IMPLEMENTATION.md:834
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    WEBHOOK_URL=https://hooks.slack.com/...
    placeholder
  • low Exfiltration read-dotenv docs/QUICKSTART.md:25
    Reads a .env file
    cp .env.example .env
  • low Exfiltration read-dotenv minimal_publish.sh:36
    Reads a .env file
    cp .env.example "$TEMP_DIR/"
  • low Exfiltration read-dotenv SKILL.md:30
    Reads a .env file
    cp .env.example .env

Files scanned: 76. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-short description under 40 chars: too little signal for triggering
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "contact"

Process rating: all ten parameters 46/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 40Consistency. Frontmatter name (aiops-agent) differs from the folder (sre-agent)
  • 100Tools and files. No external tools needed
  • 100Steps. 26 steps
  • 100Execution cost. Instruction body is 494 tokens
  • 100Running it twice. No mutating operations

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)
  • +3Description length 29: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -2localhost URLs: will not work for another user
  • -212 emoji in the instructions: noise for the model
  • -43 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 26 items
  • +4Has examples (5 code blocks)

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