memory-report

Analyze ROM and RAM usage in embedded ELF and object files.

1|Updated May 19, 2026
One-click install
npx skills add https://github.com/auroralabs-loci/loci-claude --skill memory-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-report
Source: https://github.com/auroralabs-loci/loci-claude/tree/main/skills/memory-report
Command: npx skills add https://github.com/auroralabs-loci/loci-claude --skill memory-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides fast, actionable memory visibility for embedded firmware builds so developers can understand how much flash and RAM their compiled binaries consume and where the largest consumers live.

Core Features & Use Cases

  • Section-level breakdowns: reports per-section sizes and types for linked ELFs and relocatable object files.
  • ROM/RAM summaries and top consumers: aggregates totals and lists largest functions and variables to target for optimization.
  • Delta comparisons and region budgets: compares two builds for size regressions and optionally reports memory region usage when a linker map file is provided.
  • Use Case: use it during code review or CI to ensure a change did not unexpectedly increase flash or RAM usage.

Quick Start

Request a memory report by providing the compiled ELF or object file and optionally a linker map file to see section breakdowns, totals, and top consumers.

Frequently Asked Questions about memory-report

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

FAQPage Schema
How do I check ROM and RAM usage in an embedded ELF file?

You can analyze ROM and RAM usage by providing the compiled embedded ELF or object file to generate section-level breakdowns, memory summaries, and top consumer lists for flash and RAM budgets.

How do I detect flash size regressions between firmware builds?

Detect flash size regressions by running delta comparisons across two firmware builds, which calculates symbol and section size differences to pinpoint unexpected ROM or RAM increases.

Can I analyze memory usage with a linker map file for embedded projects?

Yes, providing a linker map file alongside the linked ELF binary generates optional memory region budgets and reports allocation against defined memory regions for embedded firmware.

What is the best way to find the largest functions consuming flash memory?

The best way to find the largest functions consuming flash memory is to generate a memory report that aggregates ROM summaries and lists top consumers, targeting the largest symbols for optimization.

Does memory analysis work with relocatable object files or only linked binaries?

Memory analysis works with both linked ELF binaries and relocatable object files, providing section-level size breakdowns and type reporting for compiled firmware at any build stage.

When do I need to analyze ROM and RAM budgets for embedded firmware?

You need to analyze ROM and RAM budgets during code review or CI pipelines to ensure code changes do not unexpectedly increase flash or RAM usage beyond embedded hardware constraints.