CtrlK
BlogDocsLog inGet started
Tessl Logo

creative

Playful, character-driven design with expressive typography and bold graphics for landing pages and creative projects.

49

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/creative/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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-organized, self-contained guideline-authoring skill with a clear sequenced workflow, but it leans on structural directives and overlapping sections rather than a concrete worked example. Actionability and conciseness are the main improvement areas.

Suggestions

Add a concrete worked example of a full component guideline (anatomy, states, tokens) so the abstract directives become copy-paste-ready, improving actionability.

Consolidate the overlapping Rules Do/Don't, Expected Behavior, Quality Gates, and Example Constraint Language sections to remove restated principles and tighten token efficiency.

Insert an explicit mid-workflow validation checkpoint (e.g., 'Review the draft against the Quality Gates before finalizing; fix and re-check') to add a feedback loop to the authoring process.

DimensionReasoningScore

Conciseness

The body is lean with no padding of concepts Claude already knows, but the Do/Don't, Expected Behavior, Quality Gates, and Example Constraint Language sections restate overlapping principles and could be consolidated.

2 / 3

Actionability

It provides concrete structural checklists (Required Output Structure, required-states list, 6-step workflow) but no complete worked example of an actual guideline, so guidance is actionable yet incomplete.

2 / 3

Workflow Clarity

The Guideline Authoring Workflow gives a clear 6-step sequence with a final QA checklist, but validation is end-of-flow rather than interleaved checkpoints and there is no explicit validate-fix-retry feedback loop.

2 / 3

Progressive Disclosure

The skill is a single self-contained file with well-organized headed sections and no nested references, so content is appropriately scoped and easy to navigate with no need for external bundles.

3 / 3

Total

9

/

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 conveys a concrete creative aesthetic and target use cases, but it lacks explicit action verbs, an explicit 'Use when...' trigger, and broad enough trigger terms to fully distinguish it. It is solid but mid-tier across all dimensions.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g., 'Use when creating landing pages, marketing pages, or playful brand design needing expressive typography.'

Name concrete capabilities with action verbs (e.g., 'Generate', 'Apply', 'Author design-system guidelines') so the skill's actions are explicit, not just its aesthetic.

Broaden trigger terms with common variations users would say, such as 'branding', 'marketing page', 'hero section', or 'bold graphics'.

DimensionReasoningScore

Specificity

It concretely names the design domain ('playful, character-driven design', 'expressive typography', 'bold graphics', 'landing pages') but states no explicit action verbs, so it names a domain without listing concrete capabilities.

2 / 3

Completeness

It answers 'what' (a playful, character-driven design style) and gives an implied 'when' ('for landing pages and creative projects'), but provides no explicit 'Use when...' trigger, capping completeness at 2.

2 / 3

Trigger Term Quality

Terms like 'playful', 'design', 'typography', 'landing pages', and 'creative projects' are reasonably natural, but coverage is incomplete and lacks common variations or explicit trigger phrasing.

2 / 3

Distinctiveness Conflict Risk

The playful creative landing-page niche is themed clearly, but 'creative projects' is broad enough to overlap with other design skills, so it is only somewhat distinct.

2 / 3

Total

8

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
bergside/awesome-design-skills
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.