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.

1.00x

Quality

83%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

High

Do not use without reviewing

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-structured and actionable content with a clear validated workflow and good reference separation. The main weakness is redundant Best Practices/Tips sections that restate earlier material and slightly inflate token usage.

Suggestions

Consolidate the Best Practices and Tips sections into the existing Workflow/Checklist sections to remove redundancy and save tokens.

Add concrete before/after examples for the CircleCI→GitHub Actions and GitLab CI→GitHub Actions paths, which currently list only high-level steps.

Move the detailed Common Patterns mapping snippets into references/build-systems.md or references/ci-platforms.md to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Core workflow and examples are efficient, but the Best Practices and Tips sections largely restate content already covered in the Workflow, Checklist, and Validation Strategies sections, adding noticeable redundancy.	3 / 5
Actionability	Provides executable examples (Maven→Gradle XML/Groovy, Travis→GitHub Actions YAML, validation commands, caching/matrix mappings), though the CircleCI and GitLab migration paths offer only high-level steps without concrete examples.	4 / 5
Workflow Clarity	A clearly sequenced 5-step workflow includes an explicit 'Validate Migration' step, before/during/after checklists, and a Troubleshooting section that supplies fix-and-retry feedback loops for error recovery.	5 / 5
Progressive Disclosure	SKILL.md acts as an overview pointing to two verified one-level-deep references (build-systems.md, ci-platforms.md) that are clearly signaled, though some detailed Common Patterns mapping code is inlined rather than deferred.	4 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what the skill does and when to use it, with concrete actions and named migration paths. The only gap is the absence of file-extension trigger terms.

Suggestions

Add natural file-extension triggers (e.g., pom.xml, build.gradle, .travis.yml, .gitlab-ci.yml) so the description fires when users mention those files.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Analyzes existing configuration, generates equivalent target configuration, maps dependencies and commands, and provides validation and migration documentation' — with comprehensive coverage of the migration domain.	5 / 5
Completeness	Explicitly answers both 'what' (migrates build systems and CI/CD configurations to target platforms) and 'when' ('Use when modernizing build infrastructure, switching CI/CD providers, or standardizing across projects').	5 / 5
Trigger Term Quality	Includes natural trigger phrases ('modernizing build infrastructure', 'switching CI/CD providers') and many platform names, but omits file extensions like .travis.yml or pom.xml that users would naturally mention.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (build/CI migration) with named platform pairs and distinct triggers, making conflict with other skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ArabelaTso/Skills-4-SE
Path: skills/build-ci-migration-assistant/SKILL.md
Commit: 4f38503

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.