build-ci-migration-assistant
Assists migrating a build or CI pipeline from one system to another — Jenkins to GitHub Actions, Travis to GitLab CI, Makefile to Bazel — preserving semantics and surfacing untranslatable constructs. Use when switching CI providers, when modernizing a legacy build, or when the user pastes a Jenkinsfile and asks for the GitHub Actions equivalent.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill build-ci-migration-assistant100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 defines its purpose (CI/build migration), provides concrete examples of source-to-target migrations, and includes explicit trigger conditions. The description uses proper third-person voice and covers both the 'what' and 'when' comprehensively with natural user terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'migrating a build or CI pipeline', 'preserving semantics', 'surfacing untranslatable constructs', with specific examples like 'Jenkins to GitHub Actions, Travis to GitLab CI, Makefile to Bazel'. | 3 / 3 |
Completeness | Clearly answers both what ('migrating build/CI pipelines, preserving semantics, surfacing untranslatable constructs') and when ('switching CI providers, modernizing legacy build, user pastes Jenkinsfile asking for GitHub Actions equivalent'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Jenkins', 'GitHub Actions', 'Travis', 'GitLab CI', 'Makefile', 'Bazel', 'Jenkinsfile', 'CI pipeline', 'build', 'switching CI providers', 'legacy build'. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on CI/build system migration between named platforms. Unlikely to conflict with general coding skills or individual CI platform skills due to the explicit migration focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that treats CI migration as a translation problem with a clear methodology. The concept map table is particularly valuable for quick reference, the worked example demonstrates the full process end-to-end, and the 'untranslatables' section shows sophisticated awareness of where migrations fail. The output format template ensures consistent, verifiable results.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for dense information delivery. No unnecessary explanations of what CI systems are or how they work—assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides a complete worked example with real Jenkinsfile and GitHub Actions YAML that are copy-paste ready. The concept map table gives concrete mappings, and the output format template is immediately usable. | 3 / 3 |
Workflow Clarity | Clear 3-step process (extract DAG → translate via concept map → flag untranslatables) with explicit verification plan at the end. The 'Do not' section provides guardrails, and the recommendation to run both pipelines in parallel is a proper validation checkpoint. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (concept map, steps, worked example, anti-patterns, output format). Content is appropriately self-contained for a skill of this scope—no need for external references, and the structure allows quick navigation. | 3 / 3 |
Total | 12 / 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.
- 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.