CtrlK
BlogDocsLog inGet started
Tessl Logo

data-client-vue-testing

Test @data-client/vue composables and components - renderDataCompose, mountDataClient, fixtures, jest, nock HTTP mocking, polling/subscription tests with fake timers, useSuspense, useLive, useSubscription, Vue 3 reactive props. Use when writing or debugging tests for composables or components built on @data-client/vue.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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-organized, highly actionable skill body built around executable code examples and a clean overview-to-reference split. The main weaknesses are minor redundancy across the Suspense sections and two reference bundle files that are broken stubs pointing to paths that do not exist.

Suggestions

Consolidate the useSuspense Promise->ComputedRef demonstration so the flow is shown once (e.g., in the 'Vue Suspense Behavior' section) and referenced from the other sections instead of re-demonstrated.

Replace the stub pointer text in references/Fixtures.md and references/unit-testing-hooks.md with actual content (or point them at files that exist), so the References links do not dead-end.

Add an explicit validation checkpoint reminder to the component-testing and mutation workflows (e.g., assert after waitForNextUpdate/nextTick and always call cleanup in afterEach) to bring their sequencing up to the polling section's standard.

DimensionReasoningScore

Conciseness

Mostly lean, code-first content that assumes Claude's competence (no generic explanations of Vue/jest), but the useSuspense Promise->ComputedRef flow is demonstrated in three separate sections, adding redundancy that could be consolidated.

4 / 5

Actionability

Fully executable, copy-paste-ready TypeScript examples cover the common cases (renderDataCompose, mountDataClient, fixtures/interceptors, mutations, controller.setResponse/fetch, polling with fake timers), with concrete option and return-value lists.

5 / 5

Workflow Clarity

The polling/subscription flow is an explicitly numbered sequence with validation checkpoints (useFakeTimers before mount, advanceTimersByTime, mutate+advance+await, restore real timers in afterEach), but most other sections are pattern recipes without explicit sequencing or feedback loops.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references (nock and polling/subscriptions split into referenced files with descriptive links), but two referenced bundle files (Fixtures.md, unit-testing-hooks.md) contain only broken relative pointers to a non-existent ../../../../docs path, so navigation partly dead-ends.

4 / 5

Total

17

/

20

Passed

Description

92%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, highly specific description that clearly states both capabilities and an explicit Use-when trigger, tightly scoped to the @data-client/vue testing niche. The only soft spot is trigger-term quality, which mixes natural phrases with internal API names rather than leaning fully on user language.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities and tooling (renderDataCompose, mountDataClient, fixtures, jest, nock HTTP mocking, polling/subscription tests with fake timers, useSuspense/useLive/useSubscription, Vue 3 reactive props), giving comprehensive coverage of the skill's testing actions.

5 / 5

Completeness

Explicitly answers both what ('Test @data-client/vue composables and components - ...') and when ('Use when writing or debugging tests for composables or components built on @data-client/vue') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('writing or debugging tests', 'composables or components', 'Vue 3 reactive props', 'jest', 'nock', 'polling/subscription'), but the trigger mix leans technical with API names (renderDataCompose, mountDataClient, useSuspense) rather than purely natural user phrasings, and a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Scoped to a single named library (@data-client/vue) with distinct, library-specific triggers, yielding a clear niche and minimal risk of firing for unrelated skills.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
reactive/data-client
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.