frame-flowchart-sticky

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

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/frame-flowchart-sticky/SKILL.md

Quality

Content

86%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.

The body is a lean, highly actionable specification with concrete design values and clear sectioned structure. Its main gap is the absence of complete copy-paste code blocks and explicit validation checkpoints, though neither is strictly required for this non-destructive single-purpose template skill.

Dimension	Reasoning	Score
Conciseness	The body is dense with concrete specifications (hex colors, pixel sizes, font names, CSS transforms, SVG stroke values) and assumes Claude's competence without explaining what SVG or a flowchart is, matching 'lean and efficient; every token earns its place' rather than the minor-trimming of score 4.	5 / 5
Actionability	It gives concrete, near-executable values (e.g. '#fcd34d', 'transform: rotate(±2deg)', 'stroke-dasharray: 8 6') but stops short of complete copy-paste code blocks, fitting 'mostly executable; minor gaps' rather than the fully copy-paste-ready score 5.	4 / 5
Workflow Clarity	Sections sequence the build clearly (canvas → nodes → connectors → interactions → design details) for this single-purpose skill, but there are no explicit validation checkpoints; this fits 'clear sequence with most checkpoints present; minor gaps' better than the checkpoint-rich score 5.	4 / 5
Progressive Disclosure	At under 50 lines with no bundle files and no need for external references, the well-organized section headers (画布, 节点, 连接线, 可选交互, 设计细节) satisfy the simple-skill exception allowing a score of 5 for clear organization.	5 / 5
	Total	18 / 20 Passed

Description

58%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.

The description concretely describes the template's visual signature but lacks an explicit 'Use when...' trigger clause and omits common user terms like 'flowchart'. It is distinct but not fully self-triggering.

Suggestions

Append an explicit trigger clause, e.g. 'Use when creating flowchart, process, or onboarding videos that need a whiteboard/sticky-note look.'

Add natural trigger terms users actually say — 'flowchart', 'diagram', 'process map' — alongside the existing 'sticky-note' and 'whiteboard' phrasing.

Reframe the element list as concrete actions (e.g. 'Builds sticky-note flowchart frames with SVG curve connectors and cursor interaction') to strengthen specificity and completeness together.

Dimension	Reasoning	Score
Specificity	The description lists several concrete elements ('SVG curve connectors, sticky-note nodes, and cursor interaction'), matching the 'lists several specific actions' anchor rather than the less comprehensive score 3 or fully comprehensive score 5.	4 / 5
Completeness	A clear 'what' is present but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3; it is not vague enough for 2 and lacks the explicit 'when' needed for 4.	3 / 5
Trigger Term Quality	It includes some relevant natural keywords ('sticky-note', 'whiteboard-brainstorm') but omits common variations a user would say such as 'flowchart' or 'diagram', landing at 'some relevant keywords but missing common synonyms' rather than the fuller coverage of score 4.	3 / 5
Distinctiveness Conflict Risk	The sticky-flowchart whiteboard niche is mostly distinct with only minor overlap risk against other diagram skills, fitting 'mostly distinct; minor overlap risk' better than the broad score 3 or fully-niche score 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/frame-flowchart-sticky/SKILL.md
Commit: d4138ea

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.