CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

miniapp

Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.

Quality

88%

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.

An exceptionally lean body that only adds facts Claude cannot already know: tool availability, host constraints, and the escalation path to `apps` publish. The single relative weakness is the absence of a minimal worked example that would make the guidance fully concrete.

Suggestions

Include a short skeleton or minimal HTML snippet of a typical self-contained playground to make the guidance copy-paste ready.

Add one line clarifying what "tiny" means in practice (e.g., a target element/interaction count or file-size ceiling) so the scope constraint is checkable.

DimensionReasoningScore

Conciseness

Every line conveys host-specific constraints Claude could not infer ("no network requests, external assets, modules, or servers"; "the client attaches the playground from the typed tool result") with zero padding or explanation of known concepts.

5 / 5

Actionability

The guidance is concrete and directive, including a specific alternative command ("Use `apps` action `publish` instead"), but there is no minimal example or skeleton of a typical playground, leaving a minor gap versus fully copy-paste-ready guidance.

4 / 5

Workflow Clarity

This is a simple single-purpose skill and its single action — invoke the `miniapp` tool with the listed constraints — is unambiguous; it involves no destructive or batch operations, so no validation checkpoints are required.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and is well organized as a short intro plus a constraint list, satisfying the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

78%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 concise, explicit description that clearly states both what the skill does and when to use it, with natural trigger phrasing. Its main limitation is low action specificity — it names only one action and omits the range of outputs (simulations, visual explanations, games) the body actually covers.

Suggestions

List the concrete output types in the description (e.g., simulations, visual explanations, small games) to raise specificity from one action to several.

Add one or two common trigger synonyms such as "demo", "interactive", or "simulate" to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Build a tiny interactive HTML playground" names the domain and one concrete action, but lists no further actions or output types, matching the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor.

3 / 5

Completeness

It explicitly answers both questions: "Build a tiny interactive HTML playground" (what) and "only when someone asks to see, play with, or step through a mechanism" (when, with concrete trigger phrases).

5 / 5

Trigger Term Quality

"asks to see, play with, or step through" provides good natural trigger phrases, but common variations like "demo", "simulate", or "interactive" are missing, so it falls just short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"tiny interactive HTML playground" and "step through a mechanism" carve out a distinct niche with clear triggers, though there is minor overlap risk with visualization or demo-oriented skills.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

yc-software/qm

Path

skills-seed/miniapp/SKILL.md

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.