SKILLEMALL.ai
GitHub ↗ RU Sign in

CB unified-ai-gateway

Operate and evaluate Unified AI System through fifteen governed MCP tools, including provider-free prompt enhancement, while preserving fake-provider, authorization, and evidence boundaries.

sickn33/agentic-awesome-skills Hermes author: sickn33 MIT 1 file body ≈ 3 837 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Operate and evaluate Unified AI System through fifteen governed MCP tools, including provider-free prompt enhancement, while preserving fake-provider…

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

IntegrationGitHubDockerAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code Hermes Agent
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
94
Quality 40%
80
Run on models
none yet
Process rating
B
67/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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 · 2

✓ No critical or high findings

Medium and low: 2
  • medium Dangerous commands cmd-privilege SKILL.md:79
    Privilege escalation / world-writable permissions
    # Extract as an unprivileged user, never preserve owner/setuid permissions, into this private empty directory.
  • low Risky intent intent-offensive-security SKILL.md:140
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    pulling, container networking, Linux capabilities, and privilege escalation

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

Against the Agent Skills spec

  • warning description-long-hermes description is 190 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "source_repo"
  • note frontmatter-key unknown frontmatter key "source_type"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "license_source"

Process rating: all ten parameters 67/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 8 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 58 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3837 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 11 top-level sections: this looks like several domains in one skill

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 190: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 58 items
  • +4Has examples (4 code blocks)
  • +1License stated

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