framework-migration-assistant
Automatically migrate Python web applications between frameworks (Flask → FastAPI, Django → FastAPI). Use when you need to migrate an existing web application to a modern framework while preserving functionality. The skill analyzes the codebase, updates routes, handlers, configuration, dependency injection patterns, and tests. Creates git commits for each migration phase and generates a comprehensive summary of all changes. Supports automatic dependency updates, code transformations, and test adaptations.
89
86%
Does it follow best practices?
Impact
93%
1.24xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 articulates specific capabilities (framework migration, code analysis, route updates, git commits), includes natural trigger terms developers would use, and explicitly states when to use it. The description is comprehensive yet focused, with clear differentiation from other potential skills through its specific framework mentions and migration-focused scope.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'migrate Python web applications between frameworks', 'analyzes the codebase', 'updates routes, handlers, configuration, dependency injection patterns, and tests', 'Creates git commits', 'generates a comprehensive summary'. Very detailed and actionable. | 3 / 3 |
Completeness | Clearly answers both what ('migrate Python web applications between frameworks, analyzes codebase, updates routes...') AND when ('Use when you need to migrate an existing web application to a modern framework while preserving functionality'). Explicit trigger guidance is present. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'migrate', 'Flask', 'FastAPI', 'Django', 'web application', 'framework', 'routes', 'handlers', 'dependency injection', 'tests'. These are terms developers naturally use when discussing framework migration. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche: Python web framework migration specifically between Flask/Django to FastAPI. The specific framework names and migration-focused language make it highly unlikely to conflict with general Python skills or other web development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability and good progressive disclosure. The main weaknesses are moderate verbosity (some redundant explanations of the migration process) and missing explicit validation/error-recovery steps within the automated migration workflow, which is important for a potentially destructive batch operation.
Suggestions
Add explicit validation checkpoints within the migration phases (e.g., 'After Phase 3, run pytest to verify routes still work before proceeding to Phase 4')
Include error recovery guidance: what to do if a specific phase fails, how to rollback, and how to retry
Trim redundant explanations - the 'What gets migrated' lists and the Phase descriptions cover similar ground; consolidate or reference one from the other
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary verbosity, such as explaining what the migration process will do in multiple places and repeating information about the phases. The example output showing checkmarks is helpful but the overall document could be tightened. | 2 / 3 |
Actionability | Provides fully executable commands and concrete code examples throughout. The before/after Flask→FastAPI transformation is copy-paste ready, CLI commands are specific, and the individual migration module usage shows real Python imports and method calls. | 3 / 3 |
Workflow Clarity | The 6-phase migration process is clearly sequenced, and post-migration steps include running tests. However, there are no explicit validation checkpoints within the automated migration phases, and no feedback loops for error recovery if a phase fails. For a destructive batch operation like framework migration, this is a gap. | 2 / 3 |
Progressive Disclosure | Excellent structure with a quick start section, detailed phases, and clear one-level-deep references to external documentation (references/framework_comparison.md, migration_guide.md, migration_patterns.md). Content is appropriately split between overview and detailed reference files. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ArabelaTso/Skills-4-SE
- Commit
0f00a4f
- 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.