CtrlK
BlogDocsLog inGet started
Tessl Logo

pulse

Dynamic, vibrant style with thick borders, geometric shapes, high-contrast colors, and expressive typography conveying motion and vitality.

63

Quality

75%

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

Quality

Content

100%

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-crafted, actionable reference: concrete design tokens, explicit do/don't rules, a sequenced authoring workflow with a QA checklist, and testable quality gates. It is concise, navigable, and implementation-ready without relying on external files.

DimensionReasoningScore

Conciseness

The body is lean bullet-point guidance with no padding or explanations of concepts Claude already knows; every section (tokens, rules, workflow, quality gates) earns its place. Minor thematic overlap between Brand and Style Foundations is not enough to drop it to the "could be tightened" anchor at 2.

3 / 3

Actionability

Provides concrete, copy-paste-ready specifics: exact hex tokens (#EA580B), exact spacing/typography scales, a 4px border rule, an explicit required-states list, and a fixed output structure. Per the instruction-only scoring note, absence of code is not penalized when guidance is this concrete, so it reaches 3 rather than 2.

3 / 3

Workflow Clarity

The 6-step "Guideline Authoring Workflow" is clearly sequenced and terminates in a QA checklist, with the "Quality Gates" section providing testable validation checkpoints. This is not a destructive/batch operation, so the missing-feedback-loop cap does not apply, and it exceeds the bare-list anchor at 2.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the skill is a focused, self-contained reference organized into clearly navigable sections with no nested references. This matches the simple-skill exemption (well-organized sections, no external references required) rather than the inline-could-be-split anchor at 2.

3 / 3

Total

12

/

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 concretely characterizes the Pulse visual style but is attribute-focused rather than action-focused and omits any "Use when..." trigger guidance. It is clear and non-vague yet functionally incomplete as a trigger description.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating or styling UI for the Pulse design system, or when the user asks for bold/vibrant geometric styling."

Lead with concrete capabilities/actions (e.g. "Authors implementation-ready Pulse design-system guidelines: tokens, component rules, accessibility criteria") before the stylistic adjectives.

Include natural trigger terms users would say ("Pulse design system", "bold UI theme", "design tokens") to improve distinctiveness and trigger quality.

DimensionReasoningScore

Specificity

Names concrete style elements ("thick borders", "geometric shapes", "high-contrast colors", "expressive typography") but describes attributes rather than concrete actions, matching the "names domain and some actions" anchor. It is not vague enough for 1, yet lists no executable capabilities to reach 3.

2 / 3

Completeness

Answers "what" by describing the style, but has no "Use when..." clause or explicit trigger guidance, which per the judging guidelines caps completeness at 2. It is not missing both what and when (so not 1), but lacks an explicit when (so not 3).

2 / 3

Trigger Term Quality

Contains relevant style adjectives ("vibrant", "geometric", "high-contrast") but lacks natural trigger phrases a user would say to invoke the skill (e.g. "design system", "UI theme", "brand styling"). It has some keywords but misses common variations, so not 3, and is not pure jargon, so above 1.

2 / 3

Distinctiveness Conflict Risk

The style profile is fairly specific (thick borders, geometric, high-contrast) but "dynamic, vibrant style" could overlap with other design-style skills and there are no distinct explicit triggers. It is not generic enough for 1 and lacks a clear distinct niche with triggers for 3.

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.