CtrlK
BlogDocsLog inGet started
Tessl Logo

mobile-app

A mobile-app screen rendered inside a pixel-accurate iPhone 15 Pro frame on the page. Built by copying the seed `assets/template.html` and pasting one screen archetype from `references/layouts.md`. Use when the brief asks for "mobile app", "iOS app", "Android app", "phone screen", or "app UI".

70

Quality

86%

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 well-structured, mostly lean body that sequences a six-step workflow with an explicit self-check and routes detail to real one-level-deep bundle files. Main room for improvement is making the validation feedback loop explicit and showing literal :root variable names.

Suggestions

Make Step 4's feedback loop explicit: 'If a checklist item fails, fix it and re-run the checklist before emitting the artifact' rather than leaving fix→retry implicit.

Show the six :root variable names inline (or one example replacement) so the design-token mapping in Step 1 is copy-paste ready.

Trim Step 4's "Pay extra attention to" list since those items already appear in references/checklist.md and the Hard rules, keeping only the cross-reference.

DimensionReasoningScore

Conciseness

Lean and free of concept over-explanation, assuming Claude's competence throughout; docked one point because Step 4's "Pay extra attention to" list partially duplicates references/checklist.md and the Hard rules, so a few tokens could be trimmed.

4 / 5

Actionability

Gives concrete, executable steps (copy template.html to index.html, replace the six :root variables, paste the archetype block into <main class='content'>) and a real artifact-emit block; falls short of 5 because no literal :root variable names or filled example screen are shown inline.

4 / 5

Workflow Clarity

Clear six-step sequence with an explicit self-check checkpoint (Step 4 referencing checklist.md with specific items to verify); not a 5 because the fix-and-retry feedback loop is implicit rather than spelled out as a validate→fix→re-run cycle.

4 / 5

Progressive Disclosure

A resource-map file tree plus one-level-deep, clearly signaled references (assets/template.html, references/layouts.md, references/checklist.md) — all verified to exist — with content appropriately split across files, making navigation easy.

5 / 5

Total

17

/

20

Passed

Description

95%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, third-person description that concretely states what it builds and gives explicit trigger phrases with platform synonyms. The only slight gap is action breadth — it describes essentially one copy-and-paste workflow rather than a broad action set.

DimensionReasoningScore

Specificity

Names several concrete actions ("rendered inside a pixel-accurate iPhone 15 Pro frame", "copying the seed assets/template.html", "pasting one screen archetype from references/layouts.md") with only minor coverage gaps; not quite the comprehensive multi-action list of a 5.

4 / 5

Completeness

Explicitly answers both what ("A mobile-app screen rendered inside a pixel-accurate iPhone 15 Pro frame... Built by copying the seed... and pasting one screen archetype...") and when ("Use when the brief asks for 'mobile app', 'iOS app'..."), matching the anchor exactly.

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger phrases ("mobile app", "iOS app", "Android app", "phone screen", "app UI") plus extra synonyms in the triggers frontmatter ("app mockup", "移动端", "手机 app"), covering platform variants users would actually say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (mobile-app mockups in an iPhone 15 Pro frame) with platform-specific triggers and minimal overlap with other skills.

5 / 5

Total

19

/

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.