CtrlK
BlogDocsLog inGet started
Tessl Logo

new-app

Workflow for creating new applications from scratch. Covers requirements gathering, tech stack selection, scaffolding, implementation, and delivery of a functional prototype.

57

Quality

65%

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 ./packages/core/src/skills/bundled/new-app/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The content is a well-sequenced, actionable workflow with concrete tools, commands, and platform-specific stack recommendations, and it is appropriately organized as a single self-contained file. Its main weakness is verbosity in the plan and implementation steps, which could be trimmed without losing clarity.

DimensionReasoningScore

Conciseness

The body is mostly efficient and never explains concepts Claude already knows, but steps 2 and 4 are dense padded sentences with redundant adjectives ('beautiful, modern, and polished', 'visually coherent and functional') that could be tightened.

3 / 5

Actionability

It names concrete tools ('todo_write', 'run_shell_command', 'ask_user_question'), specific commands ('npm init', 'npx create-react-app'), and explicit per-platform tech stacks, giving mostly executable guidance with only minor gaps.

4 / 5

Workflow Clarity

Six clearly numbered steps (Understand → Propose → Approve → Implement → Verify → Solicit Feedback) form a clear sequence with a Verify checkpoint ('Fix bugs... ensure there are no compile errors'), though the error-recovery feedback loop is implicit rather than spelled out.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files, and is organized into well-signaled numbered sections with no need for external references, satisfying the simple-skill exception for a top score.

5 / 5

Total

16

/

20

Passed

Description

58%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.

The description clearly states what the skill does and lists concrete workflow phases, but it omits an explicit 'when to use' trigger clause in the description field and lacks the natural variation terms that would make it easily matched. Adding trigger phrasing and common app-type synonyms would materially raise completeness and trigger quality.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when the user asks to create a new application, website, game, mobile app, CLI tool, or library from scratch.'

Fold the natural synonyms already in when_to_use (website, game, mobile app, CLI tool, library) into the description so trigger_term_quality reaches the common variations users actually say.

Tighten the action list from workflow phases to more concrete capabilities (e.g. 'scaffold a project, select a tech stack, generate placeholder assets, build a runnable prototype') to push specificity toward 5.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'requirements gathering, tech stack selection, scaffolding, implementation, and delivery of a functional prototype' — but these are high-level workflow phases rather than granular capabilities, leaving minor gaps versus the comprehensive 5 anchor.

4 / 5

Completeness

It gives a clear 'what' ('Workflow for creating new applications from scratch...') but contains no 'Use when...' trigger clause in the description field itself, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

It includes relevant natural terms like 'creating new applications from scratch', but the common variations users say (website, game, mobile app, CLI tool, library) appear only in the separate when_to_use field, not the description, so coverage is incomplete.

3 / 5

Distinctiveness Conflict Risk

'creating new applications from scratch' carves a clear greenfield-prototyping niche that is mostly distinct, with only minor overlap risk against general development skills.

4 / 5

Total

14

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
QwenLM/qwen-code
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.