SKILLEMALL.ai
GitHub ↗ RU Sign in

CC progressive-loading

Implements hub-and-spoke lazy loading to minimize token usage in large skills. Use when building multi-module skills that need conditional on-demand loading.

Not recommendedcritical or high security findings
athola/claude-night-market Hermes author: athola 25 files body ≈ 1 933 tokens Open the sourcegithub.com↗ analyzed 2 h ago

Implements hub-and-spoke lazy loading to minimize token usage in large skills.

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
C
70/100
safety, quality, tests
Safety 60%
67
Quality 40%
75
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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.

Dangerous commands
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. 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.
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 · 4

  • high Dangerous commands cmd-persistence modules/macos-patterns.md:59
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    ~/Library/LaunchAgents/
Medium and low: 3
  • medium Dangerous commands cmd-persistence modules/macos-patterns.md:98
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    User-scoped agents go in `~/Library/LaunchAgents/`. System-scoped
    quoted
  • medium Dangerous commands cmd-persistence modules/macos-patterns.md:99
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    daemons go in `/Library/LaunchDaemons/` and require root. Load
    quoted
  • medium Dangerous commands cmd-persistence modules/macos-patterns.md:100
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    with `launchctl load -w <path>`, unload with `launchctl unload`.
    quoted

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

Against the Agent Skills spec

  • warning description-long-hermes description is 157 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "alwaysApply"
  • note frontmatter-key unknown frontmatter key "dependencies"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "provides"
  • note frontmatter-key unknown frontmatter key "usage_patterns"
  • note frontmatter-key unknown frontmatter key "complexity"
  • note frontmatter-key unknown frontmatter key "model_hint"
  • note frontmatter-key unknown frontmatter key "estimated_tokens"
  • note frontmatter-key unknown frontmatter key "progressive_loading"
  • note frontmatter-key unknown frontmatter key "modules"
  • note edit-residue the text marks something as outdated (lines 150): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 85Steps. 69 steps, 1 vague phrases
  • 100Tools and files. Tools declared in frontmatter
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1933 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • 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
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 157: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 69 items
  • +4Has examples (4 code blocks)

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