Generate CI/CD pipeline configurations for Endor Labs security scanning. Supports GitHub Actions, GitLab CI, Jenkins, Azure DevOps, Bitbucket Pipelines, and CircleCI. Use when the user says "add security to my pipeline", "endor CI/CD", "GitHub Actions endor", "set up CI scanning", or wants automated security checks in their build pipeline. Do NOT use for running scans locally (/endor-scan) or managing policies (/endor-policy).
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Generate CI/CD security scanning configurations for your preferred platform.
| Platform | Config File |
|---|---|
| GitHub Actions | .github/workflows/endor-security.yml |
| GitLab CI | .gitlab-ci.yml (append stage) |
| Jenkins | Jenkinsfile (append stage) |
| Azure DevOps | azure-pipelines.yml (append stage) |
| Bitbucket Pipelines | bitbucket-pipelines.yml (append step) |
| CircleCI | .circleci/config.yml (append job) |
Check for existing CI/CD config files. If multiple detected or none found, ask the user.
Read references/cicd-templates.md for the template matching the detected platform. Customize the template with project-specific settings (languages, build commands, namespace).
After generating, provide:
| Secret | Description |
|---|---|
ENDOR_NAMESPACE | Organization identifier |
ENDOR_API_CREDENTIALS_KEY | API key for auth |
ENDOR_API_CREDENTIALS_SECRET | API secret for auth |
Never hardcode these in config files.
/endor-policy to add policy gates blocking PRs with critical issuesFor data source policy, read references/data-sources.md.
| Error | Action |
|---|---|
| No CI/CD detected | Ask which platform to use |
| Existing config | Append security stage alongside existing config, do not overwrite |
344e7ff
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.