CtrlK
BlogDocsLog inGet started
Tessl Logo

audit-ai-design-slop

Audit websites, apps, screenshots, mockups, and design code for harmful AI-design clichés, generic generated defaults, and established UI defects. Use when the user wants evidence-backed design feedback, an anti-slop review, or a removal-first cleanup plan without a speculative redesign.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An instruction-only audit skill that is lean, highly actionable, and well-sequenced with a per-finding validation gate and a concrete output template. Structure is clean with a single appropriately signaled external reference, so all dimensions score at the top of the scale.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it lists flag categories, a removal test, priorities, and an output template without explaining what gradients, cards, or glass effects are. Every section earns its place with no padding.

5 / 5

Actionability

Concrete, specific guidance throughout: enumerated flag patterns ("card treatment applied to nearly every content block", "unclear or competing primary actions"), a five-step Removal Test, a defined P0–P3 priority scheme, and a copy-paste-ready output template with a worked table row.

5 / 5

Workflow Clarity

Clear sequenced audit process (Audit the Evidence → Classify → What to Flag → Removal Test → Prioritize → Output) with the Removal Test acting as an explicit per-finding validation gate and the "Mark anything outside ... evidence as unknown" checkpoint plus an Unknowns output section.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with a single, well-signaled one-level-deep reference ("read [../no-ai-design-slop/ARTICLE.md] and use only the catalog sections relevant to the inspected artifact") and no nested references.

5 / 5

Total

20

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states what the skill does and when to use it with concrete trigger phrases. Coverage of actions and artifact types is comprehensive; only trigger-term synonyms and a slight overlap with generic design feedback keep it just short of a perfect score.

DimensionReasoningScore

Specificity

Names multiple concrete audit actions across distinct artifact types ("Audit websites, apps, screenshots, mockups, and design code") and three defect classes ("AI-design clichés, generic generated defaults, and established UI defects"), giving comprehensive coverage rather than a few actions.

5 / 5

Completeness

Explicitly answers both what ("Audit ... for harmful AI-design clichés, generic generated defaults, and established UI defects") and when ("Use when the user wants evidence-backed design feedback, an anti-slop review, or a removal-first cleanup plan") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ("evidence-backed design feedback", "an anti-slop review", "a removal-first cleanup plan"), but a few common variants like "UI review" or "design critique" are absent.

4 / 5

Distinctiveness Conflict Risk

The "anti-slop review" and "removal-first cleanup plan without a speculative redesign" niche is distinct, but the broad trigger "design feedback" creates minor overlap risk with general design-critique skills.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
MengTo/Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.