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.

60

Quality

70%

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 ./design-templates/contact-widget/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is well-structured, concrete, and efficiently written, providing clear actionable and design guidance for a single-task generation skill. The main improvements are an explicit verification step and a small example of the assembled widget output.

Suggestions

Add an explicit verification step to the workflow, e.g., "Open the generated file in a browser and confirm the widget renders with no external network calls."

Include a minimal assembled-HTML skeleton example so the core widget generation is as copy-paste-ready as the optional backend snippets.

Consider moving the Tier 3 real-time-chat vendor list into a short reference file to tighten the main body and strengthen progressive disclosure.

DimensionReasoningScore

Conciseness

The body is efficient and free of concepts Claude already knows, with only minor padding (e.g., the optional Tier 3 vendor URL list) that could be trimmed.

4 / 5

Actionability

Concrete specs (hex colors, radii, shadows) and executable snippets (mailto:/fetch) give mostly executable guidance, with the main gap being no assembled HTML example for the core widget.

4 / 5

Workflow Clarity

A clear 4-step numbered workflow with explicit defaults and a hard no-external-script constraint, missing only an explicit validation/verification checkpoint.

4 / 5

Progressive Disclosure

No bundle files exist; content is well-organized into clear sections, with only the inline Tier 3 vendor list and the slightly-over-50-line length keeping it from a perfect score.

4 / 5

Total

16

/

20

Passed

Description

66%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 is specific and distinctive, clearly conveying what the skill produces, but it lacks an explicit "when to use" clause, which limits its completeness score. Adding a trigger-guidance sentence would round it out.

Suggestions

Add an explicit trigger clause such as "Use when the user asks for a contact, chat, or floating chat widget for a site." to satisfy the 'when' requirement and lift completeness.

Include a couple more natural synonyms (e.g., "live chat", "messaging widget") in the description to broaden trigger-term coverage.

Mention the offline-form and mobile-responsive capabilities to close the minor gaps in specificity versus the full feature list in the body.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete features ("welcome screen, social links, meeting button, and message input") plus the "Single HTML file, zero dependencies" constraint, listing several specific capabilities with only minor gaps in full coverage.

4 / 5

Completeness

The "what" is clearly and concretely stated, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Natural phrases like "floating chat widget", "social links", and "meeting button" give good keyword coverage that aligns with the skill's triggers, though a few common variations (e.g., "live chat", "messaging widget") are absent from the description itself.

4 / 5

Distinctiveness Conflict Risk

"Self-contained floating chat widget" carves a distinct niche with low overlap risk, with only minor potential overlap against a generic chat or contact-form skill.

4 / 5

Total

15

/

20

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.