Skip to content
TrustedSkillsbeta
Back to all skills

Security Ownership Map

Checked
tech-leads-club·vlatest·security

Visually maps security ownership across your tech leads' club, identifying gaps and clarifying responsibilities for improved protection.

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 tech-leads-club/agent-skills --skill security-ownership-map -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

tech-leads-club

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 tech-leads-club/agent-skills at 6df68d5202.

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

Commit
6df68d5202
Manifest
packages/skills-catalog/skills/(security)/security-ownership-map/SKILL.md
Scanned
7 files, 2,439 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

The security-ownership-map skill enables AI agents to dynamically visualize and analyze the distribution of security responsibilities across an organization. It helps identify gaps in accountability, map ownership of specific assets, and streamline incident response workflows by connecting roles to critical security domains.

When to use it

  • During post-incident reviews to determine which team or individual was responsible for a specific vulnerability or breach.
  • When onboarding new security engineers to quickly understand who owns access controls, network segmentation, or application hardening.
  • To audit current governance structures and ensure every critical asset has a clearly assigned owner before an external audit.
  • While designing a Zero Trust architecture to map identity ownership against resource protection duties.

Key capabilities

  • Generates interactive maps linking security assets to specific organizational roles and teams.
  • Identifies unassigned or ambiguous ownership areas that create blind spots in the security posture.
  • Correlates incident data with responsible owners to accelerate root cause analysis.
  • Provides a structured view of the "who does what" landscape for compliance reporting.

Example prompts

  • "Generate a security ownership map for our cloud infrastructure, highlighting who is responsible for IAM policies versus network firewalls."
  • "Identify any critical security assets in our current architecture that currently lack a defined owner."
  • "Map the response chain of command for a potential data breach involving customer PII based on our existing team structure."

Tips & gotchas

Ensure your organization has recently updated its RACI matrices or role definitions, as the skill relies on accurate input data to produce meaningful maps. This tool is most effective when used proactively during architecture reviews rather than solely reacting to incidents.