vue-best-practices

Vue 3 TypeScript, vue-tsc, Volar, Vite, component props, testing, composition API.

Quality

33%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./bcs-services/bcs-project-manager/.cursor/skills/vue-best-practices/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is essentially a keyword dump of Vue ecosystem technologies without explaining capabilities or usage triggers. It fails to communicate what actions the skill enables Claude to perform and provides no guidance on when to select this skill over others. The lack of verbs and explicit trigger conditions makes it difficult for Claude to make informed skill selection decisions.

Suggestions

Add concrete action verbs describing what the skill does, e.g., 'Build Vue 3 components, configure Vite projects, write composition API code, set up vue-tsc type checking'

Include an explicit 'Use when...' clause with trigger conditions, e.g., 'Use when the user asks about Vue.js development, .vue files, Vue components, or Vite configuration'

Add natural language variations users might say, such as 'Vue app', 'Vue project', 'single file components', 'SFC', or 'Vue frontend'

Dimension	Reasoning	Score
Specificity	The description is a comma-separated list of technologies and concepts (Vue 3, TypeScript, Vite, etc.) but contains no concrete actions or verbs describing what the skill actually does.	1 / 3
Completeness	The description only lists technologies without explaining what actions the skill performs or when Claude should use it. There is no 'Use when...' clause or equivalent guidance.	1 / 3
Trigger Term Quality	Contains relevant technical keywords users might mention (Vue 3, TypeScript, Vite, composition API, component props) but lacks common variations or natural phrases like 'Vue app', 'Vue project', '.vue files', or 'single file components'.	2 / 3
Distinctiveness Conflict Risk	The Vue 3 focus provides some distinction from general JavaScript/TypeScript skills, but 'TypeScript' and 'testing' are generic enough to potentially conflict with other skills covering those domains.	2 / 3
	Total	6 / 12 Passed

Implementation

44%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill functions as a well-organized index/table of contents for Vue best practices rules, with excellent progressive disclosure and conciseness. However, it lacks any actionable content in the main file itself - no quick-start examples, no workflow guidance, and no concrete instructions. Users must navigate to linked files for any actual guidance.

Suggestions

Add a 'Quick Start' section with 1-2 concrete examples of the most common issues and their solutions directly in SKILL.md

Include a brief workflow section explaining when to consult this skill (e.g., 'When encountering Vue/TypeScript errors, check the Keywords column to find relevant rules')

Add at least one executable code snippet demonstrating a common fix (e.g., the vue-tsc strict templates configuration)

Dimension	Reasoning	Score
Conciseness	The content is extremely lean - just organized tables with rule names, keywords, and brief descriptions. No unnecessary explanations or padding; every element serves navigation purposes.	3 / 3
Actionability	The SKILL.md provides no concrete guidance, code examples, or executable instructions. It's purely an index/table of contents with no actionable content - all actual guidance is deferred to linked files.	1 / 3
Workflow Clarity	There is no workflow described. The content is a static index with no sequencing, no process steps, and no guidance on when or how to apply these rules in a development workflow.	1 / 3
Progressive Disclosure	Excellent structure with clear categorization (Capability Rules, Efficiency Rules), well-organized tables with keywords for discovery, and one-level-deep references to detailed rule files.	3 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: TencentBlueKing/bk-bcs
Commit: b08ac38

Reviewed: about 2 months 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.