Skip to content
TrustedSkillsbeta
Back to all skills

security-ownership-map

Official
openai·v1.0.0·ai-ml·MIT

Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger on

Install on your platform

Showing OpenClaw.

  1. 1

    Run this in your terminal

    terminal
    $

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-ownership-map/SKILL.md
Scanned
8 files, 2,440 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 analyzes Git repositories to determine the individuals responsible for specific files within them. It calculates the "bus factor," representing the number of people who own critical code, and identifies owners of potentially sensitive code sections. The results can be exported in CSV or JSON formats, making them suitable for integration with graph databases and visualization tools.

When to use it

  • Security Audits: Identify potential single points of failure by determining which files have limited ownership.
  • Onboarding New Engineers: Quickly understand code ownership and dependencies when a new team member joins.
  • Risk Assessment: Evaluate the risk associated with sensitive code sections lacking clear ownership.
  • Knowledge Transfer Planning: Facilitate knowledge transfer efforts by pinpointing individuals responsible for key components.

Key capabilities

  • Analyzes Git repositories to map people to files.
  • Calculates bus factor based on file ownership.
  • Identifies owners of sensitive code.
  • Exports data in CSV and JSON formats.
  • Triggers automated analysis.

Example prompts

  • "Analyze the repository https://github.com/openai/whisper for security ownership."
  • "Generate a CSV report showing file ownership and bus factor for the llama project."
  • "Identify owners of files containing API keys in the stable-diffusion repository, export as JSON."

Tips & gotchas

  • The skill requires read access to the specified Git repository. Ensure appropriate permissions are granted before running the analysis.
  • Accuracy depends on commit history and consistent coding practices; incomplete or obscured ownership information may affect results.