CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webapp-building

Build or modify production-oriented web applications by following the repository architecture and validating real user flows.

Quality

71%

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 ./resources/bundled-skills/webapp-building/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, well-structured body that assumes Claude's competence and wastes no tokens, with a clearly sequenced workflow and real validation gates. Its main weakness is actionability: it names tools and states to check but never shows a concrete command, script invocation, or worked example of running and interpreting the acceptance checks.

Suggestions

Add one or two concrete check invocations, e.g. an example `verify_changes` call or the specific package scripts to run for focused vs. full acceptance checks.

Add a brief feedback loop after step 5 (what to do when checks fail: fix, re-run, and report baseline vs. introduced failures), which would lift workflow clarity toward 5.

Give a short worked example of "the smallest affected user flow" (e.g., login or checkout) so step 2's instruction is executable rather than directional.

DimensionReasoningScore

Conciseness

The body is ~35 lean lines with zero concept explanations Claude already knows — no web-dev primers, no library tutorials, no padding. Every line is directive (e.g., "Inspect the repository, package scripts, design system, routing, and data boundaries", "Report any baseline failures separately from introduced failures"), matching anchor 5 ("Lean and efficient; assumes Claude's competence; every token earns its place"). The only non-instructional token is the one-line copyright notice, which is negligible.

5 / 5

Actionability

There is concrete guidance — the tool routing table maps exact tools ("fast_context", "verify_changes", "design_component") to uses, and step 4 lists specific states ("inputs, loading, error, empty, success, and responsive") — but no executable commands or examples: "Run focused checks, then broader checks proportional to risk" and "Run project scripts" name no actual script or check invocation. This lands at anchor 3 ("Some concrete guidance but incomplete... missing key details") rather than 4, which expects concrete commands with only minor gaps.

3 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced (inspect → trace flow → implement → validate states → run checks) with validation checkpoints present ("Validate inputs, loading, error, empty, success, and responsive states"; "Run focused checks, then broader checks"), matching anchor 4 ("Clear sequence with most checkpoints present; minor validation gaps"). It falls short of anchor 5 because there is no explicit feedback loop for error recovery — e.g., no instruction on what to do when acceptance checks fail, only "Report any baseline failures separately from introduced failures".

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files (references/, scripts/, assets/ do not exist), and needs none — all content fits in well-organized sections (Tool routing, Workflow, Completion gates, Boundaries, Delivery) with no monolithic reference dumps. Per the scoring note for simple skills under 50 lines with no need for external references, this scores 5.

5 / 5

Total

17

/

20

Passed

Description

50%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 is clear and in third person with a well-defined 'what', but it omits any explicit 'Use when...' trigger clause, which caps completeness and limits natural keyword coverage. It is reasonably distinct from adjacent skills thanks to the 'production-oriented' and 'repository architecture' qualifiers, yet remains a broad domain where common user phrasings are absent.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to build, extend, or fix a feature in an existing web application, or mentions web app, frontend, UI, or user flows."

Include natural synonyms users would say ("web app", "frontend", "add a feature", "fix a bug in my app") to improve trigger term coverage.

Enumerate 1-2 more concrete actions (e.g., "add features, fix bugs, wire up APIs") to raise specificity beyond a generic build/modify pair.

DimensionReasoningScore

Specificity

"Build or modify production-oriented web applications" names the domain and a couple of concrete actions ("following the repository architecture", "validating real user flows"), but the action list is not comprehensive — no mention of specific tasks like adding features, fixing bugs, wiring APIs, or UI work. This matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive") better than anchor 4, which expects several distinct specific actions with only minor gaps.

3 / 5

Completeness

The 'what' is clear ("Build or modify production-oriented web applications by following the repository architecture and validating real user flows"), but there is no 'Use when...' clause or equivalent trigger guidance — the 'when' is only weakly implied by 'Build or modify'. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3, which is exactly the anchor: "Has a clear 'what' but 'when' is missing or only weakly implied".

3 / 5

Trigger Term Quality

Natural terms present include "web applications", "build", "modify", and "user flows", but common variations users would actually say are missing ("web app", "frontend", "add a feature", framework names, "website"). This fits anchor 3 ("Some relevant keywords but missing common variations or synonyms") more than anchor 4's "good keyword coverage; a few natural terms missing".

3 / 5

Distinctiveness Conflict Risk

The qualifiers "production-oriented", "following the repository architecture", and "validating real user flows" carve out a niche distinct from prototyping/design skills, but the domain is broad enough to overlap with general coding and debugging skills. Anchor 3 ("Somewhat specific but could still overlap with similar skills") fits; anchor 4 would require mostly-distinct triggers with only minor overlap risk, which the vague 'when' does not provide.

3 / 5

Total

12

/

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

KunAgent/Kun

Path

resources/bundled-skills/webapp-building/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.