Project Graveyard
Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions abandoned, unfinished, or old side projects, asks "what should I finish", wants to revive or resurrect a project, says "run the graveyard", wonders why they never finish anything, or is about to start a new project that sounds like one they already built. Runs entirely locally.
Install
npx skills add Shubhamsaboo/awesome-llm-apps --skill project-graveyardgit clone --depth 1 https://github.com/Shubhamsaboo/awesome-llm-apps.git /tmp/awesome-llm-apps
mkdir -p ~/.claude/skills
cp -r /tmp/awesome-llm-apps/agent_skills/project-graveyard ~/.claude/skills/project-graveyardPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Project Graveyard Every developer has a folder full of dead projects. Nobody has ever gotten an autopsy report. This skill scans the machine for abandoned repos, works out why each one died from its git history, finds the user's personal death patterns, and picks the one corpse worth digging up — then helps ship it. Everything runs locally. No API, no network, nothing leaves the machine. ## When to use - The user asks about abandoned/unfinished/old side projects, or what to finish - The user wants to revive, resurrect, or "finally ship" something - The user asks why they never finish projects - The user proposes a new project — check the graveyard first (see Necromancer mode). There's a decent chance they already built half of it. ## When not to use - Cleaning up disk space or node_modules — that's `kondo`/`npkill`, not this - Archiving repos on GitHub — this works on local clones and never-pushed work - Analyzing one specific repo's history in depth — just read the git log ## Run it ```bash python3 scripts/graveyard.py ~/dev ~/projects ``` Point it at wherever projects actually live. If you don't know where that is, ask — one question beats sweeping someone's home directory uninvited. No args scans the usual suspects (~/dev, ~/projects, ~/code, ~/Desktop, ...). Useful flags: - `--days 90` — how long silent before a repo counts as dead (default 45) - `--json report.json` — full machine-readable data
Details
- Skill name
project-graveyard- Repository
- Shubhamsaboo/awesome-llm-apps
- Path
agent_skills/project-graveyard/SKILL.md- License
- Apache-2.0
- Repo updated
- 18 November 2026
FAQ
What does the Project Graveyard skill do?
Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions abandoned, unfinished, or old side projects, asks "what should I finish", wants to revive or resurrect a project, says "run the graveyard", wonders why they never finish anything, or is about to start a new project that sounds like one they already built. Runs entirely locally.
How do I install the Project Graveyard skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Shubhamsaboo/awesome-llm-apps --skill project-graveyard. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Project Graveyard popular?
It lives in Shubhamsaboo/awesome-llm-apps, which has 145,013 GitHub stars and 21,357 forks.
Related skills
Advisor Orchestrator Worker
145kShubhamsaboo/awesome-llm-apps
Use when a task is too large for one model pass, needs parallel research or generation across many subtasks (like researching a dozen competitors at once), or the user asks to orchestrate multiple models, split work across a model team, run an advisor-worker loop, have a stronger model review the plan while cheap workers execute, or says "too big for one model" or "fan this out". Not for single-file edits or tasks one model handles in one pass.
Chatgpt App Builder
145kShubhamsaboo/awesome-llm-apps
DEPRECATED: This skill has been replaced by `mcp-app-builder`. Check if `mcp-app-builder` is available in the skills folder. If not, install it: `npx skills install mcp-use/mcp-use --skill mcp-app-builder` Use `mcp-app-builder` instead of this skill. Build ChatGPT apps with interactive widgets using mcp-use and OpenAI Apps SDK. Use when creating ChatGPT apps, building MCP servers with widgets, defining React widgets, working with Apps SDK, or when user mentions ChatGPT widgets, mcp-use widgets, or Apps SDK development.
Commit Archaeologist
145kShubhamsaboo/awesome-llm-apps
Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite, refactor, or risky edit. Runs entirely locally.
Scope Creep Detector
145kShubhamsaboo/awesome-llm-apps
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad pull requests, changes that grew beyond a fix, dependency additions, public API renames, config or CI edits, oversized hunks, and formatting-only files. Use when the user asks whether a change grew beyond the fix, a PR is too broad, or what unrelated stuff they touched, and wants keep, split, or justify guidance. Operates locally and offline.
MCP Builder
145kShubhamsaboo/awesome-llm-apps
DEPRECATED: This skill has been replaced by `mcp-app-builder`. Check if `mcp-app-builder` is available in the skills folder. If not, install it: `npx skills install mcp-use/mcp-use --skill mcp-app-builder` Use `mcp-app-builder` instead of this skill. Build Model Context Protocol (MCP) servers with mcp-use framework. Use when creating MCP servers, defining tools/resources/prompts, working with mcp-use, bootstrapping MCP projects, or when user mentions MCP development, tools, resources, or prompts.
Thinking Out Loud
145kShubhamsaboo/awesome-llm-apps
A contract for what the agent does when a long, messy, stream-of-consciousness ramble arrives (usually voice dictation): act on nothing until the echo brief is approved. The echo audits the entire transfer, mission, locked decisions and constraints, open questions, flips and parked tangents, with the model's inferences and guesses quarantined away from the user's own phrasing, so the user verifies what the model believes, not just what it doubts. Use when the user says "let me think out loud" or wants to ramble a bit before building anything, when a message opens with a speech-to-text preamble
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.