SKILLEMALL.ai
GitHub ↗ RU Sign in

CC status-page-gen

Generate a lightweight static HTML status page for self-hosted services. Checks health endpoints, ping, SSL certificates, and uptime history. Outputs a self-contained dark-theme HTML file (Upptime/Cachet-style) that can be served locally or pushed to a GitHub Gist. Triggers on: status page, service status, uptime, are my services up, health check, service monitor, generate status page, check my services.

Not recommendedcritical or high security findings
ClawHub Agent Skills author: New Age Investments v1.0.0 MIT-0 8 files body ≈ 652 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 50/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

GeneratorGitHubInfrastructuretype 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
73/100
safety, quality, tests
Safety 60%
75
Quality 40%
69
Run on models
none yet
Process rating
C
50/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

The same skill appears in 1 more place: ClawHub

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

  • high Dangerous commands cmd-persistence references/setup-guide.md:132
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load ~/Library/LaunchAgents/com.statuspage.check.plist
Medium and low: 3
  • medium Dangerous commands cmd-persistence references/setup-guide.md:110
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    Alternatively, use a macOS LaunchAgent for more reliable scheduling. Create `~/Library/LaunchAgents/com.statuspage.check.plist`:
    quoted
  • low Dangerous commands cmd-cron-mention references/setup-guide.md:95
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention SKILL.md:46
    Mentions editing / listing crontab (quoted — discussed, not commanded)
    Add to crontab (`crontab -e`):
    quoted

Files scanned: 8. 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: Generate a lightweight static HTML status page for self-hosted ser… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 50/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
  • 30Running it twice. 3 mutating operations with no state check
  • 40Consistency. Frontmatter name (status-page-gen) differs from the folder (nai-status-page-gen)
  • 70When it triggers. States when to use, but not when not to
  • 75Steps. 3 steps
  • 100Tools and files. No external tools needed
  • 100Execution cost. Instruction body is 652 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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 407: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 3 items
  • +4Has examples (4 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 4 scripts are documented

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

External checks

ClawHub: clean
This skill does what it claims: it checks user-configured services and generates a local status page, with optional scheduling and public publishing steps.
LLM: benign (high) · VirusTotal: · 29 May 2026