CtrlK
BlogDocsLog inGet started
Tessl Logo

contact-widget

Self-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.

69

Quality

85%

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

87%

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

A well-crafted, actionable body that gives precise design and integration specs without over-explaining basics. The main gap is the lack of an explicit verification step in the workflow for confirming the generated widget renders and runs offline.

Suggestions

Add a verification step to the workflow, e.g. 'Open the generated file in a browser; confirm the widget renders and makes no network requests beyond Google Fonts' — this would lift workflow_clarity to 3.

The Backend integration tier list (5 SDKs with URLs) could optionally move to a reference file if the skill grows, though at its current size it is acceptable inline.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it does not explain HTML/CSS basics — and every section (design specs, input table, tiered backend options) earns its place rather than padding, with no unnecessary conceptual explanation to tighten.

3 / 3

Actionability

Provides exact, copy-paste-ready guidance: concrete design tokens (px sizes, hex colors, shadow values), a typed input table with defaults, and executable snippets such as `window.location.href = 'mailto:…'` and `fetch('/api/contact', { method: 'POST', body: JSON.stringify({ text }) })`.

3 / 3

Workflow Clarity

The four-step workflow is clearly sequenced but has no explicit verification checkpoint, even though the skill's own constraints ('zero network calls beyond Google Fonts', 'runs from disk') make a render/offline check a natural validation step; the body exceeds 50 lines so the simple-skills 3-exception does not cleanly apply.

2 / 3

Progressive Disclosure

Content is organized into clear, single-level sections with no nested external references, and no bundle files are needed, so a single well-structured file is appropriate rather than a monolithic wall of text.

3 / 3

Total

11

/

12

Passed

Description

82%

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 concrete, well-scoped description that names specific features and a clear deliverable format, with good natural trigger terms. Its only weakness is the absence of an explicit 'Use when…' clause for when to invoke the skill.

Suggestions

Append a 'Use when…' clause naming the situations that should trigger this skill (e.g. 'Use when the user wants a floating contact/chat widget for a website') to lift completeness to 3.

Consider adding one or two user-facing synonyms (e.g. 'contact widget', 'live chat widget') directly into the description text so the trigger terms appear in the evaluated field itself.

DimensionReasoningScore

Specificity

Lists multiple concrete components — 'welcome screen, social links, meeting button, and message input' — plus the concrete deliverable 'Single HTML file, zero dependencies', matching the score-3 anchor for multiple specific capabilities.

3 / 3

Completeness

'What' is clearly stated (a self-contained chat widget with named features), but there is no 'Use when…' or equivalent explicit trigger guidance, which the judging guidelines cap at 2.

2 / 3

Trigger Term Quality

Contains natural terms a user would say — 'floating chat widget', 'social links', 'meeting button', 'message input' — giving good coverage of likely request phrasings.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche — a floating single-file chat/contact widget — with distinct triggers, making it unlikely to fire for the wrong skill.

3 / 3

Total

11

/

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.