SKILLEMALL.ai
GitHub ↗ RU Sign in

AC box

Box manages cloud files, sharing, search, and metadata.

NousResearch/hermes-agent Hermes author: NousResearch MIT 11 files body ≈ 2 817 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Box manages cloud files, sharing, search, and metadata.

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

IntegrationData and analyticstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
99
Quality 40%
81
Run on models
none yet
Process rating
C
57/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
Inputs and preconditions w 11
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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Concealment en-hide-from-user references/hubs.md:19
      Instruction to hide actions from the user (negated — the text forbids it)
      For a known Hub URL or ID, run `box hubs:get <HUB_ID>` directly even if the list is empty. Report each Hub as `https://app.box.com/hubs/<HUB_ID>`. Check `is_ai_enabled` before asking a question, then
      negated

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "prerequisites"

    Process rating: all ten parameters 57/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 30Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 7 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
    • 60Consistency. The Hermes dialect needs category and tags
    • 100Steps. 25 steps
    • 100Failures and branches. 4 branches, has a failure section
    • 100Execution cost. Instruction body is 2817 tokens
    • low 10 top-level sections: this looks like several domains in one skill
    • low The response is described with custom markup (3 tags): a typed call is more reliable

    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 55: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +2Single-language instructions
    • +4Structure: 11 headings
    • +3Step-by-step instructions: 25 items
    • +4Reference files are cited in the instructions (10 of 10)
    • +1License stated

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