SKILLEMALL.ai
RU Sign in

DF openbotauth

(no description)

Not recommendedlow grade D
ClawHub Agent Skills author: hammadtq v0.1.1 2 files body ≈ 6 583 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process F 52/100 · Will not run — References files that are not bundled: [a-zA-Z0-9-]{0,61}[a-zA-Z0-9]

ProcedureInfrastructuretype 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
D
59/100
safety, quality, tests
Safety 60%
99
Quality 40%
0
Run on models
none yet
Process rating
F
52/100
Will not run
References files that are not bundled: [a-zA-Z0-9-]{0,61}[a-zA-Z0-9]
Tools and files w 18
0
Result and completion w 14
0
When it triggers w 12
30
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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. 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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-private-key SKILL.md:38
    Private key material (placeholder value)
    "privateKeyPem": "-----BEGIN PRIVATE KEY----- …
    placeholder

Files scanned: 2. 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 body-long SKILL.md body ≈ 6583 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: [a-zA-Z0-9-]{0,61}[a-zA-Z0-9]

Process rating: all ten parameters 52/100

Will not run. References files that are not bundled: [a-zA-Z0-9-]{0,61}[a-zA-Z0-9]
  • 0Tools and files. 1 referenced file(s) missing: [a-zA-Z0-9-]{0,61}[a-zA-Z0-9]
  • 0Result and completion. Does not say what the result is
  • 30When it triggers. No condition that starts the skill
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Failures and branches. 4 branches
  • 70Execution cost. Instruction body is 6583 tokens
  • 100Steps. 50 steps
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +4Structure: 30 headings
  • +3Step-by-step instructions: 50 items
  • +4Has examples (16 code blocks)

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

External checks

ClawHub: suspicious
Review is recommended because the skill is mostly disclosed and purpose-related, but its browser proxy grants broad signing and HTTPS interception power without enough scoping or client authorization.
LLM: suspicious (high) · VirusTotal: suspicious · 10 Sept 2026