Skip to content
TrustedSkillsbeta
Back to all skills

Security

Checked
alinaqi·vlatest·security·MIT

Identifies and mitigates potential cybersecurity threats using advanced threat intelligence and automated vulnerability scanning.

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 alinaqi/maggy --skill security -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

alinaqi

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 alinaqi/maggy at 72a456e6cc.

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

Commit
72a456e6cc
Manifest
skills/security/SKILL.md
Scanned
1 file, 542 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 enforces security best practices and automated security testing for projects, ensuring a baseline level of protection against common vulnerabilities. It emphasizes preventing sensitive information (like API keys and database credentials) from being committed to repositories and provides guidance on managing environment variables securely. The core principle is that all projects must pass security checks before merging changes.

When to use it

  • When setting up new development projects to ensure secure coding practices from the start.
  • During code reviews to identify potential security risks related to exposed secrets or improper configuration.
  • To standardize environment variable management across a team or organization.
  • Before committing code to repositories, ensuring sensitive data is excluded via .gitignore.
  • When migrating existing projects to improve their overall security posture.

Key capabilities

  • Gitignore Enforcement: Defines a mandatory .gitignore file to prevent the accidental commit of environment files, secrets, IDE settings, and build outputs.
  • Environment Variable Management: Provides guidelines for creating .env.example files with required variables (without values) and distinguishes between server-side only and client-exposed environment variables.
  • Secret Exposure Prevention: Highlights the dangers of exposing secrets in client-side code and provides examples of correct implementation.
  • Environment Validation: Includes example configuration for validating environment variables at startup using Zod (TypeScript) or Pydantic (Python).
  • Pre-Commit Security Checks: Suggests integrating a secret detection tool (Yelp/detect-secrets) into pre-commit hooks.

Example prompts

  • "Create a .gitignore file with the recommended security exclusions."
  • "Show me an example of how to securely store and access my Anthropic API key in a Next.js project."
  • "What environment variables are required for this project, and where should they be stored?"

Tips & gotchas

  • Mandatory Gitignore: The .gitignore file is non-negotiable; its contents must be adhered to strictly.
  • Client-Side Exposure: Be extremely careful about which environment variables are prefixed with VITE_ or NEXT_PUBLIC_, as these will be included in the client-side bundle and potentially exposed. Always verify this in browser devtools.
  • Server-Only Secrets: Secrets should always be accessed server-side, never directly from client-side code.