How do I install the Endor Cicd skill?

Run npx skillmds@latest add endorlabs/endor-cicd in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Endor Cicd safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Endor Cicd?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Endor Cicd free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Endor Cicd?

endorlabs (@endorlabs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Endor Cicd by endorlabs — Agent Skill

Name: Endor Cicd
Rating: 4.666666666666667 (3 reviews)
Author: endorlabs

Endor Cicd

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).

endorlabs 0ae4568 2 files · 5.7 KB Updated Sep 10, 2026

File contents

Endor Labs CI/CD Pipeline Generator

Generate CI/CD security scanning configurations for your preferred platform.

Supported Platforms

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)

Workflow

Step 1: Detect Platform

Check for existing CI/CD config files. If multiple detected or none found, ask the user.

Step 2: Detect Project Settings

Languages (from manifest files)
Build commands (from existing CI config or package.json scripts)
ENDOR_NAMESPACE (from environment or ask user)

Step 3: Generate Configuration

Read references/cicd-templates.md for the template matching the detected platform. Customize the template with project-specific settings (languages, build commands, namespace).

Step 4: Setup Instructions

After generating, provide:

Required Secrets

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.

Next Steps

Add secrets to CI/CD platform
Commit configuration file
Push test commit or open PR to verify
/endor-policy to add policy gates blocking PRs with critical issues

For data source policy, read references/data-sources.md.

Error Handling

Error	Action
No CI/CD detected	Ask which platform to use
Existing config	Append security stage alongside existing config, do not overwrite

---name: endor-cicddescription: 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).---# Endor Labs CI/CD Pipeline GeneratorGenerate CI/CD security scanning configurations for your preferred platform.## Supported Platforms| 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) |## Workflow### Step 1: Detect PlatformCheck for existing CI/CD config files. If multiple detected or none found, ask the user.### Step 2: Detect Project Settings- Languages (from manifest files)- Build commands (from existing CI config or package.json scripts)- ENDOR_NAMESPACE (from environment or ask user)### Step 3: Generate ConfigurationRead `references/cicd-templates.md` for the template matching the detected platform. Customize the template with project-specific settings (languages, build commands, namespace).### Step 4: Setup InstructionsAfter generating, provide:#### Required Secrets| 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.#### Next Steps1. Add secrets to CI/CD platform2. Commit configuration file3. Push test commit or open PR to verify4. `/endor-policy` to add policy gates blocking PRs with critical issuesFor data source policy, read references/data-sources.md.## Error Handling| Error | Action ||-------|--------|| No CI/CD detected | Ask which platform to use || Existing config | Append security stage alongside existing config, do not overwrite |

Frequently asked questions