free-memory

Audit memory usage, classify processes, and reclaim RAM after per-PID confirmation.

12|2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/Loringtonian/second-brain-template --skill free-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: free-memory
Source: https://github.com/Loringtonian/second-brain-template/tree/main/.claude/skills/free-memory
Command: npx skills add https://github.com/Loringtonian/second-brain-template --skill free-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly find what is actually consuming memory on your machine and safely reclaim RAM when the system is slow, swapping, or under pressure.

Core Features & Use Cases

  • Footprint-Accurate Audit: Inspects processes using memory-aware metrics so swapped or compressed usage is not missed.
  • Safe Process Triage: Separates disposable servers, uncertain processes, interactive sessions, and supervised services into clear buckets before any action is taken.
  • Explicit Confirmation Workflow: Kills only the PIDs you approve, never the current session, and verifies that memory was recovered afterward.
  • Use Case: A developer notices their laptop becoming sluggish after leaving local servers and tools open overnight, then uses this Skill to identify safe targets and free memory without risking active work.

Quick Start

Ask the free-memory skill to audit current memory usage, show the kill candidates, and reclaim RAM only after you confirm which PIDs to terminate.

Frequently Asked Questions about free-memory

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

FAQPage Schema
How do I safely reclaim RAM on macOS without killing active work?

To safely reclaim RAM, audit memory usage with footprint-accurate metrics, bucket processes by disposal safety, and terminate only explicitly confirmed PIDs. This prevents killing active work or interactive sessions.

Why does my macOS system keep swapping and how can I find the processes causing it?

Systems swap when memory is exhausted by forgotten dev servers or stale sessions. You can find the cause by inspecting processes using footprint-accurate memory-aware metrics that reveal swapped or compressed usage missed by standard tools.

How do I clean up forgotten local dev servers consuming excessive RAM?

Clean up forgotten dev servers by running a safe process triage that separates disposable servers from interactive sessions, then approve graceful termination for specific PIDs to recover memory and reduce system pressure.

Can I audit memory usage on my local machine without accidentally killing supervised services?

Yes, you can audit memory safely using a bucketed classification system that separates supervised services and interactive sessions from disposable processes, requiring explicit per-PID confirmation before any termination action is taken.

What is the best way to free memory from stale interactive sessions on a slow system?

The best way to free memory from stale interactive sessions is to perform a process audit, review the bucketed kill candidates, and manually confirm which PIDs to gracefully terminate, ensuring memory is recovered without unsaved data loss.

Does manual RAM reclamation report memory before and after termination?

Yes, manual RAM reclamation includes before-and-after memory reporting to verify that memory was actually recovered after you confirm and gracefully terminate the targeted processes consuming excessive RAM and swap.