corporate

Professional, brand-aligned design with structured grids, minimalist layouts, and consistent enterprise patterns.

Quality

62%

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/corporate/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 lean, well-structured instruction skill with concrete tokens, a sequenced authoring workflow, and explicit quality gates. Its main gap is the absence of a worked example showing the expected authored output.

Suggestions

Add one short worked example of an authored component rule (anatomy, states, token usage, accessibility acceptance criteria) to make the output structure concrete and copy-paste ready.

Show the "must/should + paired do/don't" constraint language applied to a real example instead of only describing it abstractly.

Tighten the mild redundancy between "Rules: Do/Don't", "Expected Behavior", and "Quality Gates" by consolidating overlapping guidance.

Dimension	Reasoning	Score
Conciseness	The body is dense and terse with no padding of concepts Claude already knows (no "what is a design system" preamble); each line is a concrete rule or token, and every token earns its place despite minor overlap between Rules/Expected Behavior/Quality Gates.	3 / 3
Actionability	It supplies concrete tokens (hex colors, font names/weights, 8pt spacing), required states, and a required output structure, but it never shows a worked example of an authored component guideline or an example of the constraint language in use, leaving the guidance instructive rather than copy-paste ready.	2 / 3
Workflow Clarity	A clearly sequenced 6-step Guideline Authoring Workflow is paired with explicit Quality Gates acting as validation checkpoints and a required QA checklist, satisfying the anchor for clear sequence with validation steps and a checklist.	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the single self-contained file is organized into well-labeled sections (Brand, Style Foundations, Accessibility, Rules, Workflow, Output Structure, Quality Gates) with no nested references, which earns a 3 for a self-contained skill.	3 / 3
	Total	11 / 12 Passed

Description

40%

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 reads as a style descriptor rather than a capability statement: it lists aesthetic qualities but no actions and no explicit use-when guidance. It is recognizable but underspecified as a trigger for Claude.

Suggestions

Rewrite in third-person action voice naming what the skill does, e.g. "Authors enterprise design-system guidelines with token-driven rules, component states, and accessibility acceptance criteria."

Add an explicit trigger clause: "Use when creating or reviewing corporate/enterprise UI guidelines, brand-aligned design tokens, or component rule sets."

Include natural user phrasing such as "corporate", "enterprise UI", "on-brand", and "design tokens" to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	The description is a string of descriptive adjectives ("Professional, brand-aligned design with structured grids, minimalist layouts, and consistent enterprise patterns") and names no concrete actions or verbs the skill performs, matching the "no actions; abstract language" anchor.	1 / 3
Completeness	It conveys a domain (what aesthetic the skill targets) but never states what the skill actually does (author design-system guidelines) and has no "Use when..." clause, so per the rubric it is capped at 2 with only an implied, weak "what" and no explicit "when".	2 / 3
Trigger Term Quality	Terms like "brand-aligned design", "professional", and "enterprise patterns" are plausible user phrases, but they are not framed as triggers and common variations (e.g. "corporate", "enterprise UI", "make it look on-brand") are missing.	2 / 3
Distinctiveness Conflict Risk	The enterprise/brand-aligned framing gives it a recognizable niche, but with no distinct triggers it could overlap with other general design or brand-styling skills.	2 / 3
	Total	7 / 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/corporate/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.