Skip to content
TrustedSkillsbeta
Back to all skills

Audit

Listed
melodic-software·vlatest·security·MIT

Analyzes software code for musicality potential, identifying rhythmic patterns and harmonic structures suitable for audio generation.

Repository

Install on your platform

This skill no longer installs under the name audit. SKILL.md has no name/description frontmatter, so the skills CLI skips it.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

melodic-software

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 failed 2 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    SKILL.md frontmatter is missing name.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: failed

    Contacts 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: code.claude.com, json.schemastore.org.

    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.

    Hosts contacted

    code.claude.comundeclaredgithub.comsource hostjson.schemastore.orgundeclaredraw.githubusercontent.comsource host

    What it found (3 of 21)

    • plugins/attribution/skills/audit/scripts/emit-findings.test.sh:115contacts code.claude.com
      "source": {"url": "https://code.claude.com/docs/skills.md", "fetched": "2026-08-27",
    • plugins/attribution/skills/audit/scripts/emit-findings.test.sh:220contacts code.claude.com
      NF_SEARCHED='["https://code.claude.com/docs/llms.txt","site search: nf-surface.example"]'
    • plugins/attribution/skills/audit/scripts/emit-findings.test.sh:297contacts code.claude.com
      assert_contains "the copy row names its source" "$COPY_ROW" "https://code.claude.com/docs/skills.md"

  • 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 melodic-software/claude-code-plugins at a57dc67851.

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

Commit
a57dc67851
Manifest
plugins/ai-slop/skills/audit/SKILL.md
Scanned
60 files, 23,656 lines
Copies in repo
3 — all of them scanned
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 performs software audits, identifying potential vulnerabilities and areas of non-compliance. It can analyze code repositories to detect security flaws and adherence to coding standards. The audit results are presented in a structured format, facilitating remediation efforts.

When to use it

  • Security Review: Before deploying new code or releasing an application, ensure its security posture through automated auditing.
  • Compliance Checks: Verify that your codebase adheres to specific industry regulations or internal coding guidelines.
  • Codebase Assessment: Gain a comprehensive understanding of the quality and potential risks within an existing software project.
  • Due Diligence: Evaluate the technical health of a software asset during acquisition or merger activities.

Key capabilities

  • Vulnerability detection
  • Coding standard adherence checks
  • Structured audit reporting
  • Repository analysis

Example prompts

  • "Audit this GitHub repository for security vulnerabilities: [repository URL]"
  • "Perform a compliance check against the OWASP Top 10 on this code."
  • "Analyze this codebase and report any deviations from our internal coding standards."

Tips & gotchas

The effectiveness of the audit depends heavily on the quality and completeness of the provided codebase. Ensure that all relevant files are included for accurate results.