CtrlK
BlogDocsLog inGet started
Tessl Logo

nodejs-app

Build a Node.js server app that runs inside the WebToApp on-device runtime

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/nodejs-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 content is a tight, highly actionable overview that tells Claude only what it does not already know, sequences the build steps clearly, and is appropriately organized for a simple skill with no bundle artifacts.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned, explains only runtime-specific quirks Claude would not know (sandbox, no native modules, suspension), and avoids padding or restating known concepts, matching the score-3 anchor.

3 / 3

Actionability

It gives executable specifics such as `process.env.PORT || 3000`, exact package.json fields, the four named build modes, and a concrete file layout — copy-paste-ready guidance rather than vague direction.

3 / 3

Workflow Clarity

The numbered workflow (package.json first, minimal deps, server.js, auto-restart) is clearly sequenced, and the restart/log signal provides a feedback loop; the simple-skill allowance applies since no destructive/batch cap is triggered.

3 / 3

Progressive Disclosure

Under 50 lines with no bundle files (references/scripts/assets absent) and no external file references, the body relies solely on well-organized section headers, which the rubric explicitly allows to score 3.

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 clearly states what the skill does and is tied to a distinct platform, but it lists only one action, relies on product jargon for its trigger surface, and omits an explicit "Use when..." clause that the rubric expects for full completeness.

Suggestions

Expand from one action to multiple concrete capabilities (e.g. "serves HTTP APIs, renders SSR pages, and builds fullstack apps") to lift specificity.

Add an explicit "Use when..." clause with natural trigger terms ("Use when the user wants a Node.js API, SSR page, or fullstack app") so completeness and trigger_term_quality can reach 3.

Replace or augment the product-jargon "WebToApp on-device runtime" phrasing with terms a user would actually say.

DimensionReasoningScore

Specificity

It names one concrete action ("Build a Node.js server app") and a specific runtime, but lists only a single action rather than the multiple specific concrete actions of the score-3 anchor.

2 / 3

Completeness

The description answers "what" clearly but lacks any "Use when..." trigger clause; per the guidelines, a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Natural terms like "Node.js" and "server app" appear, but "WebToApp on-device runtime" is product jargon and common variations (Express, API, backend, SSR) are missing, matching the score-2 anchor.

2 / 3

Distinctiveness Conflict Risk

Being locked to the specific "WebToApp on-device runtime" gives it a clear niche that is unlikely to conflict with other Node skills, matching the score-3 anchor despite the absent trigger phrasing.

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.