SKILLEMALL.ai
GitHub ↗ RU Sign in

DC entropy-box

Entropy Box knowledge-compiler for embodied-AI: turns bounded requirements into grounded workflows via Solution Consult, Search, Lookup, and Evidence. Do not use it to control physical robots.

Not recommendedcritical or high security findings · low grade D
sickn33/agentic-awesome-skills Hermes author: sickn33 MIT 4 files body ≈ 5 190 tokens Open the sourcegithub.com↗ analyzed 26 h ago

Entropy Box knowledge-compiler for embodied-AI: turns bounded requirements into grounded workflows via Solution Consult, Search, Lookup, and Evidence.

As a process C 63/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

ProcedureResearchAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code Hermes Agent
JSON
Technical rating
D
53/100
safety, quality, tests
Safety 60%
39
Quality 40%
74
Run on models
none yet
Process rating
C
63/100
Has gaps
Inputs and preconditions w 11
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

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. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
  3. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 SKILL.md:395
    Webhook / callback URL commonly used for exfiltration (verify the destination)
    - Project site: https://xiangshang.ngrok.app/
  • high Exfiltration exfil-webhook-url SKILL.md:399
    Webhook / callback URL commonly used for exfiltration (verify the destination)
    - Live API schema: https://xiangshang.ngrok.app/openapi.json
Medium and low: 5
  • medium Exfiltration exfil-webhook-url references/api.md:3
    Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)
    Base URL: `https://xiangshang.ngrok.app`
    quoted
  • medium Exfiltration exfil-webhook-url references/api.md:16
    Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)
    -X POST "https://xiangshang.ngrok.app/api/search" \
    quoted
  • medium Exfiltration exfil-webhook-url references/api.md:61
    Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)
    -X POST "https://xiangshang.ngrok.app/api/evidence/search" \
    quoted
  • medium Exfiltration exfil-webhook-url references/api.md:91
    Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)
    -X POST "https://xiangshang.ngrok.app/api/lookup" \
    quoted
  • medium Exfiltration exfil-webhook-url references/api.md:139
    Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)
    -X POST "https://xiangshang.ngrok.app/api/consult" \
    quoted

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

Against the Agent Skills spec

  • warning description-long-hermes description is 192 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning body-long SKILL.md body ≈ 5190 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "license_source"
  • 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"

Process rating: all ten parameters 63/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 8 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
  • 70Execution cost. Instruction body is 5190 tokens
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 91 steps
  • 100Consistency. Name and required fields are in place
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 12 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 192: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 91 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)
  • +1License stated

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