Skip to content
TrustedSkillsbeta
Back to all skills

Prowler Api

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

Provides API guidance and assistance for agent workflows.

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-api -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-api/SKILL.md
Scanned
7 files, 1,834 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

This skill provides guidance and assistance for developing Prowler API workflows, specifically addressing its unique architecture and security considerations. It focuses on patterns related to Row-Level Security (RLS), Role-Based Access Control (RBAC), provider lifecycle management, Celery tasks within a tenant context, and multi-database configurations. This is not a general coding assistant; it's tailored for Prowler API development.

When to use it

This skill is useful in the following scenarios:

  • Implementing Row-Level Security (RLS) or tenant isolation logic.
  • Managing RBAC permissions and verifying user roles within the application.
  • Validating provider lifecycle events and data integrity.
  • Developing Celery tasks that require explicit tenant context.
  • Working with Prowler's 4-database architecture, including understanding when to use each database (default, admin, replica, admin_replica).

Key capabilities

  • Provides guidance on using rls_transaction(tenant_id) for secure queries outside of ViewSet contexts.
  • Offers instructions on retrieving user roles with get_role().
  • Details the correct order of decorators: @set_tenant then @handle_provider_deletion.
  • Explains requirements for using explicit through models in M2M relationships to enforce RLS.
  • Outlines best practices for Celery task development within a tenant context.

Example prompts

  • "How do I ensure my query respects the current tenant's data?"
  • "What is the correct way to check user permissions in Prowler?"
  • "Explain how to use rls_transaction with a UUID."

Tips & gotchas

  • RLS Context: Always use rls_transaction(tenant_id) when querying data outside of a ViewSet context.
  • Database Selection: Be mindful of which database you're using (default, admin, replica, or admin_replica) and its implications for RLS enforcement. The 'admin' database bypasses RLS.
  • M2M Relationships: Explicit through models are required for M2M relationships to function correctly with Row-Level Security.