CtrlK
BlogDocsLog inGet started
Tessl Logo

html-app

Build a single-page HTML/CSS/JS app for an Android WebView

65

Quality

78%

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 ./app/src/main/assets/skills/html-app/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, well-structured skill that assumes competence, gives concrete executable guidance, sequences the work with a finishing validation checklist, and is appropriately organized for a sub-50-line single-purpose skill with no external references needed.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it gives the viewport meta verbatim, lists relative units and thresholds, and never explains what HTML/CSS/JS or a viewport is; the only repetition (the one-line summary guardrail) is intentional reinforcement, not padding, so it meets the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Guidance is concrete and executable: an exact viewport meta tag, specific relative units, a 44px tap-target floor, a ~400-line split threshold, file naming (index.html), and named tool calls (GenerateImage, Read, Edit, Write); per the rubric's instruction-only note, the absence of a full HTML skeleton is not penalized when guidance is this actionable.

3 / 3

Workflow Clarity

A clear numbered Workflow (1–5) is followed by a 'Review heuristics before finishing' checklist that acts as an explicit validation checkpoint (tap targets, offline render, alt tags, AA contrast), matching the 'clear sequence with explicit validation steps; checklists' anchor for this simple skill.

3 / 3

Progressive Disclosure

At under 50 lines with no bundle files present (references/scripts/assets directories do not exist) and no need for external references, the well-organized sections (Constraints, Workflow, Review heuristics, Working with the user) satisfy the simple-skills note that progressive disclosure can score 3 on organization alone.

3 / 3

Total

12

/

12

Passed

Description

57%

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 in its Android WebView niche but stops at a single action and omits any explicit 'Use when' trigger guidance, leaving completeness and trigger coverage at the mid level.

Suggestions

Add an explicit 'Use when...' clause to the description (e.g., 'Use when the user wants a static page, landing screen, mobile UI demo, or interactive prototype for an Android WebView') to raise completeness to 3.

Broaden trigger terms in the description itself with natural variations like 'web page', 'landing page', 'mobile UI', or 'prototype' rather than relying on the separate when_to_use field.

List a couple more concrete actions (e.g., 'Build and iterate on a single-page HTML/CSS/JS app; generate inline imagery') to move specificity from one action to multiple specific actions.

DimensionReasoningScore

Specificity

The phrase 'Build a single-page HTML/CSS/JS app for an Android WebView' names a concrete domain (HTML/CSS/JS, Android WebView) and one action (build), but lists only a single action rather than multiple specific concrete actions, so it falls short of the level-3 anchor.

2 / 3

Completeness

It clearly states what the skill does ('Build a single-page HTML/CSS/JS app for an Android WebView') but contains no 'Use when...' clause or equivalent explicit trigger guidance in the description field, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

It includes relevant natural terms ('HTML', 'CSS', 'JS', 'app', 'Android WebView') a user might say, but misses common variations such as 'web page', 'landing page', or 'prototype' that appear only in the separate when_to_use field, matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The 'Android WebView' single-file mobile niche is a clear, specific target unlikely to be served by generic web-page skills, fitting the 'clear niche with distinct triggers; unlikely to conflict' anchor; it is not the level-2 anchor because the WebView framing is more specific than 'Works with document files'.

3 / 3

Total

9

/

12

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
shiaho777/web-to-app
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.