SKILLEMALL.ai

BB report-with-html

Produces the reader-facing HTML artifact — report, dashboard, architecture view, data browser, or review workbench — evidence-backed, browser-verified. Use when the deliverable IS a visual HTML report, or the user asks for an HTML/web presentation. Load data-visualization-discipline for chart judgment. Not for chat status or Markdown prose unless asked to become a report; not for PowerPoint (deck-creator Route C).

daymade/claude-code-skills Agent Skills author: daymade MIT 28 files · 6 scripts body ≈ 11 549 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Produces the reader-facing HTML artifact — report, dashboard, architecture view, data browser, or review workbench — evidence-backed, browser-verified.

As a process B 71/100 · Nearly there — weak spots: result and completion, execution cost, running it twice

GeneratorPowerPointData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
99
Quality 40%
79
Run on models
none yet
Process rating
B
71/100
Nearly there
Running it twice w 4
30
Result and completion w 14
40
Execution cost w 6
40
the three weakest of ten parameters · all ten

How to improve

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

✓ No critical or high findings

Medium and low: 1
  • low Risky intent intent-offensive-security references/audience-triage.md:236
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    ([Praetorian, *Red Team vs. Blue Team vs. Purple Team*](https://www.praetorian.com/secu…101/red-team-vs-blue-team-vs-purple-team/)),

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 11549 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 71/100

  • 30Running it twice. 19 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 40Execution cost. Instruction body is 11549 tokens: crowds the task out of the window
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 65Failures and branches. 3 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 56 steps
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (6 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
  • +3Output format is not stated: the model decides each time
  • -31 of 5 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 417: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 56 items
  • +4Has examples (7 code blocks)
  • +4Reference files are cited in the instructions (11 of 11)

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