fastify-plugin-creator
Fastify Plugin Creator - Auto-activating skill for Backend Development. Triggers on: fastify plugin creator, fastify plugin creator Part of the Backend Development skill category.
35
3%
Does it follow best practices?
Impact
92%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/fastify-plugin-creator/SKILL.mdQuality
Discovery
7%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 essentially a title and category label with no substantive content. It fails to describe what the skill actually does, provides no natural trigger terms beyond the skill name repeated, and lacks any 'Use when...' guidance. It would be nearly useless for Claude to differentiate this skill from others in a large skill library.
Suggestions
Add concrete actions the skill performs, e.g., 'Creates Fastify plugins with proper encapsulation, registers routes, decorators, and hooks following Fastify plugin architecture patterns.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a Fastify plugin, register middleware, add route handlers, or build a Fastify server extension.'
Include common keyword variations users might say, such as 'fastify middleware', 'fastify decorator', 'fastify hooks', 'node.js API plugin', or 'fastify encapsulation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Fastify Plugin Creator') but does not describe any concrete actions like 'creates route handlers', 'registers plugins', 'configures hooks', etc. It is essentially just a title repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a redundant repetition of the skill name rather than explicit trigger guidance. Both what and when are very weak. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'fastify plugin creator' repeated twice. It misses natural user phrases like 'create a fastify plugin', 'fastify middleware', 'fastify route', 'node.js plugin', or 'fastify extension'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Fastify' provides some specificity that distinguishes it from generic backend or Express skills, but the lack of concrete actions means it could still overlap with other Fastify-related or general Node.js backend skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It consists entirely of boilerplate meta-descriptions about what the skill supposedly does, without any actual Fastify plugin creation guidance, code examples, or technical instructions. It provides zero value to Claude in performing the task it claims to support.
Suggestions
Add concrete, executable Fastify plugin code examples showing the fp() pattern, plugin registration, and decorator usage (e.g., `fastify-plugin` wrapper with proper encapsulation).
Define a clear workflow: 1) Create plugin file with fp() wrapper, 2) Register decorators/hooks, 3) Export with fastify-plugin, 4) Register in app—with validation steps like testing plugin isolation.
Remove all meta-description sections ('When to Use', 'Capabilities', 'Example Triggers') and replace with actionable technical content covering common plugin patterns (database connections, authentication, shared utilities).
Add specific examples of plugin options schemas, TypeScript type augmentation for decorators, and testing patterns for Fastify plugins.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section describes rather than instructs, wasting tokens on information Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of Fastify plugin structure, no API patterns. The content is entirely vague descriptions like 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-descriptions with no references to detailed materials, no links to examples or advanced guides, and no meaningful structural organization of actual content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3e83543
- 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.