CtrlK
BlogDocsLog inGet started
Tessl Logo

vue-app

Build a Vue 3 single-page app for an Android WebView

53

Quality

61%

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/vue-app/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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 overview that assumes competence and avoids concept padding, but its workflow and actionability fall short of the top anchors by omitting a validation checkpoint and a complete executable example.

Suggestions

Add one complete, runnable minimal example (a full index.html plus app.js) so the guidance is copy-paste ready.

Insert an explicit validation/verification step in the Workflow — e.g. open index.html in the WebView, confirm the mount point renders, fix and re-check on failure.

Deduplicate the "summarise in one short line" instruction so it appears once instead of in both the Workflow and the Working-with-the-user section.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what Vue or a WebView is, and every section gives directives rather than background, with only minor repetition of the one-line summary instruction.

3 / 3

Actionability

Guidance is concrete (real paths like "assets/vendor/vue.global.prod.js" and the line "const { createApp, reactive, ref, computed } = Vue;"), but there is no complete, copy-paste-ready example such as a full index.html or app.js.

2 / 3

Workflow Clarity

The five-step Workflow is clearly sequenced, but it lacks an explicit validation or verification checkpoint and a fix-and-retry feedback loop.

2 / 3

Progressive Disclosure

The skill is under 50 lines, needs no external reference files (the referenced vendor/component files are workspace targets, not bundle references), and is organized into clear labeled sections.

3 / 3

Total

10

/

12

Passed

Description

50%

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 concise and names a specific, real capability, but it functions only as a what-statement: it lacks a "Use when…" trigger and lists a single action rather than a fuller set of concrete behaviors.

Suggestions

Add an explicit trigger clause, e.g. "Use when building an interactive UI for an Android WebView and the user prefers Vue over React."

List the concrete actions the skill performs (e.g. scaffold index.html, define global-build components, wire reactive state) so specificity can reach the top anchor.

Include natural user phrasings such as "Vue.js", "frontend", and "web app" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Build a Vue 3 single-page app for an Android WebView" names a concrete action and a specific target, but it lists only a single action rather than the multiple concrete actions the top anchor requires.

2 / 3

Completeness

It clearly states what the skill does, but the description field contains no "Use when…" clause or equivalent explicit trigger guidance, which caps completeness at 2.

2 / 3

Trigger Term Quality

"Vue 3", "single-page app", and "Android WebView" are relevant keywords, but common user variations (e.g. "Vue.js", "frontend", "web app") are missing and there is no natural "Use when…" phrasing.

2 / 3

Distinctiveness Conflict Risk

The Vue + Android WebView niche is fairly specific, but without explicit triggers it could still overlap with generic frontend or web-app skills.

2 / 3

Total

8

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing, 1 deeper-than-1-level

Warning

Total

14

/

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.