CtrlK
BlogDocsLog inGet started
Tessl Logo

frame-flowchart-sticky

SVG curve connectors, sticky-note nodes, and cursor interaction with a whiteboard-brainstorm feel.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/frame-flowchart-sticky/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 lean, highly actionable design spec with concrete values and clear organization that earns top marks across all content dimensions.

DimensionReasoningScore

Conciseness

The body is dense and token-efficient — exact hex colors, CSS values, and font names with no padding or condescending explanation of concepts Claude already knows.

3 / 3

Actionability

Provides fully concrete, copy-paste-ready specs (240x180px nodes, '#fcd34d' palette, 'transform: rotate(±2deg)', stroke 2.5, marker-end arrows) leaving nothing abstract.

3 / 3

Workflow Clarity

A simple single-purpose design spec under 50 lines, organized into clear component sections (canvas, nodes, connectors, interaction, constraints) with unambiguous guidance and no destructive operation requiring validation.

3 / 3

Progressive Disclosure

Well-organized into labeled sections, under 50 lines, with no need for external references and no bundle files to navigate — meeting the rubric's simple-skill allowance.

3 / 3

Total

12

/

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 clear, distinctive visual niche but is framed as a feature list rather than actionable triggers and omits any explicit 'when to use' guidance.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when turning a process, workflow, or system into a whiteboard flowchart or onboarding diagram.'

Reword features as actions and surface common user terms ('flowchart', 'diagram', 'workflow', 'process map') to improve trigger_term_quality.

Mention the flowchart structure (nodes + connectors + branching) so the 'what' is comprehensive rather than purely visual.

DimensionReasoningScore

Specificity

Names the domain and concrete visual elements ('SVG curve connectors', 'sticky-note nodes', 'cursor interaction'), but these are framed as features rather than actions and omit key aspects like flowchart layout and handwritten fonts.

2 / 3

Completeness

Clearly states what the skill produces (the visual signature) but provides no 'Use when...' clause or equivalent trigger guidance, capping completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Contains some natural terms ('whiteboard-brainstorm', 'sticky-note') but leans on jargon ('SVG curve connectors') and misses common variations a user would actually say like 'flowchart' or 'diagram'.

2 / 3

Distinctiveness Conflict Risk

The sticky-note whiteboard-flowchart niche is distinctive and unlikely to trigger for unrelated skills; it is clearly distinguishable from generic diagram or document skills.

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.