flask
Build Python web apps with Flask using application factory pattern, Blueprints, and Flask-SQLAlchemy. Prevents 9 documented errors including stream_with_context teardown issues, async/gevent conflicts, and CSRF cache problems. Use when: creating Flask projects, organizing blueprints, or troubleshooting circular imports, context errors, registration, streaming, or authentication.
87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 is an excellent skill description that clearly communicates both capabilities and usage triggers. It uses third person voice, lists specific technical patterns and error types, and provides comprehensive trigger terms that developers would naturally use. The explicit 'Use when:' clause with multiple scenarios makes it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and patterns: 'application factory pattern, Blueprints, Flask-SQLAlchemy' plus specific error types like 'stream_with_context teardown issues, async/gevent conflicts, CSRF cache problems'. | 3 / 3 |
Completeness | Clearly answers both what (build Flask apps with specific patterns, prevent documented errors) AND when (explicit 'Use when:' clause with multiple trigger scenarios including creating projects, organizing blueprints, and troubleshooting specific issues). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Flask projects', 'blueprints', 'circular imports', 'context errors', 'streaming', 'authentication', plus technical terms like 'Flask-SQLAlchemy' that developers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Flask-specific terminology, named patterns, and specific error types. Unlikely to conflict with generic Python or web development skills due to the explicit Flask focus and detailed error categories. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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 high-quality, actionable Flask skill with excellent executable code examples and clear workflow patterns. The Known Issues section is particularly valuable for preventing real-world problems. However, the document is quite long and could be more concise by trimming explanations of concepts Claude already knows and potentially splitting detailed reference content into separate files.
Suggestions
Consider moving the 9 Known Issues to a separate KNOWN_ISSUES.md file with a brief summary in the main skill, reducing the main document length significantly
Remove explanatory comments that state the obvious (e.g., '# Import routes after bp is created!' - the code structure already shows this)
Trim verbose explanations like 'Why separate file?: Prevents circular imports' - Claude understands this pattern
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbose explanations that Claude would already know (e.g., explaining what circular imports are, why to use environment variables). The 9 known issues section is valuable but could be more condensed, and some code comments are redundant. | 2 / 3 |
Actionability | Excellent executable code throughout - all examples are copy-paste ready with complete imports, proper syntax, and runnable commands. The project structure, patterns, and error fixes all provide concrete, working code rather than pseudocode. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation and sequencing. The Known Issues section provides clear problem-solution patterns with 'WRONG' vs 'RIGHT' examples. Project setup, testing, and deployment all have clear step sequences. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but it's a monolithic document that could benefit from splitting detailed content (like the 9 known issues) into separate reference files. The References section links to external docs but internal content organization could be improved. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (854 lines); consider splitting into references/ and linking | 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 | 12 / 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.