SKILLEMALL.ai
GitHub ↗ RU Sign in

BC lifepath

AI Life Simulator - Experience infinite lives year by year. Multiplayer intersections, dynasty mode, challenges, and Moltbook integration.

ClawHub Hermes author: ezbreadsniper v2.0.0 21 files · 2 scripts body ≈ 1 034 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
76/100
safety, quality, tests
Safety 60%
83
Quality 40%
66
Run on models
none yet
Process rating
C
61/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

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

Secrets in code 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 files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  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 · 9

✓ No critical or high findings

Medium and low: 9
  • medium Secrets in code secret-google-key src/services/storyGenerator.js:9
    Google API key (quoted — discussed, not commanded)
    'AIza…wh8',
    quoted
  • medium Secrets in code secret-google-key src/services/storyGenerator.js:10
    Google API key (quoted — discussed, not commanded)
    'AIza…chM'
    quoted
  • low Exfiltration read-dotenv deploy.sh:19
    Reads a .env file
    cp .env.example .env
  • low Exfiltration read-dotenv INSTALL.md:29
    Reads a .env file
    cp .env.example .env
  • low Exfiltration read-dotenv README.md:27
    Reads a .env file
    cp .env.example .env
  • low Exfiltration read-dotenv SKILL.md:99
    Reads a .env file
    cp .env.example .env
  • low Exfiltration read-dotenv src/server.js:51
    Reads a .env file (quoted — discussed, not commanded)
    console.error('Copy .env.example to .env and fill in the values');
    quoted
  • low Secrets in code secret-high-entropy-token src/services/storyGenerator.js:9
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    'AIza…wh8',
    quoted
  • low Secrets in code secret-high-entropy-token src/services/storyGenerator.js:10
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    'AIza…chM'
    quoted

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

Against the Agent Skills spec

  • warning description-long-hermes description is 138 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "requires"

Process rating: all ten parameters 61/100

  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 38 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1034 tokens
  • 100Running it twice. No mutating operations
  • low 10 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
  • -2localhost URLs: will not work for another user
  • +2Single-language instructions
  • +3Description length 138: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 38 items
  • +4Has examples (5 code blocks)
  • +3All 2 scripts are documented
  • +1License stated

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

External checks

ClawHub: suspicious
This appears to be a real AI life-simulator backend, but it has serious security and privacy flaws before it should be installed or hosted.
LLM: suspicious (high) · VirusTotal: suspicious · 10 Sept 2026