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 with no substantive content. It lacks concrete actions, natural trigger terms, and any 'Use when...' guidance. It would be nearly impossible for Claude to reliably select this skill from a pool of backend development skills based on this description alone.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Fastify plugins with proper registration, route handling, decorators, and hook lifecycle management.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a Fastify plugin, register routes in Fastify, add middleware to a Fastify server, or scaffold a Fastify project.'
Include common file types or patterns users might mention, such as '.ts plugin files', 'fastify-plugin wrapper', 'fp module', or 'Fastify decorators'.
| 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 with no actionable detail. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name and completely lacks a 'when should Claude use it' clause. There is no explicit trigger guidance or explanation of capabilities. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'fastify plugin creator' repeated twice. It misses natural user phrases like 'fastify plugin', 'create a plugin', 'fastify middleware', 'register plugin', 'fastify route', or '.ts/.js plugin file'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Fastify' provides some niche specificity that distinguishes it from generic backend skills, but the lack of concrete actions or clear scope means it could still overlap with other backend or Node.js plugin-related 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 actual instructional content. It consists entirely of boilerplate meta-descriptions about what the skill supposedly does, without providing any concrete guidance on creating Fastify plugins. It fails on every dimension because it contains no actionable information whatsoever.
Suggestions
Add a concrete quick-start example showing how to create a basic Fastify plugin with executable code (e.g., `fp(async function myPlugin(fastify, opts) { ... })`)
Include a clear workflow for plugin creation: scaffold → implement → register → test, with specific commands and validation steps
Remove all meta-description sections ('When to Use', 'Capabilities', 'Example Triggers') and replace with actual technical content covering plugin patterns like decorators, hooks, encapsulation, and error handling
Add specific code examples for common plugin patterns (database connection plugin, authentication plugin, etc.) that are copy-paste ready
| 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 specific Fastify plugin patterns, no API examples. The entire content is 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 flat, monolithic block of meta-descriptions with no meaningful structure. There are no references to detailed files, no quick-start section, and no navigation to deeper 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
3076d78
- 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.