CtrlK
BlogDocsLog inGet started
Tessl Logo

gamified-app

A multi-frame gamified mobile-app prototype — three phone frames on a dark showcase stage. Frame 1: cover / poster, Frame 2: today's quests with XP ribbons and a level bar, Frame 3: quest detail. Vivid quest tiles, level ribbon, bottom tab bar. Use when the brief asks for a "gamified app", "habit tracker", "RPG-style life app", "level-up app", "daily quests", "XP / streak app", or "ELI5-style explainer app".

73

Quality

91%

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

92%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, highly actionable design skill: concrete specs and copy, a sequenced workflow with a validation self-check, and clean section structure. The only minor gap is a few decorative sentences that slightly pad the otherwise lean body.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (no explanations of HTML/CSS), with a few color-commentary phrases like 'quests look like quests because the colors do' and 'each one its own moment in the journey' that could be trimmed — efficient with minor over-explanation, so 4 not 5.

4 / 5

Actionability

Fully actionable concrete guidance: exact dimensions (360×780, 12px bezel, 44px corner radius), a named color (#0e0d0c), real quest-name examples, and copy like 'LV 14 · Level 14 · 1648 / 2480 XP' — copy-paste-ready specs covering the common cases.

5 / 5

Workflow Clarity

A clear 9-step sequence ending in an explicit 'Self-check' validation checklist (distinct frame purposes, tile-color balance, gamified-not-childish tone), matching the anchor for a clear sequence with explicit validation steps and a checklist.

5 / 5

Progressive Disclosure

A self-contained single-purpose skill with well-organized sections (Workflow, Output contract) and no need for external bundle files; per the simple-skill guidance, clear sectioning without file references earns a 5 here.

5 / 5

Total

19

/

20

Passed

Description

91%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, specific description that pairs a concrete artifact spec with an explicit, trigger-rich 'Use when...' clause. The only soft spot is light action-verb coverage (it describes outputs rather than actions) and a single broad trigger ('habit tracker') that could overlap a sibling skill.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete output elements ('three phone frames', 'XP ribbons and a level bar', 'quest tiles, level ribbon, bottom tab bar'), but the only action verb is 'produce' — it describes the artifact rather than enumerating actions, which keeps it just below a 5.

4 / 5

Completeness

Clearly answers both 'what' (a multi-frame gamified mobile-app prototype with per-frame content) and 'when' via an explicit 'Use when the brief asks for...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural terms users would say — 'gamified app', 'habit tracker', 'RPG-style life app', 'level-up app', 'daily quests', 'XP / streak app', 'ELI5-style explainer app' — including synonyms and phrasings.

5 / 5

Distinctiveness Conflict Risk

A clear gamified/level-up niche with distinct triggers and minimal conflict risk overall, but 'habit tracker' is broad enough to overlap a dedicated habit-tracker skill — minor overlap risk, so 4 rather than 5.

4 / 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.

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.