vue-skill

Vue/TypeScriptの実装に関するAgent

Quality

32%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/vue-skill/SKILL.md

Quality

Discovery

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 severely underdeveloped, providing only a technology stack mention without any concrete capabilities or usage triggers. It fails to explain what specific tasks the skill performs (component creation, state management, testing, etc.) and provides no guidance on when Claude should select this skill over others.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates Vue 3 components with TypeScript, implements Composition API patterns, configures Vuex/Pinia stores'

Add an explicit 'Use when...' clause with trigger terms like 'Vue component', 'TypeScript setup', '.vue files', 'Composition API', 'Vue router'

Include common file extensions and framework-specific terminology users would mention, such as '.vue', 'SFC', 'script setup', 'defineProps'

Dimension	Reasoning	Score
Specificity	The description only mentions 'Vue/TypeScript implementation' without any concrete actions. It uses vague language ('Agent') and doesn't specify what operations it performs.	1 / 3
Completeness	Only vaguely addresses 'what' (implementation-related) and completely lacks any 'when' clause or explicit trigger guidance. No 'Use when...' or equivalent is present.	1 / 3
Trigger Term Quality	Contains relevant technology keywords 'Vue' and 'TypeScript' that users might naturally mention, but lacks common variations like '.vue files', 'components', 'composition API', or specific implementation tasks.	2 / 3
Distinctiveness Conflict Risk	Vue/TypeScript is somewhat specific as a technology combination, but 'implementation' is too broad and could overlap with general coding skills, frontend skills, or JavaScript-related skills.	2 / 3
	Total	6 / 12 Passed

Implementation

42%

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

This skill provides highly actionable Vue 3/TypeScript guidance with excellent code examples and clear patterns, but suffers from severe verbosity and poor progressive disclosure. The content explains many concepts Claude already understands and could be reduced by 60-70% while maintaining the same instructional value. The checklist approach is good but would benefit from validation checkpoints.

Suggestions

Reduce content by 60%+ by removing explanations of concepts Claude knows (what Composition API is, basic TypeScript, what Atomic Design means) and keeping only project-specific patterns and code examples

Split into multiple files: SKILL.md (overview + quick reference), PATTERNS.md (detailed code patterns), TESTING.md (test strategies), MIGRATION.md (React-to-Vue conversion)

Add explicit validation steps to workflows, e.g., 'After creating composable: 1. Run type check 2. Verify single responsibility 3. Test in isolation'

Convert the verbose Bad/Good examples into a concise reference table format that shows the pattern without lengthy explanations

Dimension	Reasoning	Score
Conciseness	The document is extremely verbose at 600+ lines, explaining many concepts Claude already knows (what Composition API is, basic TypeScript patterns, what Atomic Design is). Contains excessive repetition of principles and redundant examples that could be condensed significantly.	1 / 3
Actionability	Provides fully executable code examples throughout, with clear copy-paste ready snippets for Vue 3 patterns, composables, type definitions, and testing. The React-to-Vue migration table and conversion examples are concrete and immediately usable.	3 / 3
Workflow Clarity	Contains a comprehensive checklist at the end covering design, implementation, and testing stages, but lacks explicit validation checkpoints within workflows. The multi-step processes (like component creation) don't have clear feedback loops or verification steps.	2 / 3
Progressive Disclosure	The document is a monolithic wall of text with no references to external files for detailed content. The table of contents exists but all content is inline. Advanced topics like testing strategies and type patterns could be split into separate reference files.	1 / 3
	Total	7 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1026 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: h5y1m141/pedaru-vue
Commit: b4ee987

Reviewed: 29 days 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.