SKILLEMALL.ai
RU Sign in

CC evomap-node-integration

Integrate OpenClaw with EvoMap Hub for node registration, heartbeat, asset publishing (Gene/Capsule/Event), bounty claiming, and evolution asset management. Use when: (1) registering a new node with EvoMap Hub, (2) setting up persistent heartbeat without OpenClaw cron tool, (3) publishing Genes/Capsules/Events to the EvoMap asset market, (4) claiming and completing bounty tasks, (5) managing evolution assets (genes, capsules, events). Triggers on: EvoMap, node registration, heartbeat, asset publishing, bounty, GDI score, evolution assets.

Not recommendedcritical or high security findings
ClawHub Agent Skills author: Jokerli530 v1.0.0 MIT-0 5 files body ≈ 1 645 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

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

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
C
69/100
safety, quality, tests
Safety 60%
67
Quality 40%
73
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
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.
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 SKILL.md:66
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load ~/Library/LaunchAgents/ai.openclaw.evomap-heartbeat.plist
Medium and low: 3
  • medium Dangerous commands cmd-persistence references/examples.md:47
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (test fixture / example file)
    cat > ~/Library/LaunchAgents/ai.openclaw.evomap-heartbeat.plist << 'EOF'
    fixture
  • medium Dangerous commands cmd-persistence references/examples.md:67
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (test fixture / example file)
    launchctl load ~/Library/LaunchAgents/ai.openclaw.evomap-heartbeat.plist
    fixture
  • medium Dangerous commands cmd-persistence SKILL.md:45
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    **2. Create plist** at `~/Library/LaunchAgents/ai.openclaw.evomap-heartbeat.plist`:
    quoted

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

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Integrate OpenClaw with EvoMap Hub for node registration, heartbea… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value

Process rating: all ten parameters 54/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 9 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, python, node) that frontmatter does not declare
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 8 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1645 tokens

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
  • -41 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +3Description length 544: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 8 items
  • +4Has examples (12 code blocks)
  • +3All 2 scripts are documented

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

External checks

ClawHub: suspicious
This EvoMap integration is mostly coherent, but it needs review because it tells users to store secrets insecurely and set up an always-on authenticated background heartbeat without enough lifecycle controls.
LLM: suspicious (high) · VirusTotal: · 29 May 2026