Dead code

Skill ulpi-io/plugin-marketplace/plugins/parcadei/skills/dead-code

A curated collection of 7,800+ agent skills for Claude Desktop, sourced from skills.sh

Install

npx -y skills add ulpi-io/plugin-marketplace --skill dead-code

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Find unused functions and dead code in the codebase

SKILL.md

1.7 KB, as published. Nobody here has run it

Dead Code Detection

Find unused functions and dead code using TLDR static analysis.

Quick Start

# Scan entire project
tldr dead .

# Scan specific directory
tldr dead src/

# Specify entry points (functions to exclude from analysis)
tldr dead . --entry main cli test_

# Specify language
tldr dead . --lang python
tldr dead . --lang typescript

Output Format

Dead code analysis:
  Total functions: 150
  Dead functions: 12

Unused functions:
  - old_helper (src/utils.py:42)
  - deprecated_func (src/legacy.py:15)
  - _unused_method (src/api.py:230)

Cross-Platform

Works on Windows, Mac, and Linux (including WSL).

# Windows (PowerShell)
tldr dead .

# Mac/Linux
tldr dead .

Entry Points

Functions matching entry patterns are excluded from dead code analysis:

main, cli - Application entry points
test_*, *_test - Test functions
setup, teardown - Fixtures
@app.route, @api.endpoint - Framework handlers

# Custom entry points
tldr dead src/ --entry main api_handler background_job

Integration

This skill replaces the session-start-dead-code hook with on-demand analysis.

Approach	Pros	Cons
Hook (removed)	Automatic	Slowed startup by 3s
Skill (this)	On-demand, fast	Manual invocation

Related Commands

# Impact analysis (who calls this?)
tldr impact func_name .

# Architecture layers
tldr arch src/

# Full codebase structure
tldr structure . --lang python

Gives 0 of the 12 instructions most refactoring skills give

Counted across 521 of the 525 authors here whose files we hold, read 2026-08-06

run tests after each changein 59 of 521, across 56 files
write tests before refactoringin 27 of 521, across 24 files
preserve external behaviorin 26 of 521, across 22 files
remove dead codein 25 of 521, across 24 files
make small incremental changesin 20 of 521, across 17 files
break the implementation into tiny commitsin 18 of 521, across 5 files
ask the user about alternative optionsin 17 of 521, across 4 files
create a GitHub issue with the planin 17 of 521, across 4 files
explore the repository to verify assertionsin 17 of 521, across 4 files
interview the user about the refactorin 16 of 521, across 3 files
check the codebase for test coveragein 16 of 521, across 3 files
refactor one thing at a timein 16 of 521, across 12 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.