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

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

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, highly actionable body with strong validation workflows and clear references. Its chief weakness is redundancy: the trigger and validation guidance is repeated across several sections and could be consolidated to recover token budget.

Suggestions

Consolidate the validation/browser-testing guidance into a single source of truth (Engineering constitution §2) and have other sections reference it rather than restating the tsc/eslint/build/agent-browser checks each time.

Merge 'When to use this skill' into the Activation Contract (or replace it with a one-line pointer) to eliminate the near-duplicate trigger listing.

Complete the CloudBase quick-start code block (e.g. finish the auth line with app.auth() and a login call) so the example is copy-paste runnable.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's intelligence with no concept padding, but validation/browser-testing guidance is restated four times (Activation Contract gotchas, Engineering constitution §2, 'How to use' step 3, 'Core workflow' step 3) and 'When to use this skill' largely duplicates the Activation Contract, so it could be tightened.	3 / 5
Actionability	Provides concrete commands (tsc --noEmit, npm run build, npm install @cloudbase/js-sdk) and MCP JSON examples (manageHosting, queryHosting), but the quick-start code is truncated ('const auth = app.auth') leaving a minor gap.	4 / 5
Workflow Clarity	Sequences work clearly with explicit validation checkpoints across static (tsc/eslint/build/tests) and runtime (agent-browser) layers, a gated 'Only after both layers pass' rule, and a feedback loop for unverifiable steps, matching the explicit-validation-with-feedback anchor.	5 / 5
Progressive Disclosure	Well-organized sections with one-level-deep, clearly signaled references (-> frameworks.md, browser-testing.md, sibling skills); no bundle files exist in the package, and some dense inline content (CloudBase integration, engineering constitution) could arguably be split out.	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, third-person description that explicitly covers both capability and trigger conditions with concrete framework keywords. The main gap is that the action verbs are somewhat abstract and a few natural synonyms are missing.

Dimension	Reasoning	Score
Specificity	Lists six concrete engineering actions (implement, integrate, debug, build, deploy, validate) on a named Web-frontend domain, but the verbs remain fairly high-level rather than fully concrete operations, fitting the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.	4 / 5
Completeness	Explicitly answers both what (implement/integrate/debug/build/deploy/validate a Web frontend) and when ('Use when users need to...', with framework triggers and the 'after the product direction is already clear' condition), matching the clearly-explicit-both anchor.	5 / 5
Trigger Term Quality	Strong natural keywords users would say (React, Vue, Vite, CloudBase Web integration); 'browser flows' is slightly unnatural and common terms like frontend, SPA, or UI are absent, so it sits just below the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	Carves a clear Web-frontend-engineering niche separated from ui-design, miniprogram, and backend work, but the generic implement/build/deploy verbs carry some overlap risk with general coding skills, keeping it just below the minimal-conflict 5.	4 / 5
	Total	17 / 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: f07c33c

Reviewed: 4 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.