vue-nuxt

Vue 3 and Nuxt 3 for JARVIS AI Assistant UI development with security-first patterns

Quality

49%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/vue-nuxt/SKILL.md

Quality

Content

77%

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

This is a strong, actionable skill with excellent executable code examples and clear TDD workflow. The security-first approach is well-documented with concrete patterns. Main weaknesses are moderate verbosity (overview sections, some redundancy) and the file being longer than ideal for a SKILL.md overview - more content could be delegated to reference files.

Suggestions

Move detailed CVE tables and OWASP coverage to references/security-examples.md, keeping only a brief 'update to Nuxt 3.12.4+ for security fixes' note in the main file

Remove or condense the Overview section (section 1) - the description in frontmatter should suffice, and Claude doesn't need explanations of what Vue/Nuxt are for

Dimension	Reasoning	Score
Conciseness	The skill contains some unnecessary explanations (e.g., 'This skill provides expertise for building...', overview sections) and could be tightened. However, most code examples are lean and the tables are efficient. Some redundancy exists between sections (security patterns repeated in multiple places).	2 / 3
Actionability	Excellent executable code examples throughout - complete Vue components with script setup, TypeScript interfaces, server routes with Zod validation, test examples, and bash commands. All code is copy-paste ready with proper imports and context.	3 / 3
Workflow Clarity	Clear TDD workflow with explicit steps (write failing test → implement minimum → refactor → verify). The pre-deployment checklist provides explicit validation checkpoints. API integration and component workflows are well-sequenced with numbered steps.	3 / 3
Progressive Disclosure	References to external files (references/advanced-patterns.md, references/security-examples.md) are mentioned but the main file is quite long (~400 lines). Some content like the full CVE table and detailed security examples could be moved to reference files. The structure is good but the file tries to be comprehensive rather than an overview.	2 / 3
	Total	10 / 12 Passed

Description

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too terse and lacks actionable detail. It names technologies but fails to specify concrete capabilities or provide trigger guidance for when Claude should use this skill. The 'security-first patterns' claim is vague and unsupported by specific actions.

Suggestions

Add a 'Use when...' clause specifying triggers like 'Vue components', 'Nuxt pages', 'frontend for JARVIS', or 'UI security patterns'

List specific concrete actions such as 'Create Vue 3 components, configure Nuxt 3 routing, implement authentication flows, build reactive UI elements'

Include natural user terms like 'frontend', 'components', 'pages', 'composables', 'SSR' that users would actually say when needing this skill

Dimension	Reasoning	Score
Specificity	The description names technologies (Vue 3, Nuxt 3) and a domain (UI development) but provides no concrete actions. 'Security-first patterns' is vague and doesn't specify what actions Claude can perform.	1 / 3
Completeness	The description only partially addresses 'what' (UI development) and completely lacks a 'when' clause. There's no explicit guidance on when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'Vue 3', 'Nuxt 3', and 'UI development' that users might mention, but 'JARVIS AI Assistant' is project-specific jargon and common variations like 'frontend', 'components', 'SPA' are missing.	2 / 3
Distinctiveness Conflict Risk	The combination of Vue 3, Nuxt 3, and the specific project name 'JARVIS' provides some distinctiveness, but 'UI development' is generic enough to potentially conflict with other frontend skills.	2 / 3
	Total	6 / 12 Passed

Validation

68%

Warnings & errors only

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

Validation — 11 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (659 lines); consider splitting into references/ and linking	Warning
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	11 / 16 Passed

Repository: martinholovsky/claude-skills-generator
Commit: 1086ef2

Reviewed: 5 months ago

Table of Contents

Discovery Implementation Validation

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.