SKILLEMALL.ai
GitHub ↗ RU Sign in

BC Web Page Rendered HTML Content API

Call GET /api/web/rendered-html/v1 for Web Page Rendered HTML Content through JustOneAPI with url.

ClawHub Agent Skills author: justoneapi v1.0.0 MIT-0 5 files body ≈ 586 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 60/100 · Has gaps — weak spots: when it triggers, consistency, 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
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
C
60/100
Has gaps
Progress reporting w 2
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. 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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 60/100

  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 40Consistency. Frontmatter name (Web Page Rendered HTML Content API) differs from the folder (justoneapi-web-rendered-html)
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 13 steps
  • 100Execution cost. Instruction body is 586 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 98: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 13 items
  • +3Output format is stated explicitly
  • +4Has examples (1 code blocks)

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

External checks

ClawHub: suspicious
The skill appears to call the promised JustOneAPI rendered-HTML endpoint, but it handles the API token and user-supplied URLs in ways users should review before installing.
LLM: suspicious (high) · VirusTotal: · 29 May 2026