material

Google's Material Design with layered surfaces, dynamic theming, built-in motion, and responsive cross-platform patterns.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/material/SKILL.md

Quality

Content

85%

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

The body is a well-structured, actionable design-system authoring guide with concrete tokens, a clear sequenced workflow, and QA checkpoints. Its only weakness is mild over-explanation in the 'Brand' section; trimming that paragraph toward instruction would lift conciseness to a 3.

Dimension	Reasoning	Score
Conciseness	Mostly lean with well-organized bullet sections and no padding, but the 'Brand' paragraph ('UX (user experience) designers use it to create visually consistent, intuitive, and responsive digital experiences...') explains what Material is rather than instructing — some unnecessary explanation prevents a 3.	2 / 3
Actionability	Concrete, applicable guidance throughout: exact token values (#6442D6), typography/spacing scales, enumerated required component states, and a prescriptive 'must'/'should' constraint language — copy-paste-ready specifics for an instruction-only skill.	3 / 3
Workflow Clarity	The 6-step 'Guideline Authoring Workflow' is clearly sequenced and reinforced by a 'Quality Gates' section and a QA checklist acting as checkpoints; this is a generation task (not destructive/batch), so absent validate-fix-retry loops are not penalized.	3 / 3
Progressive Disclosure	A self-contained SKILL.md with no external references needed, organized into clearly labeled sections (Foundations, Workflow, Output Structure, Quality Gates); well-organized single-file structure with easy navigation warrants a 3.	3 / 3
	Total	11 / 12 Passed

Description

57%

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, distinct Material Design niche with concrete features, but lacks an explicit 'Use when...' trigger clause and concrete action verbs, leaving the 'when' only implied. Adding third-person action verbs and natural trigger phrases would raise specificity, trigger quality, and completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when applying Material Design, building Material-themed UIs, or when the user mentions Material, M3, or Material You.'

Rewrite as third-person actions rather than a noun phrase, e.g. 'Applies Google's Material Design with layered surfaces, dynamic theming, built-in motion, and responsive cross-platform patterns.'

Include natural user-facing variations ('Material Design', 'Material 3', 'M3', 'Material You') alongside the technical feature terms.

Dimension	Reasoning	Score
Specificity	Quotes 'layered surfaces, dynamic theming, built-in motion, and responsive cross-platform patterns' name concrete features of the Material domain, but the description is a noun phrase with no verb describing an action Claude performs, so it is not comprehensive concrete actions.	2 / 3
Completeness	The 'what' is stated (Material Design system with named features) but there is no 'Use when...' or equivalent explicit trigger guidance, so 'when' is only implied — capping completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Natural terms like 'Material Design', 'theming', and 'responsive' appear, but common variations users might say (e.g. 'Material 3', 'M3', 'Material You') are missing, and 'layered surfaces' / 'built-in motion' lean technical.	2 / 3
Distinctiveness Conflict Risk	The Material Design niche with named tokens (e.g. 'dynamic theming', 'cross-platform patterns') is a clear, distinct domain unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: bergside/awesome-design-skills
Path: skills/material/SKILL.md
Commit: f631a09

Reviewed: 1 day 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.