CtrlK
BlogDocsLog inGet started
Tessl Logo

vue-best-practices

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

47

Quality

50%

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 ./bcs-services/bcs-project-manager/.cursor/skills/vue-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-organized index of Vue tooling rules with clear signaling, but it offers no executable guidance, no real workflow, and its progressive-disclosure references point to rule files that are absent from the bundle. The duplicated resource URI list adds redundant tokens.

Suggestions

Ship the referenced rules/*.md files (or move them into references/) so the skill:// links resolve; a broken reference index undermines progressive disclosure.

Add the IF-THEN keyword-to-rule loading logic the body claims to use, or a short concrete workflow for diagnosing a Vue type/template error end-to-end with a validation step.

Remove the duplicated '可用资源' URI list since every path is already linked in the rule tables, or replace the tables with the URI list to avoid restating both.

DimensionReasoningScore

Conciseness

The rule tables are reasonably lean, but the '可用资源' section re-lists all 17 rule paths as skill:// URIs that already appear in the tables above, which is redundant padding that could be tightened.

3 / 5

Actionability

The body only catalogues rules with one-line descriptions ('Catch undefined components in templates', 'Type-check fallthrough attributes') and provides no executable code, commands, or concrete fix steps; the actual guidance is deferred to rule files that are not present in the bundle.

2 / 5

Workflow Clarity

No multi-step workflow is defined; the Chinese note references 'IF-THEN rules' in SKILL.md to decide loading, but no such IF-THEN rules exist in the body, leaving only a rough implied match-keyword-then-load sequence with no validation checkpoints.

2 / 5

Progressive Disclosure

The overview-into-rule-files structure is clearly signaled with one-level-deep references, but the referenced rules/*.md files do not exist in the bundle (no references/, scripts/, assets/, or rules/ directories), so the navigation points to dangling targets and cannot fully deliver.

3 / 5

Total

10

/

20

Passed

Description

65%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 a concise keyword list naming a distinct Vue 3 tooling niche with good trigger terms, but it omits any 'Use when...' trigger clause and never states the action the skill performs. Completeness is capped at 3 as a result.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when debugging Vue 3 type errors, vue-tsc/Volar template issues, or Vite plugin conflicts.'

State the action verb up front, e.g. 'Diagnoses and fixes Vue 3 TypeScript, vue-tsc, Volar, and Vite configuration issues.'

Consider including natural symptom phrases users say ('undefined component', 'cannot find module', 'slow save') to broaden trigger coverage.

DimensionReasoningScore

Specificity

The phrase 'Vue 3 TypeScript, vue-tsc, Volar, Vite, component props, testing, composition API' names the domain and several concrete topics, but lists tools/topics rather than describing concrete actions (e.g. fix, configure, type-check), so it sits between the '1-2 concrete actions' (3) and 'several specific actions' (4) anchors.

3 / 5

Completeness

Per the guideline, a missing 'Use when...' clause caps completeness at 3; the description has an implied 'what' (best practices across these tools) but no explicit trigger guidance and no stated action verb, so it cannot exceed 3.

3 / 5

Trigger Term Quality

It includes natural terms a Vue developer would actually say ('Vue 3', 'TypeScript', 'vue-tsc', 'Volar', 'Vite', 'component props', 'composition API'), giving good keyword coverage, though a few common synonyms or file extensions are missing.

4 / 5

Distinctiveness Conflict Risk

The Vue 3 + vue-tsc + Volar + Vite toolchain is a clear, distinct niche with specific triggers and minimal overlap risk with other skills.

5 / 5

Total

15

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 17 missing

Warning

Total

15

/

16

Passed

Repository
TencentBlueKing/bk-bcs
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.