CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

58

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/design-taste-frontend/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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.

The body is exceptionally actionable and workflow-driven, with executable code skeletons and a rigorous mechanical pre-flight checklist, but it is a monolithic 79KB document that buries its novel rules in padding: known-concept vocabulary lists, textbook CSS explanations, and vendored appendices that should live in separate reference files. Splitting reference material out and trimming known-concept content would sharply improve token efficiency and navigability.

Suggestions

Move the appendices (install commands, canonical URL lists, Liquid Glass approximation) and the Section 10 pattern vocabulary into separate files under references/ with one-level-deep, clearly signaled links from SKILL.md.

Cut or compress explanations of concepts Claude already knows (e.g., what prefers-reduced-motion/backdrop-filter do, generic pattern-name listings) and keep only the opinionated rules and thresholds that are novel.

Trim the Section 14 checklist by removing entries that duplicate Section 9 rules verbatim and grouping the remaining checks by phase, so the pre-flight gate stays mechanical but shorter.

DimensionReasoningScore

Conciseness

The ~1,100-line body is noticeably verbose: a 60-entry pattern-name vocabulary Claude already knows (Section 10), appendices of install commands and canonical URL lists, and textbook explanations of CSS features like prefers-reduced-motion. The core dial/AI-tells guidance is novel, so it is not pure known-concept padding, but there are several heavily padded sections that should be cut or split out.

2 / 5

Actionability

Guidance is fully executable: copy-paste GSAP/Motion component skeletons (Sections 5.A-5.C), exact Tailwind classes and thresholds ('min-h-[100dvh]', 'pt-24', 'text-4xl md:text-6xl'), concrete URLs ('https://cdn.simpleicons.org/{slug}/ffffff'), install commands, and mechanical checks like counting 'uppercase tracking' instances against ceil(sectionCount / 3).

5 / 5

Workflow Clarity

The workflow is clearly sequenced (Section 0 brief inference and one-line Design Read, Section 1 dial setting, Section 2 system choice, Section 11 redesign-mode detection with audit, Section 14 pre-flight gate) with an explicit final validation checklist, mechanical pass/fail checks, and 'Common failure -> Fix:' error-recovery loops for sticky-stack and horizontal-pan patterns.

5 / 5

Progressive Disclosure

The file has strong section structure but no bundle files at all; hundreds of lines that clearly belong in separate reference files (Appendix A install commands, Appendix B canonical URL lists, Appendix C Liquid Glass CSS, Section 10 vocabulary) are inlined in the monolithic SKILL.md. This fits 'some structure, but content that should be separate is inline' rather than the minimal-structure anchor.

3 / 5

Total

15

/

20

Passed

Description

66%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.

The description communicates a clear, fairly distinct niche with several concrete actions, but lacks any explicit 'Use when...' trigger clause, leaving the 'when' only weakly implied and missing natural synonyms like 'website' or 'marketing site'. Adding an explicit trigger sentence would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when building or redesigning landing pages, portfolios, marketing sites, or brand websites' to convert the weakly implied trigger into a concrete one.

Include natural user synonyms such as 'website', 'marketing site', 'homepage', and 'make it not look AI-generated' alongside 'landing pages, portfolios, and redesigns'.

State the exclusion boundary in the description (e.g. 'Not for dashboards, data tables, or dense product UI') to sharpen distinctiveness against generic frontend skills.

DimensionReasoningScore

Specificity

Lists several concrete actions ('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'), with minor coverage gaps (typography, motion, accessibility work unmentioned), matching the 'several specific actions; minor gaps' anchor.

4 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance; the trigger is only weakly implied by 'for landing pages, portfolios, and redesigns', which caps completeness at 3 per the judging guideline.

3 / 5

Trigger Term Quality

'landing pages, portfolios, and redesigns' are natural phrases users would say, but common synonyms and variations ('website', 'marketing site', 'homepage', 'not look AI-generated') are missing, so keyword coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Anti-slop frontend skill for landing pages, portfolios, and redesigns' carves a mostly distinct niche with distinctive vocabulary, but the exclusion boundary (e.g., not dashboards) is absent, leaving minor overlap risk with generic frontend/web-design skills.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1104 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

simstudioai/sim

Path

.agents/skills/design-taste-frontend/SKILL.md

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.