flask-blueprint-creator
Flask Blueprint Creator - Auto-activating skill for Backend Development. Triggers on: flask blueprint creator, flask blueprint creator Part of the Backend Development skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill flask-blueprint-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely lacking in all key areas. It reads like auto-generated boilerplate rather than a useful skill description, providing no concrete actions, no natural trigger terms, and no guidance on when to use it. The only distinguishing element is the Flask-specific terminology.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Flask blueprints with routes, models, and templates. Scaffolds modular Flask application structure with proper imports and configuration.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user wants to create a Flask blueprint, add a new module to a Flask app, scaffold Flask routes, or organize Flask code into blueprints.'
Include common user phrases and file extensions as triggers: 'flask app', 'blueprint', 'flask module', 'flask routes', '.py flask files', 'modular flask'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Flask Blueprint Creator') without describing any concrete actions. There's no explanation of what it actually does - no verbs like 'creates', 'generates', 'scaffolds', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Both what and when are missing or very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'flask blueprint creator' repeated twice, which is unlikely to match natural user language. Missing common variations like 'flask app', 'blueprint', 'flask routes', 'flask module', 'create flask endpoint'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Flask Blueprint' is somewhat specific to Flask framework, which provides some distinctiveness. However, 'Backend Development' is generic and could overlap with many other backend skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is entirely meta-description with zero actionable content. It describes what the skill supposedly does but provides no actual instructions, code examples, or guidance for creating Flask blueprints. The content is a template placeholder that would provide no value to Claude when performing the task.
Suggestions
Add executable Python code showing how to create a Flask blueprint with proper structure (e.g., `from flask import Blueprint; bp = Blueprint('name', __name__)`)
Include a concrete example of blueprint registration with the Flask app and route definitions
Provide a recommended file/folder structure for organizing blueprints in a Flask project
Remove all meta-description sections ('When to Use', 'Example Triggers') and replace with actual implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Flask blueprints. Phrases like 'automated assistance' and 'industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance on creating Flask blueprints. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process defined. The content only describes trigger phrases and capabilities without any actual instructions for creating Flask blueprints. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, examples, or related files. The content is a shallow placeholder with no depth or navigation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.