SKILLEMALL.ai
GitHub ↗ RU Sign in

BD yasim-xml

Provide a detailed specification for writing YASim XML files.

ClawHub Agent Skills author: container32 v1.0.0 MIT-0 2 files body ≈ 11 506 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

Provide a detailed specification for writing YASim XML files.

As a process D 47/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorWriting and documentsSoftware developmentData and analyticstype 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
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
59
Run on models
none yet
Process rating
D
47/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
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.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 2. 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")
  • warning body-long SKILL.md body ≈ 11506 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 47/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 40Execution cost. Instruction body is 11506 tokens: crowds the task out of the window
  • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
  • 70Failures and branches. 4 branches
  • 85Steps. 246 steps, 3 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • low 13 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (19 tags): a typed call is more reliable

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 61: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 41 headings
  • +3Step-by-step instructions: 246 items
  • +4Has examples (8 code blocks)

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

External checks

ClawHub: clean
This skill is a passive reference guide for writing YASim XML files and does not ask for system access, credentials, networking, persistence, or code execution.
LLM: benign (high) · VirusTotal: · 9 Sept 2026