SKILLEMALL.ai
GitHub ↗ RU Sign in

BC here-now

Publish sites to {slug}.here.now and store files in Drives.

NousResearch/hermes-agent Hermes author: NousResearch MIT 3 files · 2 scripts body ≈ 2 093 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Publish sites to {slug}.here.now and store files in Drives.

As a process C 54/100 · Has gaps — weak spots: result and completion, failures and branches, running it twice

IntegrationSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
99
Quality 40%
72
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. 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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration net-credential-use scripts/publish.sh:104
    Credential used in a network call (verify the destination is the intended service) (detector / deny-list definition; the skill's own vendor host)
    if [[ -n "$API_KEY" && "$BASE_URL" != "https://here.now" && "$ALLOW_NON_HERENOW_BASE_URL" -ne 1 ]]; then
    detectorvendor-host

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

Against the Agent Skills spec

  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "prerequisites"

Process rating: all ten parameters 54/100

  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 23 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Consistency. The Hermes dialect needs category and tags
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 39 steps
  • 100Execution cost. Instruction body is 2093 tokens
  • 100Progress reporting. Reports progress
  • 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
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 59: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 39 items
  • +4Has examples (8 code blocks)
  • +3All 2 scripts are documented
  • +1License stated

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