emil-design-eng

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

2.16x

Quality

58%

Does it follow best practices?

Impact

91%

2.16x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/emil-design-eng/SKILL.md

Quality

Content

71%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 content is a highly actionable, code-rich reference with a well-sequenced animation decision framework and a concrete review checklist; its main weaknesses are a motivational philosophy section that pads the token budget and a monolithic structure with no progressive disclosure to separate reference files.

Suggestions

Trim or collapse the "Core Philosophy" section and scattered motivational asides ("Beauty is leverage", the Paul Graham quote, "Cohesion matters") to the one or two sentences that actually guide behavior.

Move the longer reference material (CSS Transform Mastery, clip-pattern catalog, Spring configuration) into bundled reference files (e.g. references/transforms.md, references/clip-path.md) with one-level-deep links from SKILL.md.

Add a validate-then-proceed checkpoint to the Review Format workflow (e.g., re-run the Review Checklist and confirm every row is addressed before finishing) to push workflow clarity toward the top anchor.

Dimension	Reasoning	Score
Conciseness	The technical bulk (decision-framework tables, CSS/JS/JSX snippets, checklist) is efficient and earns its place, but the dedicated "Core Philosophy" section plus motivational prose ("You are a design engineer with the craft sensibility...", "Beauty is leverage", the Paul Graham quote, "Cohesion matters") is unnecessary padding Claude does not need; this fits anchor 3 (mostly efficient, some unnecessary explanation) rather than 4 whose over-explanation is only minor.	3 / 5
Actionability	The body is dense with copy-paste-ready, executable code (exact cubic-bezier curves, scale(0.97) on :active, clip-path insets, WAAPI calls, Framer Motion transform strings) plus concrete Before/After/Why and Issue/Fix tables covering the common UI-animation cases, matching anchor 5 for fully executable guidance.	5 / 5
Workflow Clarity	The Animation Decision Framework is an explicit in-order sequence (Should it animate? Purpose? Easing? Speed?) and the Review Checklist plus Debugging Animations section provide a feedback loop for finding and fixing issues; it stops short of anchor 5 because there is no hard validate-then-proceed gating, only sequenced decisions and a review checklist.	4 / 5
Progressive Disclosure	There are no bundle files and the skill is a single 675-line monolith with no references to separate files, so substantial reference material (CSS Transform Mastery, clip-path patterns, Spring configuration) is inlined that could be split out; internal section headers are well organized, keeping it above anchor 2, but the absence of any cross-file disclosure for a lengthy reference skill fits anchor 3 (some structure, content that could be separate is inline).	3 / 5
	Total	15 / 20 Passed

Description

45%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 names a clear domain and a specific source (Emil Kowalski) but frames the skill abstractly as an encoding of philosophy rather than concrete actions, and omits any "Use when..." trigger guidance. This yields mid-range scores across specificity, completeness, and trigger quality.

Suggestions

Lead with concrete actions in third person (e.g., "Reviews UI code for animation polish and prescribes transition, easing, and transform fixes") instead of the abstract "encodes philosophy".

Add an explicit trigger clause such as "Use when reviewing or refining UI animations, transitions, microinteractions, or component motion".

Include natural synonyms users say ("microinteractions", "transitions", "Framer Motion", "hover/press states") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names several domains ("UI polish, component design, animation decisions") but the only action verb is the abstract "encodes Emil Kowalski's philosophy" rather than a concrete task, matching the anchor that names the domain with minimal/generic actions and falling short of anchor 3 which requires 1-2 concrete actions.	2 / 5
Completeness	It states a "what" (encodes philosophy on UI polish/component design/animation) but provides no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3; it is not a 4 because the "when" is entirely absent rather than merely weak.	3 / 5
Trigger Term Quality	"UI polish", "component design", and "animation" are relevant natural terms, but the framing leans conceptual ("philosophy", "invisible details", "feel great") rather than the phrases a user would actually say when invoking the skill, missing common variations and synonyms; this fits anchor 3 (some relevant keywords, missing variations) better than the broad coverage of anchor 4.	3 / 5
Distinctiveness Conflict Risk	The attribution to "Emil Kowalski's philosophy" and the focused UI/animation domain give it some distinctiveness, but "UI polish, component design, animation" is broad enough to overlap with general frontend/UI skills and the absence of trigger phrases leaves it only somewhat specific, matching anchor 3.	3 / 5
	Total	11 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (675 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: emilkowalski/skills
Path: skills/emil-design-eng/SKILL.md
Commit: 78761e1

Reviewed: about 17 hours ago

Table of Contents

Discovery Implementation Validation

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.