SKILLEMALL.ai
GitHub ↗ RU Sign in

AC sheet-to-doc-skill

Generate Word documents from Word templates and JSON data. Supports basic placeholder replacement ({field} format) and placeholder extraction for data validation. Best for batch-generating contracts, invitations, certificates, and mail-merge style docs.

ClawHub Agent Skills author: WTSolutions v1.0.0 MIT-0 7 files body ≈ 4 104 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

Generate Word documents from Word templates and JSON data.

As a process C 63/100 · Has gaps — weak spots: when it triggers, progress reporting

TemplateWordSoftware developmenttype 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
A
90/100
safety, quality, tests
Safety 60%
99
Quality 40%
76
Run on models
none yet
Process rating
C
63/100
Has gaps
Progress reporting w 2
0
When it triggers w 12
20
Failures and branches w 10
50
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-high-entropy-token package-lock.json:40
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "integrity": "sha5…6RP/5q+TO2O…jJE+uu/PkpChs+NIZSSzbBoD+6kji…1dz/w==",
    quoted

Files scanned: 7. 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")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 63/100

  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4104 tokens
  • 85Steps. 53 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • low 14 top-level sections: this looks like several domains in one skill

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)
  • -221 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +3Description length 253: enough signal without eating the budget
  • +4Structure: 33 headings
  • +3Step-by-step instructions: 53 items
  • +3Output format is stated explicitly
  • +4Has examples (24 code blocks)
  • +3All 1 scripts are documented
  • +1License stated

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

External checks

ClawHub: clean
This skill does what it says, but generated documents include forced Sheet-to-Doc branding and can overwrite the chosen output file.
LLM: benign (high) · VirusTotal: · 21 Jul 2026