scaffolding-delete-pass

Audit hooks, CLAUDE.md rules, skills, and agents to propose removals of obsolete model-compensation scaffolding.

2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/DanielH2018/server --skill scaffolding-delete-pass-danielh2018
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scaffolding-delete-pass
Source: https://github.com/DanielH2018/server/tree/main/.claude/skills/scaffolding-delete-pass
Command: npx skills add https://github.com/DanielH2018/server --skill scaffolding-delete-pass-danielh2018

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI assistant configurations accumulate rules, hooks, and skills that compensate for older model weaknesses, and nothing ever removes them. This Skill audits that scaffolding at a model upgrade and proposes deletions backed by evidence, keeping the configuration lean and justified. ## Core Features & Use Cases - Compounds vs. compensates classification: Sorts each rule into knowledge that compounds (repo-specific facts) versus scaffolding that compensates for model weaknesses and should decay. - Evidence-based audit procedure: Re-runs the failure each rule guards against, queries OTEL for 30-day invocation counts of skills, agents, and memory entries, and reads candidates cheapest-to-reverse first. - Structured removal proposals: Emits one block per candidate with location, original rationale, evidence it is no longer needed, reversal command, and risk if wrong — it proposes, never applies. - Use Case: After upgrading to a new model, run this pass to discover that a retry-on-classifier-denial hook and tool-routing prose in CLAUDE.md are no longer needed, and produce a reviewable list of deletions with rollback commands. ## Quick Start Run the scaffolding delete pass to audit my hooks, CLAUDE.md rules, skills, and agents and propose what the new model no longer needs.

Frequently Asked Questions about scaffolding-delete-pass

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up unused AI assistant rules and hooks?▼

Run an audit that classifies each rule as compounding repo knowledge or compensating scaffolding, checks 30-day invocation counts, and re-tests whether the new model still fails without the rule. Propose deletions with evidence and reversal commands rather than applying them directly.

When should I remove CLAUDE.md instructions after a model upgrade?▼

Remove instructions when the new model demonstrably performs the behavior unprompted. Re-run the exact failure each rule guards against; if the model now passes without the rule, the rule is a deletion candidate.

How do I tell if a skill or agent is still being used?▼

Query OTEL telemetry for the last 30 days of subagent, skill, and memory invocations. Zero invocations suggests a candidate for removal, but first name the rare case it may cover, such as disaster recovery, before dropping it.

Why is removing a hook riskier than removing documentation?▼

Hooks change what the harness permits, so a wrong removal fails open silently. Removing a hook requires paired evidence: the input it used to reject, plus a run showing that input is now impossible or rejected elsewhere.

What if the audit finds nothing to remove?▼

A run that proposes nothing is a legitimate result, but it must still list what was examined and what evidence kept each item in place. An empty claim of nothing to remove is indistinguishable from not running the pass.