endorlabs
- 88 skills
- 0 followers
- 4 hours ago last updated
- ▌ Endor Agent Kit Setup 2 · endorlabsUse when setting up Endor Labs Agent Kit for Claude Code, checking readiness, verifying Endor auth, choosing namespaces, or diagnosing missing endorctl, gh, Endor MCP, or workflow prerequisites.
- ▌ Cicd Posture 2 · endorlabsAssesses CI/CD and software supply-chain security across an Endor namespace, GitHub organization, selected repositories, or the current repository. It combines existing Endor SCPM, CI/CD, GitHub Actions, and supply-chain findings with read-only repository configuration evidence and optional local CI inspection to produce deterministic scores, critical overrides, prioritized improvements, and explicit data gaps. It does not modify Endor, GitHub, or repository state.
- ▌ Sca Remediation 2 · endorlabsPlans and applies dependency-vulnerability fixes using Endor SCA findings, VersionUpgrade and Upgrade Impact Analysis evidence, deterministic risk decisions, and local validation. It separates low-risk changes from upgrades requiring deeper compatibility review and requires explicit approval before editing files, pushing branches, opening change requests, or creating tickets.
- ▌ Troubleshooting 2 · endorlabsDiagnoses Endor setup, authentication, integration, scanning, dependency-resolution, container, reachability, policy, and workflow problems. It gathers the smallest useful set of read-only evidence needed to identify the likely root cause and recommend the lowest-friction repair without modifying Endor, source-provider, or repository state.
- ▌ Findings Browser 2 · endorlabsBrowses, filters, and summarizes existing Endor findings without starting new scans or performing remediation. It shows the applied scope and filters, relevant severity and reachability context, pagination or truncation limits, and any evidence gaps affecting the results.
- ▌ Cicd Posture 3 · endorlabsAssesses CI/CD and software supply-chain security across an Endor namespace, GitHub organization, selected repositories, or the current repository. It combines existing Endor SCPM, CI/CD, GitHub Actions, and supply-chain findings with read-only repository configuration evidence and optional local CI inspection to produce deterministic scores, critical overrides, prioritized improvements, and explicit data gaps. It does not modify Endor, GitHub, or repository state.
- ▌ Malware Responder 2 · endorlabsCorrelates current software supply-chain malware intelligence for affected packages and versions with Endor inventory across a namespace and its child namespaces. It distinguishes confirmed exposure, possible exposure, not-observed exposure, and insufficient data using exact package, version, and inventory evidence. It reports affected projects, indicators of compromise, containment guidance, and recommended follow-up actions without modifying Endor or source systems.
- ▌ Cicd Posture 4 · endorlabsAssesses CI/CD and software supply-chain security across an Endor namespace, GitHub organization, selected repositories, or the current repository. It combines existing Endor SCPM, CI/CD, GitHub Actions, and supply-chain findings with read-only repository configuration evidence and optional local CI inspection to produce deterministic scores, critical overrides, prioritized improvements, and explicit data gaps. It does not modify Endor, GitHub, or repository state.
- ▌ AI Sast Remediation 2 · endorlabsTriages Endor AI SAST findings using exploit-reproduction evidence, data-flow context, and remediation guidance to distinguish actionable vulnerabilities from noise. It can prepare targeted code fixes and, after explicit approval, edit files and open change requests. For exception workflows, it can create or update scoped Endor exception policies only after verified AppSec approval and explicit user confirmation.
- ▌ Dependency Reviewer 2 · endorlabsEvaluates an exact package version, summarizes package risk, or reviews dependencies declared by a repository through one focused workflow. It uses available vulnerability, malware, package-health, license, policy, and Endor evidence to provide a read-only recommendation and clearly identify missing information.
- ▌ Sca Remediation 3 · endorlabsPlans and applies dependency-vulnerability fixes using Endor SCA findings, VersionUpgrade and Upgrade Impact Analysis evidence, deterministic risk decisions, and local validation. It separates low-risk changes from upgrades requiring deeper compatibility review and requires explicit approval before editing files, pushing branches, opening change requests, or creating tickets.
- ▌ Troubleshooting 3 · endorlabsDiagnoses Endor setup, authentication, integration, scanning, dependency-resolution, container, reachability, policy, and workflow problems. It gathers the smallest useful set of read-only evidence needed to identify the likely root cause and recommend the lowest-friction repair without modifying Endor, source-provider, or repository state.
- ▌ Endor Agent Kit Setup 3 · endorlabsUse when setting up Endor Labs Agent Kit for Codex, checking readiness, installing or updating bundled Codex custom agents, verifying Endor auth, or diagnosing missing endorctl, gh, namespace, or toolchain prerequisites.
- ▌ Remediation Planning 2 · endorlabsPreviews safe remediation options for existing Endor findings without changing code or opening a pull request. It compares VersionUpgrade and Upgrade Impact Analysis candidates using findings fixed, upgrade risk, compatibility evidence, and available data, then recommends the safest evidence-backed next step.
- ▌ Findings Browser 3 · endorlabsBrowses, filters, and summarizes existing Endor findings without starting new scans or performing remediation. It shows the applied scope and filters, relevant severity and reachability context, pagination or truncation limits, and any evidence gaps affecting the results.
- ▌ Cicd Posture 5 · endorlabs bundleAssesses CI/CD and software supply-chain security across an Endor namespace, GitHub organization, selected repositories, or the current repository. It combines existing Endor SCPM, CI/CD, GitHub Actions, and supply-chain findings with read-only repository configuration evidence and optional local CI inspection to produce deterministic scores, critical overrides, prioritized improvements, and explicit data gaps. It does not modify Endor, GitHub, or repository state.
- ▌ Endor Agent Kit Setup 4 · endorlabsUse when setting up Endor Labs Agent Kit for Cursor, checking readiness, verifying Endor auth, choosing namespaces, or diagnosing missing endorctl, gh, Endor MCP, or workflow prerequisites.
- ▌ Endor Agent Kit Setup 5 · endorlabsUse when setting up Endor Labs Agent Kit for Gemini CLI, checking readiness, verifying Endor auth, choosing namespaces, or diagnosing missing endorctl, gh, Gemini CLI, Endor MCP, or workflow prerequisites.
- ▌ Malware Responder 3 · endorlabsCorrelates current software supply-chain malware intelligence for affected packages and versions with Endor inventory across a namespace and its child namespaces. It distinguishes confirmed exposure, possible exposure, not-observed exposure, and insufficient data using exact package, version, and inventory evidence. It reports affected projects, indicators of compromise, containment guidance, and recommended follow-up actions without modifying Endor or source systems.
- ▌ Sca Remediation 4 · endorlabsPlans and applies dependency-vulnerability fixes using Endor SCA findings, VersionUpgrade and Upgrade Impact Analysis evidence, deterministic risk decisions, and local validation. It separates low-risk changes from upgrades requiring deeper compatibility review and requires explicit approval before editing files, pushing branches, opening change requests, or creating tickets.
- ▌ Troubleshooting 4 · endorlabsDiagnoses Endor setup, authentication, integration, scanning, dependency-resolution, container, reachability, policy, and workflow problems. It gathers the smallest useful set of read-only evidence needed to identify the likely root cause and recommend the lowest-friction repair without modifying Endor, source-provider, or repository state.
- ▌ Findings Browser 4 · endorlabsBrowses, filters, and summarizes existing Endor findings without starting new scans or performing remediation. It shows the applied scope and filters, relevant severity and reachability context, pagination or truncation limits, and any evidence gaps affecting the results.
- ▌ Vulnerability Explainer 2 · endorlabsExplains a CVE, GHSA, or Endor vulnerability, optionally in the context of a supplied package and version. It summarizes severity, exploitability signals, affected and fixed versions, recommended remediation, and relevant reachability or repository context when supported by exact Endor evidence. It clearly identifies missing information rather than inferring package or project applicability.
- ▌ AI Sast Remediation 3 · endorlabsTriages Endor AI SAST findings using exploit-reproduction evidence, data-flow context, and remediation guidance to distinguish actionable vulnerabilities from noise. It can prepare targeted code fixes and, after explicit approval, edit files and open change requests. For exception workflows, it can create or update scoped Endor exception policies only after verified AppSec approval and explicit user confirmation.
- ▌ Dependency Reviewer 3 · endorlabsEvaluates an exact package version, summarizes package risk, or reviews dependencies declared by a repository through one focused workflow. It uses available vulnerability, malware, package-health, license, policy, and Endor evidence to provide a read-only recommendation and clearly identify missing information.
- ▌ Sca Remediation 5 · endorlabs bundlePlans and applies dependency-vulnerability fixes using Endor SCA findings, VersionUpgrade and Upgrade Impact Analysis evidence, deterministic risk decisions, and local validation. It separates low-risk changes from upgrades requiring deeper compatibility review and requires explicit approval before editing files, pushing branches, opening change requests, or creating tickets.
- ▌ Troubleshooting 5 · endorlabs bundleDiagnoses Endor setup, authentication, integration, scanning, dependency-resolution, container, reachability, policy, and workflow problems. It gathers the smallest useful set of read-only evidence needed to identify the likely root cause and recommend the lowest-friction repair without modifying Endor, source-provider, or repository state.
- ▌ Malware Responder 4 · endorlabsCorrelates current software supply-chain malware intelligence for affected packages and versions with Endor inventory across a namespace and its child namespaces. It distinguishes confirmed exposure, possible exposure, not-observed exposure, and insufficient data using exact package, version, and inventory evidence. It reports affected projects, indicators of compromise, containment guidance, and recommended follow-up actions without modifying Endor or source systems.
- ▌ Configuration Automation 2 · endorlabsCompares GitHub repository inventory with Endor projects, GitHub App coverage, monitored branches, scan profiles, package-manager integrations, dependency resolution, and reachability evidence. It identifies onboarding and configuration gaps and provides targeted setup instructions without changing GitHub, Endor, or source repositories.
- ▌ Oss Upgrade Investigator 2 · endorlabsEvaluates candidate dependency upgrades using Endor VersionUpgrade data, Code Impact Analysis, findings, breaking-change information, and Endor-provided manifest targets. It compares findings fixed or introduced and explains the safest available upgrade path, including whether to upgrade now, proceed cautiously, defer, or gather more evidence.
- ▌ Remediation Planning 3 · endorlabsPreviews safe remediation options for existing Endor findings without changing code or opening a pull request. It compares VersionUpgrade and Upgrade Impact Analysis candidates using findings fixed, upgrade risk, compatibility evidence, and available data, then recommends the safest evidence-backed next step.
- ▌ Findings Browser 5 · endorlabs bundleBrowses, filters, and summarizes existing Endor findings without starting new scans or performing remediation. It shows the applied scope and filters, relevant severity and reachability context, pagination or truncation limits, and any evidence gaps affecting the results.
- ▌ Endor Agent Kit Setup 6 · endorlabsUse when setting up Endor Labs Agent Kit for Antigravity CLI, checking readiness, verifying Endor auth, choosing namespaces, or diagnosing missing endorctl, gh, Antigravity CLI, Endor MCP, or workflow prerequisites.
- ▌ Malware Responder 5 · endorlabs bundleCorrelates current software supply-chain malware intelligence for affected packages and versions with Endor inventory across a namespace and its child namespaces. It distinguishes confirmed exposure, possible exposure, not-observed exposure, and insufficient data using exact package, version, and inventory evidence. It reports affected projects, indicators of compromise, containment guidance, and recommended follow-up actions without modifying Endor or source systems.
- ▌ AI Sast Remediation 4 · endorlabsTriages Endor AI SAST findings using exploit-reproduction evidence, data-flow context, and remediation guidance to distinguish actionable vulnerabilities from noise. It can prepare targeted code fixes and, after explicit approval, edit files and open change requests. For exception workflows, it can create or update scoped Endor exception policies only after verified AppSec approval and explicit user confirmation.
- ▌ Dependency Reviewer 4 · endorlabsEvaluates an exact package version, summarizes package risk, or reviews dependencies declared by a repository through one focused workflow. It uses available vulnerability, malware, package-health, license, policy, and Endor evidence to provide a read-only recommendation and clearly identify missing information.
- ▌ Remediation Planning 4 · endorlabsPreviews safe remediation options for existing Endor findings without changing code or opening a pull request. It compares VersionUpgrade and Upgrade Impact Analysis candidates using findings fixed, upgrade risk, compatibility evidence, and available data, then recommends the safest evidence-backed next step.
- ▌ Vulnerability Explainer 3 · endorlabsExplains a CVE, GHSA, or Endor vulnerability, optionally in the context of a supplied package and version. It summarizes severity, exploitability signals, affected and fixed versions, recommended remediation, and relevant reachability or repository context when supported by exact Endor evidence. It clearly identifies missing information rather than inferring package or project applicability.
- ▌ AI Sast Remediation 5 · endorlabs bundleTriages Endor AI SAST findings using exploit-reproduction evidence, data-flow context, and remediation guidance to distinguish actionable vulnerabilities from noise. It can prepare targeted code fixes and, after explicit approval, edit files and open change requests. For exception workflows, it can create or update scoped Endor exception policies only after verified AppSec approval and explicit user confirmation.
- ▌ Dependency Reviewer 5 · endorlabs bundleEvaluates an exact package version, summarizes package risk, or reviews dependencies declared by a repository through one focused workflow. It uses available vulnerability, malware, package-health, license, policy, and Endor evidence to provide a read-only recommendation and clearly identify missing information.
- ▌ Configuration Automation 3 · endorlabsCompares GitHub repository inventory with Endor projects, GitHub App coverage, monitored branches, scan profiles, package-manager integrations, dependency resolution, and reachability evidence. It identifies onboarding and configuration gaps and provides targeted setup instructions without changing GitHub, Endor, or source repositories.
- ▌ Oss Upgrade Investigator 3 · endorlabsEvaluates candidate dependency upgrades using Endor VersionUpgrade data, Code Impact Analysis, findings, breaking-change information, and Endor-provided manifest targets. It compares findings fixed or introduced and explains the safest available upgrade path, including whether to upgrade now, proceed cautiously, defer, or gather more evidence.
- ▌ Remediation Planning 5 · endorlabs bundlePreviews safe remediation options for existing Endor findings without changing code or opening a pull request. It compares VersionUpgrade and Upgrade Impact Analysis candidates using findings fixed, upgrade risk, compatibility evidence, and available data, then recommends the safest evidence-backed next step.
- ▌ Endor Agent Kit Setup 7 · endorlabs bundleUse when checking Endor Agent Kit readiness in Codex, verifying the local Endor CLI, authentication, namespace, GitHub, or toolchain prerequisites.
- ▌ Vulnerability Explainer 4 · endorlabsExplains a CVE, GHSA, or Endor vulnerability, optionally in the context of a supplied package and version. It summarizes severity, exploitability signals, affected and fixed versions, recommended remediation, and relevant reachability or repository context when supported by exact Endor evidence. It clearly identifies missing information rather than inferring package or project applicability.
- ▌ Configuration Automation 4 · endorlabsCompares GitHub repository inventory with Endor projects, GitHub App coverage, monitored branches, scan profiles, package-manager integrations, dependency resolution, and reachability evidence. It identifies onboarding and configuration gaps and provides targeted setup instructions without changing GitHub, Endor, or source repositories.
- ▌ Oss Upgrade Investigator 4 · endorlabsEvaluates candidate dependency upgrades using Endor VersionUpgrade data, Code Impact Analysis, findings, breaking-change information, and Endor-provided manifest targets. It compares findings fixed or introduced and explains the safest available upgrade path, including whether to upgrade now, proceed cautiously, defer, or gather more evidence.
- ▌ Vulnerability Explainer 5 · endorlabs bundleExplains a CVE, GHSA, or Endor vulnerability, optionally in the context of a supplied package and version. It summarizes severity, exploitability signals, affected and fixed versions, recommended remediation, and relevant reachability or repository context when supported by exact Endor evidence. It clearly identifies missing information rather than inferring package or project applicability.
- ▌ Configuration Automation 5 · endorlabs bundleCompares GitHub repository inventory with Endor projects, GitHub App coverage, monitored branches, scan profiles, package-manager integrations, dependency resolution, and reachability evidence. It identifies onboarding and configuration gaps and provides targeted setup instructions without changing GitHub, Endor, or source repositories.
- ▌ Oss Upgrade Investigator 5 · endorlabs bundleEvaluates candidate dependency upgrades using Endor VersionUpgrade data, Code Impact Analysis, findings, breaking-change information, and Endor-provided manifest targets. It compares findings fixed or introduced and explains the safest available upgrade path, including whether to upgrade now, proceed cautiously, defer, or gather more evidence.
- ▌ Endor Agent Kit Setup · endorlabsUse when setting up Endor Labs Agent Kit for Claude Code, checking readiness, verifying Endor auth, choosing namespaces, or diagnosing missing endorctl, gh, Endor MCP, or workflow prerequisites.
- ▌ Cicd Posture · endorlabs bundleAssesses CI/CD and software supply-chain security across an Endor namespace, GitHub organization, selected repositories, or the current repository. It combines existing Endor SCPM, CI/CD, GitHub Actions, and supply-chain findings with read-only repository configuration evidence and optional local CI inspection to produce deterministic scores, critical overrides, prioritized improvements, and explicit data gaps. It does not modify Endor, GitHub, or repository state.
- ▌ Sca Remediation · endorlabs bundlePlans and applies dependency-vulnerability fixes using Endor SCA findings, VersionUpgrade and Upgrade Impact Analysis evidence, deterministic risk decisions, and local validation. It separates low-risk changes from upgrades requiring deeper compatibility review and requires explicit approval before editing files, pushing branches, opening change requests, or creating tickets.
- ▌ Troubleshooting · endorlabs bundleDiagnoses Endor setup, authentication, integration, scanning, dependency-resolution, container, reachability, policy, and workflow problems. It gathers the smallest useful set of read-only evidence needed to identify the likely root cause and recommend the lowest-friction repair without modifying Endor, source-provider, or repository state.
- ▌ Findings Browser · endorlabs bundleBrowses, filters, and summarizes existing Endor findings without starting new scans or performing remediation. It shows the applied scope and filters, relevant severity and reachability context, pagination or truncation limits, and any evidence gaps affecting the results.
- ▌ Malware Responder · endorlabs bundleCorrelates current software supply-chain malware intelligence for affected packages and versions with Endor inventory across a namespace and its child namespaces. It distinguishes confirmed exposure, possible exposure, not-observed exposure, and insufficient data using exact package, version, and inventory evidence. It reports affected projects, indicators of compromise, containment guidance, and recommended follow-up actions without modifying Endor or source systems.
- ▌ AI Sast Remediation · endorlabs bundleTriages Endor AI SAST findings using exploit-reproduction evidence, data-flow context, and remediation guidance to distinguish actionable vulnerabilities from noise. It can prepare targeted code fixes and, after explicit approval, edit files and open change requests. For exception workflows, it can create or update scoped Endor exception policies only after verified AppSec approval and explicit user confirmation.
- ▌ Dependency Reviewer · endorlabs bundleEvaluates an exact package version, summarizes package risk, or reviews dependencies declared by a repository through one focused workflow. It uses available vulnerability, malware, package-health, license, policy, and Endor evidence to provide a read-only recommendation and clearly identify missing information.
- ▌ Remediation Planning · endorlabs bundlePreviews safe remediation options for existing Endor findings without changing code or opening a pull request. It compares VersionUpgrade and Upgrade Impact Analysis candidates using findings fixed, upgrade risk, compatibility evidence, and available data, then recommends the safest evidence-backed next step.
- ▌ Vulnerability Explainer · endorlabsExplains a CVE, GHSA, or Endor vulnerability, optionally in the context of a supplied package and version. It summarizes severity, exploitability signals, affected and fixed versions, recommended remediation, and relevant reachability or repository context when supported by exact Endor evidence. It clearly identifies missing information rather than inferring package or project applicability.
- ▌ Configuration Automation · endorlabs bundleCompares GitHub repository inventory with Endor projects, GitHub App coverage, monitored branches, scan profiles, package-manager integrations, dependency resolution, and reachability evidence. It identifies onboarding and configuration gaps and provides targeted setup instructions without changing GitHub, Endor, or source repositories.
- ▌ Oss Upgrade Investigator · endorlabs bundleEvaluates candidate dependency upgrades using Endor VersionUpgrade data, Code Impact Analysis, findings, breaking-change information, and Endor-provided manifest targets. It compares findings fixed or introduced and explains the safest available upgrade path, including whether to upgrade now, proceed cautiously, defer, or gather more evidence.
- ▌ Endor Oss Request · endorlabsTrigger ingestion and analysis of a specific open source package version via an Endor Labs OSS dependency request. Use when the user says "trigger OSS dependency request", "request ingestion of <pkg>", "ingest this package", "add this OSS version to Endor", or wants Endor Labs to analyze a package version that isn't yet in the platform. Do NOT use for scanning local code (/endor-scan) or checking an already-ingested package (/endor-check).
- ▌ Endor Supply Chain · endorlabsAssess supply chain risk for your repository by scanning dependencies, secrets, and GitHub Actions workflows using Endor Labs. Use when the user says "supply chain risk", "supply chain assessment", "assess my supply chain", "endor supply chain", "third-party risk", "software supply chain", or wants a combined view of dependency vulnerabilities, leaked secrets, and CI/CD pipeline risks. Do NOT use for GitHub Actions workflows only (/endor-ghactions), code-level SAST scanning (/endor-sast), single package checks (/endor-check), or full reachability analysis (/endor-scan-full).
- ▌ Endor Troubleshoot · endorlabsTroubleshoot Endor Labs scan errors and failures. Use when the user says "scan failed", "why did the scan fail", "endor troubleshoot", "fix scan error", "diagnose error", or pastes an error message from a failed scan. Matches errors against known patterns across NPM, Maven, PyPI, Go, Cargo, NuGet, RubyGems, and Packagist. Do NOT use for setup issues (/endor-setup) or general scanning (/endor-scan).
- ▌ Endor Upgrade Impact · endorlabsAnalyze the impact of upgrading a dependency before you do it. Use when the user says "should I upgrade lodash", "what breaks if I update express", "upgrade impact", "endor upgrade", "breaking changes from upgrading", or wants to find the safest version that fixes vulnerabilities. Uses pre-computed Endor Labs data — no scanning required. Do NOT use for just checking vulnerabilities (/endor-check) or applying a fix (/endor-fix).
- ▌ Endor Validate Policy · endorlabsValidate an Endor Labs policy against a project to test if it matches any findings. Use when the user says "validate policy", "test policy", "does this policy match", "endor validate", "check policy against project", or wants to verify that a policy (finding or exception) correctly targets findings in a specific project before enforcing it. Do NOT use for creating policies (/endor-policy) or viewing findings (/endor-findings).
- ▌ Endor · endorlabsMain Endor Labs security router. Use when the user says "endor", "endor labs", or asks a general security question without specifying a particular endor command. Routes ambiguous requests like "check my security", "help with this dependency", or "what security tools are available" to the right specialized skill. Do NOT use when the user names a specific command like /endor-scan, /endor-check, /endor-fix, etc. — those skills handle themselves directly.
- ▌ Endor API · endorlabsExecute custom queries against the Endor Labs API for advanced use cases. Use when the user asks to query findings, projects, packages, or metrics directly, says "endor api", "raw api query", "custom query", "list resources", or needs to run API filters not covered by other endor skills. Do NOT use for standard scanning (/endor-scan), dependency checks (/endor-check), or finding display (/endor-findings).
- ▌ Endor Fix · endorlabsRemediate security vulnerabilities by finding safe upgrade paths. Use when the user says "fix this vulnerability", "how do I fix CVE-XXXX", "remediate this finding", "patch this vuln", "endor fix", or wants step-by-step fix instructions for a specific CVE, finding, or vulnerable package. Can apply fixes automatically. Do NOT use for general scanning (/endor-scan) or just viewing vulnerability info (/endor-explain).
- ▌ Endor Sca · endorlabsScan all project dependencies for known vulnerabilities using Software Composition Analysis. Use when the user says "scan my dependencies", "SCA scan", "vulnerable dependencies", "endor sca", "what's wrong with my deps", or wants a focused dependency vulnerability report with direct vs transitive breakdown. Do NOT use for checking a single package (/endor-check), SAST code scanning (/endor-sast), or quick full scan (/endor-scan).
- ▌ Endor Cicd · endorlabs bundleGenerate 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 Demo · endorlabsDemo Endor Labs capabilities using simulated data, no account required. Use when the user says "try endor", "demo", "endor without account", "show me what endor can do", or when MCP auth fails and user wants to see capabilities before signing up. Do NOT use when the user has a working Endor Labs account — use real scans instead.
- ▌ Endor Help · endorlabsQuick reference for all available Endor Labs commands. Use when the user says "endor help", "what commands are available", "endor usage", "what can endor do", or wants to discover available security scanning capabilities. Do NOT use when the user already knows which specific command they want — route to that skill directly.
- ▌ Endor Sbom · endorlabsManage Software Bill of Materials — export, import, analyze, and compare SBOMs in CycloneDX and SPDX formats. Use when the user says "generate SBOM", "export SBOM", "software bill of materials", "endor sbom", "compare SBOMs", "NTIA compliance", or needs component inventory for compliance. Do NOT use for vulnerability scanning (/endor-scan) or license analysis (/endor-license).
- ▌ Endor Scan · endorlabsFast security scan of the current repository using Endor Labs. Use when the user says "scan my code", "quick scan", "endor scan", "scan this repo", "run a security scan", or wants a rapid overview of vulnerabilities, secrets, and SAST issues. Also handles incremental PR scans when user mentions "just my changes" or "PR scan". Do NOT use for deep reachability analysis (/endor-scan-full) or checking a single package (/endor-check).
- ▌ Endor Check · endorlabsCheck if a specific dependency has known vulnerabilities or malware using Endor Labs. Use when the user names a package and wants to know if it's safe, says "check lodash", "is express vulnerable", "any CVEs in django", "endor check", "is this package safe", or provides a package name after installing a dependency. Do NOT use for scanning an entire repo (/endor-scan) or viewing existing findings (/endor-findings).
- ▌ Endor Score · endorlabsEvaluate open source package health before adoption. Use when the user says "should I use this package", "is lodash well-maintained", "endor score express", "package health", "compare lodash vs underscore", "evaluate this dependency", or wants activity, popularity, security, and quality scores. Do NOT use for checking known CVEs in a package (/endor-check) or scanning the whole repo (/endor-scan).
- ▌ Endor Setup · endorlabsOnboarding wizard for Endor Labs. Guides users through prerequisites, MCP server configuration, authentication, namespace setup, and running their first scan. Use when the user says "endor setup", "configure endor", "endor auth", "set up endor", "install endor", "endor onboarding", or when any MCP tool fails with an auth or namespace error. Do NOT use when the user already has a working setup — route to specific skills instead.
- ▌ Endor Policy · endorlabsCreate and manage Endor Labs security policies for automated enforcement. Use when the user says "create a policy", "block critical vulns", "endor policy", "security gate", "enforcement rules", "exception policy", or wants to define rules for blocking PRs, requiring reviews, or enforcing security standards. Do NOT use for one-time PR review (/endor-review) or viewing findings (/endor-findings).
- ▌ Endor Review · endorlabsPre-PR security review of your current branch or git diff. Use when the user says "review my changes", "ready to merge", "pre-PR check", "security review before PR", "endor review", or is about to create a pull request. Runs dependency checks, SAST, secrets detection, and license compliance as a security gate. Do NOT use for scanning repos outside the current branch (/endor-scan) or checking individual packages (/endor-check).
- ▌ Endor Explain · endorlabsGet detailed information about a specific CVE or security finding. Use when the user says "what is CVE-2024-XXXXX", "explain this vulnerability", "tell me about GHSA-...", "endor explain", "finding details", or wants to understand severity, impact, attack vectors, and affected versions for a specific issue. Do NOT use for fixing a vuln (/endor-fix) or listing all findings (/endor-findings).
- ▌ Endor License · endorlabsAnalyze dependency license compliance and identify license risks. Use when the user says "check licenses", "license compliance", "any GPL dependencies", "copyleft risk", "endor license", or wants to know if dependencies are compatible with their project license. Flags copyleft (GPL, AGPL), unknown, and no-license packages. Do NOT use for vulnerability scanning (/endor-sca) or policy enforcement (/endor-policy).
- ▌ Endor Secrets · endorlabsScan for exposed secrets, credentials, API keys, and sensitive data in your codebase. Use when the user says "find secrets", "scan for API keys", "exposed credentials", "endor secrets", "check for hardcoded passwords", pre-commit / staged-only secret checks, or suspects leaked tokens in code. Detects AWS keys, GitHub tokens, Stripe keys, private keys, and more. Do NOT use for code vulnerability scanning (/endor-sast) or dependency checks (/endor-sca).
- ▌ Endor Findings · endorlabsDisplay and filter security findings from Endor Labs. Use when the user says "show findings", "list vulnerabilities", "what did the scan find", "endor findings", "show me critical reachable vulns", or wants to browse/filter results after a scan. Supports filtering by severity, reachability, category (vuln/sast/secrets/license). Do NOT use for running a new scan (/endor-scan) or explaining a specific CVE (/endor-explain).
- ▌ Endor Container · endorlabsScan container images and analyze Dockerfiles for security issues. Use when the user says "scan my Docker image", "Dockerfile security", "container scan", "endor container", "docker compose security", or is creating/modifying Dockerfiles and docker-compose files. Checks for root user, latest tags, exposed ports, secrets in build args, and missing health checks. Do NOT use for application code scanning (/endor-sast).
- ▌ Endor Ghactions · endorlabsScan a repository's GitHub Actions workflows for insecure patterns and vulnerable third-party action versions using Endor Labs. Use when the user says "scan GitHub Actions", "workflow security", "endor ghactions", "insecure CI workflow", "vulnerable action version", "harden my GHA workflows", or focuses on `.github/workflows` without asking for a full dependency or secrets scan. Do NOT use for combined supply chain reports (/endor-supply-chain), generic quick scans (/endor-scan), adding Endor to pipelines (/endor-cicd), or dependency-only checks (/endor-check).
- ▌ Endor Scan Full · endorlabsComprehensive security scan with full reachability analysis. Builds call graphs to determine which vulnerabilities are actually exploitable in your code. Use when the user says "full scan", "deep scan", "reachability scan", "which vulns are actually reachable", "endor scan full", or before a release. Takes 2-5 minutes. Do NOT use for quick daily scans (/endor-scan) or checking individual packages (/endor-check).