CtrlK
BlogDocsLog inGet started
Tessl Logo

doodle

Hand-drawn, sketch-like style with doodles, handwritten fonts, and imperfect lines for a playful, informal feel.

60

Quality

71%

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/doodle/SKILL.md
SKILL.md
Quality
Evals
Security

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 concise, well-structured, actionable guideline-authoring skill with concrete tokens, an explicit output structure, a sequenced workflow, and testable quality gates. Its main gap is the absence of a concrete worked example demonstrating the expected authored-guideline output.

Suggestions

Add one fully worked example of an authored component guideline (anatomy, states, tokens, a do/don't pair) to demonstrate the expected output format.

Show an example pairing a do-rule with a concrete don't-example, since the skill instructs this but does not model it.

Tighten minor redundancy (the 'Brand' paragraph restates the frontmatter description) and compress the weights list (e.g. '100–900') to further improve token efficiency.

DimensionReasoningScore

Conciseness

The body is lean and bullet-driven with no padding or explanations of concepts Claude already knows; each section (tokens, states, output structure, quality gates) earns its place, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Concrete copy-paste-ready tokens (hex colors, type/spacing scales), enumerated required states, and an explicit output structure are provided, but there is no worked example of an authored guideline showing the expected output format, matching 'some concrete guidance but incomplete; missing key details' rather than the 'specific examples; copy-paste ready' anchor at 3.

2 / 3

Workflow Clarity

A clear 6-step numbered authoring workflow is sequenced with a QA-checklist final step and testable Quality Gates serving as explicit validation checkpoints, matching the 'clear sequence with explicit validation steps; checklists for complex processes' anchor; this is authoring guidance, not a destructive/batch operation, so the strict feedback-loop cap does not apply.

3 / 3

Progressive Disclosure

No bundle files exist, so the single self-contained SKILL.md is evaluated on organization; it has clear, well-signaled sections and no nested references, matching the simple-skills note that well-organized sections score 3 when external references are unnecessary.

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 conveys a distinct, recognizable visual style with concrete attributes but omits any explicit usage triggers and does not name the actions Claude performs. Adding a 'Use when...' clause and concrete verbs would raise completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating hand-drawn, sketch-style, or playful informal designs.'

Lead with concrete actions (e.g. 'Apply a hand-drawn, sketch-like style...') rather than only describing attributes.

Broaden trigger terms to include common variations users might say, such as 'sketchy', 'rough draft', or 'playful design'.

DimensionReasoningScore

Specificity

The description names the domain and concrete style attributes ("doodles, handwritten fonts, and imperfect lines") but lists no concrete actions a user would invoke, so it matches the 'names domain and some actions, but not comprehensive' anchor rather than the multiple-actions anchor at 3.

2 / 3

Completeness

It clearly states what the style is, but there is no "Use when..." clause or equivalent explicit trigger, so 'when' is only implied; per the judging guideline a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

Natural terms like "doodle", "hand-drawn", "sketch", and "handwritten fonts" are present, but coverage lacks common variations (e.g. "sketchy", "rough", "playful design"), matching 'some relevant keywords but missing common variations.'

2 / 3

Distinctiveness Conflict Risk

"doodle", "hand-drawn", "sketch-like", and "handwritten fonts" describe a clearly distinct aesthetic niche that is unlikely to trigger for the wrong skill, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

9

/

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.