agentleFS
Starr-delStarr-del/ShipSafe/skills/bundle-weight/SKILL.md

bundle-weight

Skill0 starsChanged 5 months agoMITView on GitHub

Audit package.json for heavyweight dependencies, duplicate-purpose libraries, and misplaced build tools before they bloat bundles and slow cold starts. Use when the user mentions slow builds, large bundles, slow page loads, serverless cold starts, 'why is my app heavy', dependency cleanup, or when reviewing any package.json. Runs fully offline — no API keys, no network, no credentials.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All paths below are relative to this skill's directory (bundle-weight/).

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

bundle-weight

Part of shipsafe — offline deploy-safety skills. Every script is stdlib-only Python 3.8+; nothing leaves the machine.

python3 scripts/audit_weight.py <project_root> [--json]

Three checks against curated tables:

  • HEAVY_DEP — packages with well-known lighter or native replacements (moment → date-fns/Intl, axios → fetch, uuid → crypto.randomUUID, dotenv → platform-native env, deprecated request...).
  • DUPLICATE_PURPOSE — two+ libraries doing the same job (HTTP clients, date libs, state managers, validators, CSS-in-JS). Each ships in full.
  • MISPLACED_TYPES — @types/*, typescript, eslint etc. in dependencies instead of devDependencies, slowing production installs.

Interpretation guidance: these are review prompts, not mandates. A flagged dep that the project uses deeply (e.g. rxjs with heavy operator use, axios with interceptors) is a legitimate keep — confirm usage before recommending removal, and prefer suggesting the migration only when the usage is shallow.

Exit codes: 0 clean, 1 findings.

All paths below are relative to this skill's directory (bundle-weight/).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.