SKILLEMALL.ai

BB frontend-visual-qa

Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI implementation to find typography, overflow, responsive, routing, data-viz, browser-output, or native-shell defects, or to compare a render against a reference. Not for greenfield UI design (use ui-designer) or QA-program setup (use qa-expert).

daymade/claude-code-skills Agent Skills author: daymade MIT 45 files · 14 scripts body ≈ 9 045 tokens Open the sourcegithub.com↗ analyzed 33 h ago

Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone.

As a process B 70/100 · Nearly there — weak spots: result and completion, execution cost

AnalyzerObsidianPlaywrightSoftware developmentData and analyticsDesigntype and topics are labelled automatically from the skill text
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
77
Run on models
none yet
Process rating
B
70/100
Nearly there
Result and completion w 14
40
Execution cost w 6
40
When it triggers w 12
50
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
  • 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: 19. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

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

Process rating: all ten parameters 70/100

  • 40Result and completion. Does not say what the result is
  • 40Execution cost. Instruction body is 9045 tokens: crowds the task out of the window
  • 50When 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
  • 100Steps. 76 steps
  • 100Inputs and preconditions. Inputs and preconditions are listed
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 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 (12 tags): a typed call is more reliable
  • low No test case covers injection arriving through data

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
  • -2localhost URLs: will not work for another user
  • -31 of 6 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 555: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 76 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (10 of 11)

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