Skip to content
TrustedSkillsbeta
Back to all skills

Prowler Ci

Checked
prowler-cloud·vlatest·devops·Apache-2.0

Prowler Ci automates security checks within your CI/CD pipelines, proactively identifying vulnerabilities and misconfigurations before deployment.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add prowler-cloud/prowler --skill prowler-ci -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

prowler-cloud

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned prowler-cloud/prowler at 03502c2426.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
03502c2426
Manifest
skills/prowler-ci/SKILL.md
Scanned
1 file, 76 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

Prowler Ci automates security checks within your CI/CD pipelines, specifically focusing on GitHub Actions workflows located under .github/workflows/. It helps diagnose why pull requests (PRs) fail checks related to title validation, changelog updates, conflict markers, and secret scanning. This skill allows agents to understand which workflows run for specific code changes and troubleshoot path-filtering behavior.

When to use it

  • When reading or modifying GitHub Actions workflows under .github/workflows/.
  • To explain why a pull request is failing checks (e.g., title, changelog, conflict markers, secret scanning).
  • To determine which workflows are triggered by UI, API, or SDK changes and understand the reasons behind them.
  • When diagnosing issues with path-filtering behavior in GitHub Actions workflows.

Key capabilities

  • PR Title Validation: Checks if pull request titles adhere to Conventional Commits standards.
  • Changelog Gate: Verifies that a changelog is updated or the no-changelog label is applied.
  • Conflict Marker Check: Identifies and flags conflict markers (<<<<<<<, =======, >>>>>>>) in pull requests.
  • Secret Scanning (TruffleHog): Scans for leaked secrets, including patterns like OpenAI API keys, AWS Access Keys, GitHub tokens, and Base64-encoded credentials.
  • Workflow Path Filtering: Helps understand why a workflow did or didn't run based on file changes.

Example prompts

  • "Explain why this pull request failed its checks."
  • "What workflows are triggered by changes to the UI code?"
  • "Why isn’t this workflow running for these changed files?"
  • "Analyze this TruffleHog report and identify potential false positives in test files."

Tips & gotchas

  • This skill focuses specifically on GitHub Actions workflows.
  • Be aware of common TruffleHog false positives, particularly within test files. Use obviously fake credentials (e.g., api_key = "sk-fake-test-key-for-unit-testing-only") to avoid triggering the scanner in those cases.
  • If a real secret is flagged by TruffleHog, immediately remove it from the code and rotate the credential.