CtrlK
BlogDocsLog inGet started
Tessl Logo

dating-web

A consumer-feeling dating / matchmaking dashboard — left rail navigation, ticker bar of community signals, headline KPIs, a 30-day mutual-matches bar chart, and a match-rate trend block. Editorial typography, restrained accent. Use when the brief asks for a "dating site", "matchmaking", "community dashboard", "social network dashboard", or any consumer product where the data is the story.

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

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

A highly actionable, well-structured design skill with concrete specs and a crisp output contract. The main weakness is a subjective self-check that lacks a runnable fix-and-retry loop.

Suggestions

Make the self-check runnable where possible — e.g., assert the accent token appears in ≤4 places via a grep/count rather than a subjective 'restrained' judgment.

Add an explicit fix-and-retry loop after the self-check (if a check fails, revise the offending section and re-verify) to strengthen workflow_clarity.

Tighten the editorial prose in the intro paragraph to remove flavor text that does not change the output.

DimensionReasoningScore

Conciseness

Mostly lean and purposeful with specific copy examples and concrete layout specs; a little editorial flavor text ('feels like a Sunday-paper dating column rendered as software') could be trimmed but earns its place for a design skill.

4 / 5

Actionability

Fully executable guidance: pixel widths (220–260px), font-feature-settings: 'tnum', data-od-id attributes, an SVG bar chart with ~30 bars, and a precise output contract with artifact tags — copy-paste ready.

5 / 5

Workflow Clarity

Clear 5-step sequence ending in a self-check checkpoint, but the self-check is subjective ('reads as restrained, editorial, slightly funny') with no fix-and-retry feedback loop, leaving a minor validation gap.

4 / 5

Progressive Disclosure

Single well-organized SKILL.md with clear Workflow and Output contract sections and a one-level reference to an injected DESIGN.md; no bundle files to misplace, though it sits just over the 50-line simple-skill threshold.

4 / 5

Total

17

/

20

Passed

Description

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

A strong, well-targeted description that states concrete dashboard components and gives explicit, natural-language use-when triggers. Minor room to broaden trigger synonyms, but it clearly answers what and when.

DimensionReasoningScore

Specificity

Names several concrete dashboard features ('left rail navigation, ticker bar of community signals, headline KPIs, a 30-day mutual-matches bar chart, and a match-rate trend block') rather than vague language, though it enumerates components more than distinct actions.

4 / 5

Completeness

Explicitly answers both 'what' (a consumer dating/matchmaking dashboard with listed components) and 'when' via a concrete 'Use when the brief asks for…' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('dating site', 'matchmaking', 'community dashboard', 'social network dashboard'); good coverage but missing a few common synonyms or file/medium cues.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (dating/matchmaking consumer dashboard) with distinctive triggers, making overlap with unrelated skills minimal.

5 / 5

Total

18

/

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.

Validation — 15 / 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.