CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

botanical-design

Complete design system guide for Dr. Sophia AI's botanical brand identity. Includes official typography (Livvic/Onest), color palette (#00B368 green spectrum), shadow systems, gradients, and component templates. Use when creating or modifying UI components, implementing brand colors, or ensuring design consistency across the application.

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable reference skill: copy-paste templates, explicit color mappings, and clean one-level-deep progressive disclosure to its three reference files. The main weakness is redundancy — color guidance is repeated across four sections and padded metadata (keywords line, production stats, dated footer) adds tokens without adding guidance.

Suggestions

Consolidate the four color sections ('Essential Colors', 'Component Color Mapping', 'Document Download Colors', 'Color Selection Rules') into a single authoritative color-mapping table and push secondary mappings into references/color-palette.md.

Remove the '**Keywords**' line (it duplicates the frontmatter description) and the non-actionable 'Production Requirements' marketing stats and dated footer metadata.

Since the body already contains a full 'Typography Implementation' CSS section, trim it to the essential import snippet and defer extended examples to references/typography-guide.md to reduce duplication.

DimensionReasoningScore

Conciseness

The body is mostly efficient reference material (templates, hex tables, CSS), but the same color information appears across four sections ('Essential Colors', 'Component Color Mapping', 'Document Download Colors', 'Color Selection Rules'), and the '**Keywords**' line, 'Production Requirements' marketing stats ('98% colors ✅', 'Consistent 3-5s response times'), and dated footer ('Last Updated: October 7, 2025') are padded or time-sensitive content Claude cannot act on. This sits between the 2 anchor (several padded sections) and 4 anchor (efficient with minor trim), so 3 fits best.

3 / 5

Actionability

Everything is directly executable: copy-paste-ready JSX container and button templates with the exact Tailwind classes, the Google Fonts CSS import block, explicit scenario-to-hex mapping tables, and a concrete 'Avoid' list with named replacements. It is not 4 because there are no meaningful gaps — the common cases (containers, buttons, color selection) are each covered with ready-to-use code.

5 / 5

Workflow Clarity

This is a single-purpose reference skill: apply the brand system when building components. Per the simple-skill exception, workflow clarity can score 5 when the single action is unambiguous, and it is — the 'When to Use This Skill' section plus the color-mapping tables and template rules leave no ambiguity about what to do. No destructive or batch operations exist that would require validation checkpoints or cap the score.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview with quick-reference essentials inline, and a dedicated 'Detailed Documentation' section signals all three one-level-deep references ('Extended Color Palette', 'Typography Guide', 'Transformation History') with verified existing files. It is not 4 because the split is appropriate and navigation is easy, not just mostly clear — no buried references or content that clearly belongs in a separate file is inlined wholesale.

5 / 5

Total

18

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it concisely states what the skill contains with concrete specifics (fonts, hex codes, component templates) and includes an explicit, natural 'Use when...' clause. The only weaknesses are slightly generic trigger phrases like 'design consistency' and 'UI components' that could overlap with other frontend skills.

DimensionReasoningScore

Specificity

The description enumerates concrete, specific assets — 'official typography (Livvic/Onest), color palette (#00B368 green spectrum), shadow systems, gradients, and component templates' — which matches the anchor for several specific items with minor gaps. It stays at 4 rather than 5 because it lists included materials rather than multiple concrete actions, and at 4 rather than 3 because coverage is broad and every item is concrete, not generic.

4 / 5

Completeness

It explicitly answers both what ('Complete design system guide... Includes official typography... color palette... shadow systems, gradients, and component templates') and when ('Use when creating or modifying UI components, implementing brand colors, or ensuring design consistency') with concrete trigger phrases, matching the top anchor. It is not 4 because the 'when' clause is already explicit and specific, not merely present.

5 / 5

Trigger Term Quality

'Use when creating or modifying UI components, implementing brand colors, or ensuring design consistency' provides good natural phrases users would actually say. It is not 5 because common variations like 'styling', 'fonts', or 'theme' are absent, and not 3 because the included triggers are natural rather than jargon-only.

4 / 5

Distinctiveness Conflict Risk

'Dr. Sophia AI's botanical brand identity' establishes a clear niche, but fairly broad phrases like 'UI components' and 'design consistency' create minor overlap risk with closely related frontend or design skills. It is not 5 due to that residual overlap, and not 3 because the brand-specific framing makes triggering for the wrong skill unlikely.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fernandezbaptiste/Skrillz

Path

skill-builder-package/examples/botanical-design/SKILL.md

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.