Execute build/test commands and return structured summaries. Use for Maven, Node, or Python builds during dependency remediation. Use when the user says "build", "compile", "test", "verify", "run tests", "maven verify", "unit tests", or "build summary". Not for: deployment, CI/CD pipeline management, or code generation.
EnglishFork management lifecycle for Azure OSDU SPI service forks — three-branch strategy, upstream sync, cascade integration, conflict resolution, template propagation, and multi-repo status monitoring across 8 service forks. Use when checking sync status, reviewing cascades, resolving conflicts, triggering manual syncs, managing forkupstream/forkintegration/main branches, or coordinating template updates across osdu-spi- repos. Not for: infrastructure deployment (use iac skill), OSDU GitLab services (use osdu plugin), or tool installation (use setup skill).
EnglishFix FOSSA NOTICE file from failed MR pipeline. Downloads the updated NOTICE artifact from a GitLab CI fossa-check-notice job and commits it. Use when the user mentions FOSSA failure, NOTICE file update, fossa-check-notice job failure, or needs to fix a FOSSA pipeline error. Not for: license scanning setup, dependency vulnerability analysis (use maven scan), or general pipeline debugging (use glab).
EnglishOSDU QA Testing - Environment management, API test execution, failure analysis, and report generation. Use when running OSDU API tests, analyzing failures, comparing environments, generating QA reports, or managing test environments. Not for: unit testing application code or build compilation (use build-runner instead).
EnglishIncludes Build Runner and other workflows.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Build Runner
Execute build/test commands and return structured summaries. Use for Maven, Node, or Python builds during dependency remediation. Use when the user says "build", "compile", "test", "verify", "run tests", "maven verify", "unit tests", or "build summary". Not for: deployment, CI/CD pipeline management, or code generation.
Forks
Fork management lifecycle for Azure OSDU SPI service forks — three-branch strategy, upstream sync, cascade integration, conflict resolution, template propagation, and multi-repo status monitoring across 8 service forks. Use when checking sync status, reviewing cascades, resolving conflicts, triggering manual syncs, managing forkupstream/forkintegration/main branches, or coordinating template updates across osdu-spi- repos. Not for: infrastructure deployment (use iac skill), OSDU GitLab services (use osdu plugin), or tool installation (use setup skill).
Fossa
Fix FOSSA NOTICE file from failed MR pipeline. Downloads the updated NOTICE artifact from a GitLab CI fossa-check-notice job and commits it. Use when the user mentions FOSSA failure, NOTICE file update, fossa-check-notice job failure, or needs to fix a FOSSA pipeline error. Not for: license scanning setup, dependency vulnerability analysis (use maven scan), or general pipeline debugging (use glab).
Osdu QA
OSDU QA Testing - Environment management, API test execution, failure analysis, and report generation. Use when running OSDU API tests, analyzing failures, comparing environments, generating QA reports, or managing test environments. Not for: unit testing application code or build compilation (use build-runner instead).
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Build Runner skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: Apache-2.0. The author’s terms apply.