Skip to content
TrustedSkillsbeta
Back to all skills

Security Best Practices

Official
openai·vlatest·security

Official openai skill covering OpenAI, security, best practices for building AI and machine learning applications.

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 openai/skills --skill security-best-practices -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

openai

Matched to the vendor's own GitHub organisation.

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 openai/skills at 49f948faa9.

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

Commit
49f948faa9
Manifest
skills/.curated/security-best-practices/SKILL.md
Scanned
13 files, 9,053 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 a set of security best practices tailored for AI agents, ensuring safe and responsible deployment. It includes guidance on data privacy, secure API usage, access control, and threat mitigation specific to OpenAI's tools and frameworks.

When to use it

  • When deploying AI models in production environments that handle sensitive user data
  • When integrating third-party APIs with AI systems for enhanced functionality
  • When setting up multi-user or enterprise-level AI agent platforms requiring strict access controls
  • When auditing existing AI workflows for potential security vulnerabilities

Key capabilities

  • Data encryption and secure storage recommendations
  • Secure API key management and authentication protocols
  • Role-based access control (RBAC) implementation guidelines
  • Threat detection and response strategies for AI systems

Example prompts

  • "How can I securely store user data in my AI agent?"
  • "What are the best practices for managing API keys with OpenAI tools?"
  • "Can you outline steps to implement role-based access control for an AI platform?"

Tips & gotchas

  • Always ensure that sensitive information like API keys is never hardcoded or exposed in logs.
  • Regularly update and review security protocols as new threats emerge and technologies evolve.