CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nuxt-protokit

Use when building schema-driven prototypes with nuxt-protokit (@websideproject/nuxt-protokit) - provides definePrototype, usePrototype, ProtoTool, collections, derived values, and visualizations for rapid SaaS tool prototyping.

Quality

89%

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

86%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-structured library skill: an executable Quick Start, tight token budget, and exemplary progressive disclosure across eight real, one-level-deep reference files. The only flaws are minor — a duplicated navigation section and module config placed out of setup sequence.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude knows Nuxt/Vue, but the "Available Guidance" table and the "Progressive Loading" bullet list duplicate the same topic-to-file mapping, which is trimmable padding — matching anchor 4's 'minor instances of over-explanation that could be trimmed' rather than 5's 'every token earns its place'.

4 / 5

Actionability

The Quick Start is fully executable, copy-paste-ready code covering the canonical case end to end (a schema with number/range/select fields and a derived value, the page component, and the nuxt.config.ts module registration), matching anchor 5's 'fully executable; copy-paste ready; covers the common cases'.

5 / 5

Workflow Clarity

The define-schema → mount-ProtoTool flow is unambiguous and no destructive/batch operations require validation loops, but the required module registration (`modules: ['@websideproject/nuxt-protokit']`) is relegated to an appendix at the end instead of appearing in setup sequence — a minor sequencing gap that fits anchor 4 better than 5.

4 / 5

Progressive Disclosure

The body is a clear overview with well-signaled, one-level-deep links; all 8 referenced files (schema.md, composables.md, components.md, visualizations.md, offline-first.md, extensions.md, headless.md, module-authoring.md) exist in references/ with content appropriately split, and the explicit "DO NOT read all files at once" instruction plus task-based routing makes navigation easy — matching anchor 5.

5 / 5

Total

18

/

20

Passed

Description

87%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 description: explicit 'Use when' trigger tied to a specific package, a concrete inventory of the API surface, and no vague filler. Minor room to broaden natural synonyms (MVP, mockup) and mention the remaining capabilities like offline persistence or extensions.

DimensionReasoningScore

Specificity

"provides definePrototype, usePrototype, ProtoTool, collections, derived values, and visualizations" lists several concrete capabilities, but omits others the skill covers (offline persistence, encryption, headless mode, extensions), matching anchor 4's 'several specific actions; minor gaps' rather than 5's comprehensive coverage.

4 / 5

Completeness

It explicitly answers both parts: "Use when building schema-driven prototypes with nuxt-protokit" is a concrete when-clause, and "provides definePrototype, usePrototype, ProtoTool, collections, derived values, and visualizations" is an explicit what. This matches anchor 5 better than anchor 4, whose when-clause ('Use when working with PDF files') is notably more generic.

5 / 5

Trigger Term Quality

"building schema-driven prototypes", "rapid SaaS tool prototyping", and both package-name forms ("nuxt-protokit", "@websideproject/nuxt-protokit") give good natural keyword coverage, but common synonyms like "MVP", "mockup", or "dashboard builder" are missing, so it falls just short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description is anchored to a single named npm package with unambiguous triggers ("nuxt-protokit", "schema-driven prototypes"), giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

18

/

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/nuxt-protokit/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.