build-ci-migration-assistant
Automatically migrates build systems and CI/CD configurations to target platforms. Use when modernizing build infrastructure, switching CI/CD providers, or standardizing across projects. Supports common migration paths including Maven↔Gradle, npm↔Yarn, Travis CI→GitHub Actions, CircleCI→GitHub Actions, Jenkins→GitLab CI, and GitLab CI→GitHub Actions. Analyzes existing configuration, generates equivalent target configuration, maps dependencies and commands, and provides validation and migration documentation.
95
92%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
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 hits all the marks. It provides specific concrete actions, comprehensive trigger terms covering major build tools and CI/CD platforms, explicit 'Use when' guidance, and a clearly defined niche that distinguishes it from general development or DevOps skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Analyzes existing configuration, generates equivalent target configuration, maps dependencies and commands, and provides validation and migration documentation.' Also enumerates specific migration paths (Maven↔Gradle, npm↔Yarn, etc.). | 3 / 3 |
Completeness | Clearly answers both what ('migrates build systems and CI/CD configurations') and when ('Use when modernizing build infrastructure, switching CI/CD providers, or standardizing across projects') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'build systems', 'CI/CD', 'Maven', 'Gradle', 'npm', 'Yarn', 'Travis CI', 'GitHub Actions', 'CircleCI', 'Jenkins', 'GitLab CI', 'migration', 'modernizing build infrastructure'. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on build system and CI/CD migrations with explicit platform pairs listed. Unlikely to conflict with general coding skills or other infrastructure tools due to the specific migration focus and named platforms. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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 excellent workflow clarity and actionability. The concrete examples and validation strategies are strong. However, there's some verbosity in the troubleshooting, best practices, and tips sections that could be consolidated, and some content explains concepts Claude already knows (like listing what files each build system uses).
Suggestions
Consolidate the 'Best Practices', 'Tips', and parts of 'Troubleshooting' sections to reduce redundancy - these overlap significantly
Remove the explicit listing of configuration file names for each build system/CI platform (e.g., 'Maven (pom.xml)') as Claude already knows these associations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some redundancy. The troubleshooting section, best practices, and tips sections overlap significantly. Lists of build systems and CI platforms that Claude would recognize are somewhat unnecessary. | 2 / 3 |
Actionability | Provides concrete, executable examples throughout. The Maven-to-Gradle and Travis-to-GitHub Actions examples show exact input/output transformations with copy-paste ready code. Validation commands are specific and executable. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit validation phase. Includes multiple validation strategies (dry run, parallel running, incremental) and comprehensive checklists for before/during/after migration. Feedback loops are present for error recovery. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview and appropriately references external files (references/build-systems.md, references/ci-platforms.md) for detailed mappings. Content is organized into logical sections with one-level-deep references. | 3 / 3 |
Total | 11 / 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.