Skip to content
TrustedSkillsbeta
Back to all skills

Dead Code

Checked
parcadei·vlatest·backend·MIT

Identifies and highlights unused or unreachable code segments, improving codebase clarity and reducing potential maintenance overhead.

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 parcadei/continuous-claude-v3 --skill dead-code -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

parcadei

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 parcadei/continuous-claude-v3 at d07ff4b06b.

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

Scanned
1 file, 78 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

dead-code

What it does

This skill enables AI agents to identify and remove unused, obsolete, or redundant code within software projects. It streamlines maintenance by automatically scanning repositories to find functions, variables, or files that are no longer referenced or executed.

When to use it

  • Refactoring legacy codebases where documentation is missing or outdated.
  • Reducing technical debt before deploying a new feature to production.
  • Cleaning up projects after deleting specific modules or dependencies.
  • Preparing code for performance optimization by eliminating bloat.

Key capabilities

  • Automated detection of dead functions and variables.
  • Identification of unused imports and dependencies.
  • Removal of obsolete files from the project structure.
  • Integration with continuous integration workflows for ongoing cleanup.

Example prompts

  • "Scan my current repository and list all JavaScript functions that have never been called."
  • "Remove any Python modules in this folder that are no longer imported by other scripts."
  • "Identify unused CSS classes and delete them from the stylesheet to reduce file size."

Tips & gotchas

Ensure you back up your code before running automated deletion scripts, as false positives can inadvertently remove functional logic. This skill works best on projects with established build pipelines where execution paths are clear.