CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

web-development

Use when users need to implement, integrate, debug, build, deploy, or validate a Web frontend after the product direction is already clear, especially for React, Vue, Vite, browser flows, or CloudBase Web integration.

65

Quality

82%

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

The canonical home for this skill is web-development in TencentCloudBase/CloudBase-AI-Toolkit

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 well-structured engineering skill with genuinely strong validation gates, executable commands, and well-signaled reference pointers. Its main weakness is redundancy — the browser-validation mandate and the SPA 404 gotcha are each stated multiple times, and "How to use this skill" and "Core workflow" substantially overlap.

Suggestions

State the History-mode SPA 404 rule once (in Static hosting defaults, where the manageHosting fix lives) and reduce the 'Common mistakes' entry to a one-line pointer, eliminating the duplicated NoSuchKey explanation.

Merge 'How to use this skill' and 'Core workflow' into a single canonical workflow; they currently repeat the same clarify/conventions/validate/CloudBase-branch sequence, and consolidate the browser-validation mandate into one place (the Engineering constitution).

Fix or complete the quick-start snippet's `const auth = app.auth` line, and give `frameworks.md` / `browser-testing.md` explicit in-bundle paths (e.g., `references/frameworks.md`) so the pointers resolve without the full plugin installed.

DimensionReasoningScore

Conciseness

The body is dense with earned, non-obvious directives (no padding explaining what React or Vite is), but several sections repeat the same guidance: the History-mode SPA 404 gotcha is fully explained twice ("Common mistakes" and "Static hosting defaults"), browser-level validation is admonished in four places (Activation Contract, Engineering constitution, "How to use", "Core workflow"), and the ui-design warning appears twice. This matches anchor 3 — mostly efficient but includes unnecessary duplication that could be tightened into one canonical statement.

3 / 5

Actionability

Largely executable guidance: exact commands (`tsc --noEmit`, `vue-tsc --noEmit`, `npm install @cloudbase/js-sdk`), copy-paste MCP snippets with a verify step (`manageHosting({ action: "setWebsiteDocument", ... })` then `queryHosting({ action: "websiteConfig" })`), and a concrete quick-start code block. Minor gaps keep it below anchor 5: the quick-start's `const auth = app.auth` line is truncated/incomplete, and the browser-testing workflow is delegated to `browser-testing.md`, which is not present alongside the skill.

4 / 5

Workflow Clarity

The sequence is clear (clarify execution surface → follow conventions → validate → CloudBase as a late branch) with explicit validation checklists in both layers: static (tsc/eslint/build/tests) and runtime (agent-browser route/interaction/console checks), a hard gate ("Only after both layers pass may you say the task is done"), error-recovery direction ("If either layer cannot be executed locally... list exactly which step is still unverified"; "fix the root cause" / do not delete failing tests), and a record-what-you-checked step. This matches anchor 5's explicit validation steps, feedback loops, and checklists.

5 / 5

Progressive Disclosure

Good structure: rules and gotchas live inline, deeper material is clearly signaled one level deep ("General React / Vue / Vite guidance -> `frameworks.md`", "Browser flow checks or page validation -> `browser-testing.md`"), and sibling skills are addressed by name with a stated fallback if missing. Minor gaps: `frameworks.md` and `browser-testing.md` have no resolvable path in this bundle, and the cross-cutting protocols are referenced only through sibling-skill relative paths, so navigation depends on files outside the skill.

4 / 5

Total

16

/

20

Passed

Description

83%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 strong, trigger-first description with explicit what/when guidance, natural framework keywords, and a clear engineering-vs-design boundary. Its only gaps are a few missing synonyms ("frontend", "SPA", "static site") and implicit rather than named exclusion of adjacent skills.

DimensionReasoningScore

Specificity

The description lists several specific concrete actions — "implement, integrate, debug, build, deploy, or validate a Web frontend" — comparable to the anchor-4 example of several specific actions with minor coverage gaps (e.g., routing, forms, and static-site work appear only in the body). It falls short of anchor 5 because all actions share the single object "Web frontend" rather than spanning a comprehensive set of distinct capabilities.

4 / 5

Completeness

It explicitly answers both questions: what the skill does ("implement, integrate, debug, build, deploy, or validate a Web frontend") and when to use it, with concrete trigger phrases ("Use when users need to... especially for React, Vue, Vite, browser flows, or CloudBase Web integration") plus an explicit scoping condition ("after the product direction is already clear"). This matches the anchor-5 pattern of concrete what-and-when guidance; anchor 4's deficiency (an only-weakly-specified "when") does not apply.

5 / 5

Trigger Term Quality

Strong natural keyword coverage: "React, Vue, Vite, browser flows, or CloudBase Web integration" plus "deploy", "build", and "debug" are terms users would naturally say. It misses a few common synonyms and variations ("frontend", "SPA", "static site", "website"), which keeps it at anchor 4 rather than the comprehensive synonym/extension coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The stack-specific triggers ("React, Vue, Vite", "CloudBase Web integration") and the qualifier "after the product direction is already clear" carve out a distinct engineering-execution niche versus design skills. Minor overlap risk remains with closely related skills (ui-design, miniprogram-development) that the description distinguishes only implicitly, so it does not reach the clear-niche bar of anchor 5.

4 / 5

Total

17

/

20

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.

Validation — 15 / 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

TencentCloudBase/CloudBase-AI-Toolkit

Path

config/.claude/skills/web-development/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.