Skip to content
TrustedSkillsbeta
Back to all skills

Regulatory Review Checklist

Checked
gtmagents·vlatest·productivity·Apache-2.0

Automates regulatory compliance reviews using customizable checklists, ensuring adherence to industry standards and minimizing risk.

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 gtmagents/gtm-agents --skill regulatory-review-checklist -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

gtmagents

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 gtmagents/gtm-agents at 78e0419f44.

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

Scanned
1 file, 32 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 generates a regulatory review checklist based on provided information about a product or service. It helps ensure compliance with relevant regulations, identifying potential gaps and areas for improvement. The checklists are tailored to the specifics of the input and can be used as a starting point for more detailed reviews.

When to use it

  • Before launching a new product in a regulated industry (e.g., finance, healthcare).
  • When adapting an existing product or service to operate in a new geographic region with different regulations.
  • To prepare for regulatory audits and ensure ongoing compliance.
  • For internal reviews of current processes to identify potential risks.

Key capabilities

  • Generates checklists based on provided product/service descriptions.
  • Tailors checklist items to specific inputs.
  • Identifies potential areas of non-compliance.

Example prompts

  • "Create a regulatory review checklist for a mobile banking app targeting users in the UK."
  • "Generate a checklist for a new AI-powered medical diagnostic tool, considering HIPAA and FDA regulations."
  • “I’m launching an online educational platform. What should I check to ensure compliance?”

Tips & gotchas

The quality of the generated checklist depends heavily on the detail provided in the input description. Be as specific as possible about the product or service being reviewed for best results.