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.

72

Quality

89%

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

78%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 tight, well-structured design-generation skill with concrete layout specs, a clear sequenced workflow, and a self-check checklist. It loses a little on conciseness (elaborate example copy) and actionability (no HTML template) but is appropriately self-contained with no reference sprawl.

Suggestions

Trim the multi-line KPI copy examples to one short sample each to improve token efficiency.

Add a minimal copy-paste HTML scaffold (doctype, head with inline CSS, body skeleton) so the output is fully executable rather than specified.

Convert the self-check bullets into an explicit verify-then-fix loop so the workflow ends with a concrete validation gate.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (no basic-concept explanations), but the illustrative KPI copy examples ('1,842 ↑ 41 this wk · healthy growth', '4 / exes in your circle · manageable. two are now friends.') are slightly elaborate padding that could be trimmed.

4 / 5

Actionability

Highly concrete guidance — '220–260px sidebar', '3 columns × 3 rows', "font-feature-settings: 'tnum'", 'SVG bar chart with ~30 bars', 'data-od-id on ticker, sidebar, kpi grid, chart, trend' — but provides no copy-paste HTML scaffold, leaving minor gaps for an instruction-only design skill.

4 / 5

Workflow Clarity

Clear numbered sequence (Read DESIGN.md → Pick brand voice → Layout → Write HTML → Self-check) with a 3-point self-check checklist, but there is no validate→fix→retry feedback loop; this is a single-shot generative task so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

Self-contained ~60-line body with well-organized sections (## Workflow, ## Output contract), no bundle files, and no nested references — the only external mention ('the active DESIGN.md (injected above)') is a runtime-injected file, appropriately one level deep.

5 / 5

Total

17

/

20

Passed

Description

100%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 high-quality description that names concrete UI components, supplies an explicit 'Use when' clause with multiple natural trigger synonyms, and stakes out a distinct editorial-design niche. Voice is appropriately third person with no fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete deliverables — 'left rail navigation', 'ticker bar of community signals', 'headline KPIs', 'a 30-day mutual-matches bar chart', 'and a match-rate trend block' — giving comprehensive, specific coverage of what the skill produces.

5 / 5

Completeness

Explicitly answers both what (a consumer dating/matchmaking dashboard with named components) and when ('Use when the brief asks for a "dating site", "matchmaking"...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides natural user-facing synonyms in the 'Use when' clause — 'dating site', 'matchmaking', 'community dashboard', 'social network dashboard' — with comprehensive coverage including a catch-all consumer-product phrasing.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (editorial dating/matchmaking dashboard) with distinct triggers and a defined anti-trope stance ('no swipe deck'), minimizing overlap with other skills.

5 / 5

Total

20

/

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.