Skip to content
TrustedSkillsbeta
Back to all skills

Compliance Checker

Checked
curiouslearner·vlatest·security·MIT

The Compliance Checker verifies content against predefined rulesets, ensuring adherence and mitigating risks for enhanced security.

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 curiouslearner/devkit --skill compliance-checker -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

curiouslearner

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 curiouslearner/devkit at 3fa45b7ab3.

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

Commit
3fa45b7ab3
Manifest
skills/compliance-checker/SKILL.md
Scanned
1 file, 949 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

The curiouslearner-compliance-checker skill analyzes text to identify potential violations of specified compliance regulations. It can check documents, emails, or other textual data against a defined set of rules and highlight areas requiring further review. This helps automate the process of ensuring adherence to legal and industry standards.

When to use it

  • Contract Review: Quickly scan contracts for clauses that might violate company policy or relevant laws.
  • Email Compliance: Analyze internal or external emails for sensitive data exposure or inappropriate language.
  • Policy Adherence: Evaluate employee communications against established organizational policies.
  • Regulatory Checks: Verify documents comply with specific industry regulations (e.g., GDPR, HIPAA).

Key capabilities

  • Compliance rule checking
  • Text analysis
  • Highlighting potential violations

Example prompts

  • "Check this contract for any clauses that violate our data privacy policy."
  • "Analyze this email and flag anything that might be considered a conflict of interest."
  • “Review the following document against GDPR guidelines.”

Tips & gotchas

The effectiveness depends on having clearly defined compliance rules to provide as input. The skill highlights potential violations; human review is still required for final assessment.