dramatic

High-contrast, theatrical design with bold layouts, immersive visuals, and unconventional compositions that command attention.

Quality

67%

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/dramatic/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.

A well-structured, actionable instruction-only skill that gives concrete tokens, scales, states, and a clear authoring workflow with validation gates. Its main weakness is mild redundancy across the workflow, output-structure, and component-rules sections that could be consolidated.

Suggestions

Consolidate the overlapping Guideline Authoring Workflow, Required Output Structure, and Component Rule Expectations sections to remove redundancy and tighten the body.

Trim generic filler statements such as 'Follow the foundations first, then component consistency' that do not add concrete guidance.

Add one worked example of an authored component guideline so the expected output is concrete and copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean bullet-list guidance with no concept-explaining fluff, but the Guideline Authoring Workflow, Required Output Structure, and Component Rule Expectations sections overlap, and lines like 'Follow the foundations first, then component consistency' could be tightened.	2 / 3
Actionability	It supplies exact design tokens (primary=#8B5CF6, surface=#09090B), a concrete typography scale (12/14/16/20/24/32), required component states (default, hover, focus-visible, active, disabled, loading, error), a 6-step workflow, and a fixed output structure — directly usable, specific guidance rather than vague direction.	3 / 3
Workflow Clarity	The Guideline Authoring Workflow gives a clearly sequenced 6-step process with explicit validation via the QA checklist step and the testable Quality Gates section, so checkpoints are present and signaled rather than missing.	3 / 3
Progressive Disclosure	This is a single-purpose, self-contained guideline-authoring skill with no external references needed; it is organized into clearly headed sections with easy navigation and no nested references or misplaced inline reference material.	3 / 3
	Total	11 / 12 Passed

Description

50%

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 characterizes a specific design aesthetic but is purely descriptive — it states no concrete actions and omits any 'Use when…' trigger guidance, leaving all dimensions at the mid level.

Suggestions

Add an explicit 'Use when…' clause, e.g. 'Use when creating high-contrast, theatrical UI or when the user requests bold, dramatic layouts.'

Include natural trigger terms users would actually say, such as 'dramatic UI', 'high-contrast design', and 'theatrical layouts', to improve discoverability.

Lead with a concrete action verb (e.g. 'Authors' or 'Generates') rather than only adjectives to clarify what the skill does.

Dimension	Reasoning	Score
Specificity	It names the design domain with several specific stylistic attributes ('high-contrast', 'bold layouts', 'immersive visuals', 'unconventional compositions'), which is above vague boilerplate, but it lists no concrete action verbs describing what the skill does.	2 / 3
Completeness	It answers what the skill is (a high-contrast, theatrical design style) but never states when to use it; per the guidelines a missing 'Use when…' clause caps completeness at 2.	2 / 3
Trigger Term Quality	Some relevant keywords appear ('high-contrast', 'theatrical design', 'bold layouts') that a user might say, but coverage is thin and missing common variations, with no explicit trigger guidance.	2 / 3
Distinctiveness Conflict Risk	The dramatic/theatrical/high-contrast niche is somewhat specific, but with no explicit triggers it could still overlap with other design-style skills.	2 / 3
	Total	8 / 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/dramatic/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.