bolder
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability.
56
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 the core purpose of enhancing bland designs but lacks the explicit trigger guidance required for Claude to reliably select it from a skill library. It uses appropriate third-person voice and avoids jargon, but needs more concrete actions and a clear 'Use when...' clause to be effective.
Suggestions
Add a 'Use when...' clause with trigger terms like 'make it more exciting', 'too plain', 'needs more visual interest', 'spice up the design'
List specific concrete actions such as 'adds bold typography, increases color contrast, introduces dynamic layouts, applies visual hierarchy'
Include common user phrases like 'make it pop', 'too boring', 'needs more energy', 'bland design' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (design) and describes the general action (amplify, increase impact), but lacks concrete specific actions like 'add bold typography', 'increase contrast', or 'apply dynamic layouts'. | 2 / 3 |
Completeness | Describes what it does (amplify designs) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms ('safe', 'boring designs', 'visually interesting', 'impact', 'usability') but misses common variations users might say like 'make it pop', 'more exciting', 'spice up', 'bland', 'dull', or 'eye-catching'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to design enhancement but could overlap with general design skills, UI/UX skills, or styling skills. The 'safe or boring' qualifier helps but isn't distinctive enough. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured workflow for design amplification with clear sequential steps and good validation checkpoints. However, it's somewhat verbose with repeated warnings about 'AI slop' and lacks concrete code examples that would make the guidance more immediately actionable. The content would benefit from consolidation and the addition of executable CSS/code snippets.
Suggestions
Add concrete CSS code examples for key techniques (e.g., typography scale, shadow treatments, animation timing functions) to improve actionability
Consolidate the repeated 'AI slop' warnings into a single, prominent section to reduce redundancy
Consider splitting the detailed amplification techniques (Typography, Color, Spatial, Motion) into separate reference files with the main skill providing an overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some redundant explanations and repeated warnings about 'AI slop' that could be consolidated. The content is useful but could be tightened by ~20-30%. | 2 / 3 |
Actionability | Provides good conceptual guidance with specific techniques (e.g., '3x-5x scale differences', '50-100ms delays'), but lacks executable code examples. For a design skill, concrete CSS/code snippets would significantly improve actionability. | 2 / 3 |
Workflow Clarity | Clear sequential workflow: mandatory preparation → assess current state → plan amplification → amplify design → verify quality. Includes explicit checkpoints ('Do NOT proceed until...') and validation steps at the end. | 3 / 3 |
Progressive Disclosure | References external 'frontend-design skill' appropriately, but the main content is somewhat monolithic. The amplification section could benefit from being split into separate reference files for typography, color, motion, etc. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.