SKILLEMALL.ai
GitHub ↗ RU Sign in

CF html-view

Create or revise live .univer.html pages backed by existing Workspace Sheet data using HTML bindings and JavaScript. Validate sources and publish pages with uvw html-view; revise existing pages through the Blob workflow.

dream-num/univer-workspace Agent Skills author: dream-num 5 files body ≈ 1 082 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Create or revise live .univer.html pages backed by existing Workspace Sheet data using HTML bindings and JavaScript. Validate sources and publish pages with…

As a process F 33/100 · No process to follow — weak spots: steps, result and completion, when it triggers

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
F
33/100
No process to follow
Steps w 15
0
Result and completion w 14
0
Inputs and preconditions w 11
0
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 description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 33/100

  • 0Steps. Prose only: no discrete steps
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 7 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1082 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)
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 220: enough signal without eating the budget
  • +4Structure: 5 headings
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (1 of 4)

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