Skip to content
Agentmart
Submit a tool

project-cleanup

For the Technical Writer (10).

Skill by 6SNT-RADIO

IndexedMIT
Write a review

Chalk Labs

Need help deploying project-cleanup?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/6snt-radio-project-cleanup

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

For the Technical Writer (10). Inventory and delete (only with an orchestrator-approved list) obsolete root files; no archiving, no quarantine, no 'just in case'. Use it for active root cleanup.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/project-cleanup

What's inside

Skill name
project-cleanup
Description
For the Technical Writer (10). Inventory and delete (only with an orchestrator-approved list) obsolete root files; no archiving, no quarantine, no 'just in case'. Use it for active root cleanup.
License
MIT
Instructions
43 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# SKILL: project-cleanup
## For: Agent 10 — TECHNICAL WRITER
## Version: 1.0.0

## Core principle
Deletion criterion: "Does this file serve anyone working on the project today?"
If NOT → a deletion candidate. No quarantine. No archiving. No "just in case".
With orchestrator approval → delete for good.
If it's in Git, it's in the history. It doesn't need to exist live.

## Process
STEP 1 — Inventory: list all non-code files with name, date, size, description.
STEP 2 — Classify: ACTIVE (don't touch) / OBSOLETE (candidate) / HISTORICAL (evaluate) / DUPLICATE (delete the old one).
STEP 3 — Candidate list: name, why it's a candidate, what replaces it, risk (low/medium/high).
STEP 4 — Present CLEANUP_LIST.md to the orchestrator. Delete nothing without approval.
STEP 5 — With approval → delete and report.

## OBSOLETE — delete with approval
Prompts from earlier versions, specs of already-built features, resolved QA reports, unused experimentation files, intermediate documents with an approved final version.

## HISTORICAL — evaluate before deciding
Architecture decisions (keep if they explain what was discarded), very old changelogs (if the info is already in Git → delete), specs of cancelled features (delete — if resumed, they're redesigned).

## NEVER DELETE without consensus
× Active AGENTS.md, README.md, CLAUDE.md
× Runbooks for processes in use
× Contracts of active APIs
× Files the code references directly
× .env.example and environment configs

## Signs of a contaminated root
More than 5 .md in the root beyond the standard ones, files named "prompt_X/fix_v1/issues_vX/spec_draft", multiple versions of the same doc, files untouched for over 3 months, more docs than code.

## CLEANUP_LIST.md structure
Summary (inventoried/candidates/kept) → Candidate table (file/category/reason/risk/replaced by) → Kept files with description → Pending decision

## Mistakes to avoid
× Deleting without an approved list
× Archiving in old/ or backup/ instead of deleting
× Deleting files the code references
× "Just in case" as a keep criterion

From 6SNT-RADIO/6SNT-Studio, MIT.

More from 6SNT-RADIO/6SNT-Studio

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Jun 7, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from 6SNT-RADIO

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get project-cleanup running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying project-cleanup?

CallGet help
Cite this page

project-cleanup skill. Agent Mart. https://agentmart.dev/skills/6snt-radio-project-cleanup (last updated 2026-10-24)