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.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugin/cloudbase/skills/web-development/SKILL.md

Quality

Content

70%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, actionable body with strong validation checkpoints and concrete commands, weakened by redundancy across overlapping workflow sections and references to bundle files (frameworks.md, browser-testing.md) that are not present in the skill.

Suggestions

Remove the duplicated History-mode/404 guidance — keep it in one place (static hosting) and cross-reference from the gotchas list.

Collapse the overlapping 'When to use', 'How to use', and 'Core workflow' sections into a single sequenced workflow to cut redundancy.

Either add the referenced frameworks.md and browser-testing.md to a references/ bundle or rephrase the pointers so they don't imply files that are missing.

Dimension	Reasoning	Score
Conciseness	Content is mostly value-dense project guidance rather than concept re-explanation, but the History-mode/404 point is repeated verbatim (gotchas and static-hosting sections) and 'When to use'/'How to use'/'Core workflow' overlap noticeably, so it could be tightened.	3 / 5
Actionability	Provides concrete executable commands (tsc --noEmit, npm run build, agent-browser), MCP tool-call JSON, and an SDK init snippet, with only minor gaps such as the truncated quick-start (`const auth = app.auth`).	4 / 5
Workflow Clarity	Numbered workflows plus an Engineering constitution with explicit static- and runtime-layer validation checkpoints and a feedback loop ('Only after both layers pass may you say the task is done') match the top anchor.	5 / 5
Progressive Disclosure	The body references frameworks.md and browser-testing.md as if they are local files, but no references/ bundle directory exists, and large sections (the TypeScript constitution, CloudBase integration) are inlined rather than split out.	3 / 5
	Total	15 / 20 Passed

Description

88%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 tight, third-person description that pairs an explicit 'Use when' trigger with a comprehensive list of concrete frontend engineering actions and named frameworks. It is held back only by missing synonyms/file extensions and minor overlap with adjacent design/frontend skills.

Dimension	Reasoning	Score
Specificity	Lists six concrete actions — 'implement, integrate, debug, build, deploy, or validate a Web frontend' — giving comprehensive coverage of the skill's capabilities rather than vague verbs.	5 / 5
Completeness	Explicitly answers both 'what' (the six frontend actions) and 'when' via a concrete 'Use when users need to…' trigger phrase, with the post-design-direction qualifier adding specificity.	5 / 5
Trigger Term Quality	Strong natural terms users would say ('React, Vue, Vite, browser flows, CloudBase Web integration'), but lacks synonyms and file extensions (e.g. .jsx, .vue) that would push it to a 5.	4 / 5
Distinctiveness Conflict Risk	The 'after the product direction is already clear' qualifier plus named frameworks carve a clear niche, but there is minor overlap risk with a general frontend or ui-design skill.	4 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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: plugin/cloudbase/skills/web-development/SKILL.md
Commit: ef9f182

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.