SKILLEMALL.ai
GitHub ↗ RU Sign in

CF github-release-watcher

(no description)

ClawHub Agent Skills author: rogue-agent1 v1.0.0 MIT-0 5 files · 1 script body ≈ 270 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 39/100 · Will not run — References files that are not bundled: scripts/.last_seen.json

ReferenceGitHubInfrastructuretype 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
60/100
safety, quality, tests
Safety 60%
100
Quality 40%
0
Run on models
none yet
Process rating
F
39/100
Will not run
References files that are not bundled: scripts/.last_seen.json
Tools and files w 18
0
When it triggers w 12
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
  2. The text references files that are not there: add them or drop the references.
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • error frontmatter SKILL.md: no YAML frontmatter block found
  • error name-missing SKILL.md: frontmatter has no `name`
  • error description-missing SKILL.md: no `description` — the skill can never trigger
  • warning missing-ref reference to a missing file: scripts/.last_seen.json

Process rating: all ten parameters 39/100

Will not run. References files that are not bundled: scripts/.last_seen.json
  • 0Tools and files. 1 referenced file(s) missing: scripts/.last_seen.json
  • 0When it triggers. No condition that starts the skill
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 4 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 270 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)
  • +3Description length 0: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 4 items
  • +3Output format is stated explicitly
  • +4Has examples (3 code blocks)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
This skill mostly does what it claims, but its release-check script can execute local Python code if a watched repository publishes a specially crafted release tag.
LLM: suspicious (high) · VirusTotal: · 29 May 2026