Skip to content
TrustedSkillsbeta
Back to all skills

Traceability Auditor

Checked
nahisaho·vlatest·security·MIT

This Traceability Auditor verifies data lineage and compliance records, ensuring accurate tracking & mitigating risks in complex supply chains.

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 nahisaho/codegraphmcpserver --skill traceability-auditor -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

nahisaho

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 nahisaho/codegraphmcpserver at d953aa5ad4.

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

Scanned
1 file, 368 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 Traceability Auditor skill analyzes code and dependencies to identify missing or incomplete traceability links. It helps ensure that software development processes adhere to established standards, allowing for easier debugging and compliance verification. This includes identifying gaps in requirements coverage and verifying the accuracy of dependency relationships within a codebase.

When to use it

  • Compliance Audits: Verify adherence to regulatory requirements (e.g., GDPR, HIPAA) where traceability is mandated.
  • Debugging Complex Systems: Quickly identify which code components are linked to specific requirements for easier root cause analysis.
  • Dependency Management: Validate that all dependencies have associated documentation and rationale.
  • Requirements Coverage Analysis: Determine if all project requirements are adequately implemented in the codebase.

Key capabilities

  • Code analysis
  • Dependency tracking
  • Traceability link verification
  • Gap identification

Example prompts

  • "Analyze this code repository for missing traceability links to user stories."
  • "Verify that all dependencies in this project have documented rationales."
  • "Show me the requirements coverage for module X."

Tips & gotchas

The accuracy of the audit depends on the quality and completeness of existing traceability information. Ensure your codebase includes clear linking between code, requirements, and other relevant artifacts for optimal results.