system-diet

Inventory and remove 20% of active tools, plugins, and automation pipelines.

1|Updated May 14, 2026
One-click install
npx skills add https://github.com/epicsagas/epicsagas --skill system-diet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-diet
Source: https://github.com/epicsagas/epicsagas/tree/main/skills/system-diet
Command: npx skills add https://github.com/epicsagas/epicsagas --skill system-diet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

System Diet reduces toolchain complexity by forcing removal of 20% of active tools, plugins, and automation pipelines, preventing stagnation and maintenance overhead.

Core Features & Use Cases

  • Inventory and audits of tools, plugins, and scripts
  • Classification of usage and value to determine what to remove
  • Documentation of removals and scheduling of next audits
  • Anti-rationalization safeguards to ensure real reductions

Quick Start

Initiate a quarterly system-diet audit to inventory all tools and remove at least 20% of inactive or low-value components.

Frequently Asked Questions about system-diet

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

FAQPage Schema
How do I audit and remove unused plugins and packages to reduce toolchain complexity?

Audit toolchain complexity by inventorying plugins, classifying usage, assessing value, and documenting removals to eliminate at least 20% of inactive or low-value components.

What is the best way to prune shell aliases and automation scripts?

The best way to prune shell aliases and automation scripts is to inventory them, evaluate their current value, and remove 20% during a scheduled quarterly audit to lower maintenance overhead.

How do I prevent rationalization when deciding which tools to remove?

Prevent rationalization during tool removal by applying structured anti-rationalization safeguards that enforce real reductions based on value assessment rather than keeping components just in case.

Can I use a quarterly tool diet audit for Homebrew and Cargo packages?

Yes, you can apply a quarterly tool diet audit to Homebrew and Cargo packages by inventorying installed packages, classifying usage, and pruning 20% to reduce infrastructure complexity.

When should I schedule my next toolchain complexity audit?

Schedule your next toolchain complexity audit quarterly to continuously identify and remove 20% of inactive or low-value tools, preventing stagnation and maintaining optimization.