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.

77

Quality

96%

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

92%

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

A strong, highly actionable skill body with executable examples and clear sequenced workflows for async/polling testing. The main weakness is progressive disclosure: two of the four referenced files are empty stub redirects, and some detail could be split out.

Suggestions

Replace the empty Fixtures.md and unit-testing-hooks.md stubs (which only redirect to ../../../../docs/...) with either real content or direct links to the canonical docs, so references resolve one level deep.

Consider moving the long Options/Return-values API listings for renderDataCompose/mountDataClient into a reference file, keeping SKILL.md as a concise overview.

Verify each in-body reference link points to an existing file with substantive content rather than a forwarding stub.

DimensionReasoningScore

Conciseness

The body is lean and example-driven: it assumes Claude's competence, avoids explaining what Vue/Suspense/Jest are, and every section delivers executable patterns without padding.

3 / 3

Actionability

Provides fully executable, copy-paste-ready TypeScript snippets for every pattern (renderDataCompose, mountDataClient, flushUntil, reactive props, fixtures, mutations, nock, fake timers) with concrete options and return values listed.

3 / 3

Workflow Clarity

Multi-step processes are explicitly sequenced with checkpoints — the polling section lists numbered steps with fake-timer ordering and restore-in-afterEach, and async tests show waitForNextUpdate/allSettled/nextTick feedback loops.

3 / 3

Progressive Disclosure

Detailed nock and polling material is correctly offloaded to one-level-deep references, but Fixtures.md and unit-testing-hooks.md are non-content symlink stubs pointing elsewhere, and the inline body is long with some reference-worthy API detail still embedded.

2 / 3

Total

11

/

12

Passed

Description

100%

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 specific, action-oriented, and well-triggered, naming concrete helpers and a clear 'Use when' clause scoped to @data-client/vue. It is dense but every term earns its place and is written in third person.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and APIs — "renderDataCompose, mountDataClient, fixtures, jest, nock HTTP mocking, polling/subscription tests with fake timers, useSuspense, useLive, useSubscription, Vue 3 reactive props" — rather than vague language.

3 / 3

Completeness

Clearly answers both what it does (test composables/components via the listed helpers) and when to use it ("Use when writing or debugging tests for composables or components built on @data-client/vue"), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Natural trigger terms a user would say are well covered: "writing or debugging tests for composables or components", "jest", "nock", "fixtures", plus the framework-specific composable names.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to @data-client/vue testing with distinct named APIs, making it unlikely to trigger for unrelated Vue or general testing skills.

3 / 3

Total

12

/

12

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.