SKILLEMALL.ai
RU Sign in

FC system-restoration

Restore Advantage HPE operational intelligence systems. Use when systems are down, missing alerts, broken scheduling, or data source issues. Covers LaunchD services, cron jobs, API fixes, and service restoration for zero revenue alerts, morning pulse, live nudges, and material truth reports.

Not recommendedcritical or high security findings · low grade F
ClawHub Agent Skills author: stephen550 v1.0.0 MIT-0 7 files body ≈ 1 556 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process C 54/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

IntegrationSlackInfrastructureData and analyticstype 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
F
36/100
safety, quality, tests
Safety 60%
0
Quality 40%
90
Run on models
none yet
Process rating
C
54/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
When it triggers w 12
20
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 · 13

  • high Dangerous commands cmd-persistence references/launchd-service-templates.md:109
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load ~/Library/LaunchAgents/com.ranger.SERVICENAME.plist
  • high Dangerous commands cmd-persistence references/launchd-service-templates.md:112
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl unload ~/Library/LaunchAgents/com.ranger.SERVICENAME.plist
  • high Dangerous commands cmd-persistence SKILL.md:141
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load /Users/stephendobbins/Library/LaunchAgents/com.ranger.<service>.plist
Medium and low: 10
  • medium Dangerous commands cmd-persistence references/troubleshooting-checklist.md:38
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)
    - [ ] LaunchD plist: `/Users/stephendobbins/Library/LaunchAgents/com.ranger.margin-alerts.plist`
    detector
  • medium Dangerous commands cmd-persistence references/troubleshooting-checklist.md:43
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)
    - [ ] Load service: `launchctl load ~/Library/LaunchAgents/com.ranger.margin-alerts.plist`
    detector
  • medium Dangerous commands cmd-persistence references/troubleshooting-checklist.md:59
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    - [ ] LaunchD plist: `/Users/stephendobbins/Library/LaunchAgents/com.ranger.morning-pulse.plist`
    quoted
  • medium Dangerous commands cmd-persistence references/troubleshooting-checklist.md:70
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)
    - [ ] Load service: `launchctl load ~/Library/LaunchAgents/com.ranger.morning-pulse.plist`
    detector
  • medium Dangerous commands cmd-persistence references/troubleshooting-checklist.md:91
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    - [ ] Load service: `launchctl load ~/Library/LaunchAgents/com.ranger.live-nudges.plist`
    quoted
  • medium Dangerous commands cmd-persistence scripts/create-live-nudges-service.py:50
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)
    print(f"launchctl load {plist_file}")
    code literal
  • medium Dangerous commands cmd-persistence SKILL.md:45
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    - `/Users/stephendobbins/Library/LaunchAgents/` - LaunchD service definitions
    quoted
  • medium Dangerous commands cmd-persistence SKILL.md:63
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    2. Load LaunchD service: `launchctl load /Users/stephendobbins/Library/LaunchAgents/com.ranger.margin-alerts.plist`
    quoted
  • medium Dangerous commands cmd-persistence SKILL.md:77
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)
    4. Load LaunchD service: `launchctl load /Users/stephendobbins/Library/LaunchAgents/com.ranger.morning-pulse.plist`
    detector
  • medium Dangerous commands cmd-persistence SKILL.md:92
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    3. Load service: `launchctl load /Users/stephendobbins/Library/LaunchAgents/com.ranger.live-nudges.plist`
    quoted

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

Against the Agent Skills spec

✓ No remarks against the Agent Skills spec

Process rating: all ten parameters 54/100

  • 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
  • 30Running it twice. 5 mutating operations with no state check
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 49 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1556 tokens
  • 100Progress reporting. Reports progress

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)
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • +1No license
  • +2Single-language instructions
  • +3Description length 292: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 49 items
  • +3Output format is stated explicitly
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)
  • +3All 2 scripts are documented

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

External checks

ClawHub: suspicious
This looks like a real restoration runbook, but it can re-enable persistent automations, change production scripts, point to a Slack token location, and includes a data-source helper that returns mock operational data.
LLM: suspicious (high) · VirusTotal: · 29 May 2026