CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vueuse-functions

Apply VueUse composables where appropriate to build concise, maintainable Vue.js / Nuxt features.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./skills/vueuse-functions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is a well-executed catalog-style skill: a lean categorized index with concrete invocation rules that pushes all usage detail into 269 verified, one-level-deep reference files containing executable code. The main improvement opportunities are de-duplicating the "When to Apply" bullets and presenting the decision workflow as an explicit ordered sequence with a worked example.

DimensionReasoningScore

Conciseness

The body is a lean one-line-per-function index that assumes Vue knowledge and re-teaches nothing (e.g., "Reactive `Math.abs`", "Debounced watch"), and the reference files hold the detail. Minor trimming is possible: the four "When to Apply" bullets partly restate each other ("Always check first whether a VueUse function can implement the requirement" vs. "Prefer VueUse composables over custom code"), keeping it below anchor 5.

4 / 5

Actionability

Concrete dispatch rules are given (AUTO / EXTERNAL / EXPLICIT_ONLY with defined semantics and an example), plus the explicit instruction "always consult the corresponding document in `./references` for Usage details and Type Declarations" — and the referenced files contain complete, executable code. It falls short of anchor 5 only because the body itself contains no worked example of the end-to-end decision process (requirement → table lookup → reference consultation → implementation).

4 / 5

Workflow Clarity

The procedure is unambiguous and derivable in order: check whether a VueUse function applies, map the requirement via the categorized tables, consult the function's reference document, and follow its Invocation rule. No validation checkpoints are needed for this non-destructive decision-guide skill, but the sequence is presented as loose bullets rather than an ordered list, which fits anchor 4 better than 5.

4 / 5

Progressive Disclosure

The body is a pure overview/index and all detail lives exactly one level deep: all 269 linked `references/*.md` files were verified to exist, are organized into clearly labeled category tables, and contain no further nested reference chains (only external MDN links). This matches the anchor "Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation"; the only blemishes (one orphaned `templateRef.md` and a handful of functions linking to external docs instead of local references) are negligible.

5 / 5

Total

17

/

20

Passed

Description

61%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 concise and names a distinct niche (VueUse composables for Vue.js/Nuxt), but it lacks any explicit "Use when..." trigger guidance and describes only a single action padded with generic benefit language. Adding an explicit trigger clause and mentioning the breadth of the function catalog would materially improve it.

Suggestions

Add an explicit trigger clause, e.g., "Use when building or refactoring Vue 3 / Nuxt 3 features where a composable could replace custom code for state, browser APIs, sensors, network, animation, or utilities."

Make the capability concrete and comprehensive instead of outcome-focused: mention that the skill maps requirements to 270+ VueUse functions and applies per-function usage patterns, rather than "build concise, maintainable features".

Include natural keyword variations users would say, such as "composition API", "Vue 3", "Nuxt 3", or "@vueuse/core", to strengthen trigger matching.

DimensionReasoningScore

Specificity

"Apply VueUse composables" is one concrete action with a named domain, but the remainder ("where appropriate to build concise, maintainable Vue.js / Nuxt features") is generic outcome language, so coverage is not comprehensive. It is above anchor 2 because a real action and domain are named, but below anchor 4 because only a single action is specified.

3 / 5

Completeness

The "what" is clear (apply VueUse composables), but there is no "Use when..." clause; the timing is only weakly implied by "where appropriate", which caps completeness at 3 per the judging guidelines. Not 2 because the "what" is concrete; not 4 because no explicit trigger guidance exists at all.

3 / 5

Trigger Term Quality

Natural terms a user would say are present: "VueUse composables", "Vue.js", "Nuxt". A few natural variations are missing, such as "composition API", "Vue 3", or the package name "@vueuse/core", keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

"VueUse composables" carves a clear niche with distinct triggers, but "build concise, maintainable Vue.js / Nuxt features" is broad enough to overlap with general Vue development skills. Mostly distinct with minor overlap risk, fitting anchor 4 rather than 5.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

onmax/nuxt-skills

Path

skills/vueuse-functions/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.