SKILLEMALL.ai

CC design-taste-frontend

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

simstudioai/sim Agent Skills author: simstudioai Apache-2.0 1 file body ≈ 19 796 tokens Open the sourcegithub.com↗ analyzed 11 h ago

Anti-slop frontend skill for landing pages, portfolios, and redesigns.

As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, execution cost

AnalyzerDesignSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
68
Run on models
none yet
Process rating
C
55/100
Has gaps
Result and completion w 14
0
Execution cost w 6
10
Inputs and preconditions w 11
30
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 19796 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "source"

Process rating: all ten parameters 55/100

  • 0Result and completion. Does not say what the result is
  • 10Execution cost. Instruction body is 19796 tokens: crowds the task out of the window
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 16 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 85Steps. 443 steps, 3 vague phrases
  • 100Failures and branches. 7 branches, has a failure section
  • 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 17 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (3 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)
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 269: enough signal without eating the budget
  • +4Structure: 101 headings
  • +3Step-by-step instructions: 443 items
  • +4Has examples (5 code blocks)

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