Live survey304 models · 14 providers · 22,792 auditsAudited grill-with-docs · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

memory-analysis

skill · leokemp223/embed-ai-toolLicence not declaredAudited 31 Oct 2026 · source f2eee4d05246

★ 1,053pushed 72 days ago
✓SAFEGrade B · 89/100 · 31 Oct 2026 · f2eee4d
1,053repo stars · whole leokemp223/embed-ai-tool

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit f2eee4d05246 and found no filesystem, network or shell access and no hard-coded secrets. What it does: 当需要解析 .map 文件或 ELF 获取固件内存使用报告、符号大小排名或版本对比时使用。

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “memory-analysis (leokemp223/embed-ai-tool)”. Retrieved 31 Oct 2026. https://modelsatlas.com/skills/leokemp223/memory-analysis

Trust audit

Audit 0.4.1 · source read 31 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium1 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS1
L1 Static sourceSecrets, path traversal, supply chain, hidden codePASS0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass, no license.

Findings (1)

LOWInventory / provenanceinv.no_license
F-13 Inventory / provenanceCWE-1104Layer L0
Why
no LICENSE file and no repo licence
Fix
add a licence

Audit 0.4.1 · source sha f2eee4d05246 · 31 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publisherleokemp223 GitHub userOwner of the repository this skill is read from
  • Source folderleokemp223/embed-ai-tool/skills/memory-analysisThe exact folder we audited
  • LicenceNot declaredAs the repository states it
  • Commit pinned for this verdictf2eee4d05246A new audit runs when the source changes
  • Repository statusNot archivedLast push 72 days ago
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: 当需要解析 .map 文件或 ELF 获取固件内存使用报告、符号大小排名或版本对比时使用。

---
name: memory-analysis
description: 当需要解析 .map 文件或 ELF 获取固件内存使用报告、符号大小排名或版本对比时使用。
---

# 固件内存分析

## 适用场景

- 构建完成后需要了解固件的 Flash/RAM 使用情况。
- 需要找出占用空间最大的函数或变量。
- 需要对比两次构建的内存变化,追踪代码膨胀。
- 需要确认固件是否即将超出芯片内存限制。
- 需要解析链接脚本获取芯片 Flash/RAM 总容量。

## 必要输入

- `.map` 文件路径(GCC/ARM 链接器生成),或 ELF 文件路径。
- 可选的链接脚本路径(用于计算使用率百分比)。
- 可选的告警阈值和 Top-N 符号数量。

## 自动探测

- `--scan` 模式自动搜索构建目录中的 `.map` 和 ELF 文件。
- 解析 `.map` 文件中的 `Memory Configuration` 块获取 FLASH/RAM 总容量。
- 若提供链接脚本,从 `MEMORY {}` 块解析容量信息。
- 自动检测 `arm-none-eabi-size` 和 `arm-none-eabi-readelf` 可用性。

## 执行步骤

1. 先阅读 [references/usage.md](references/usage.md),确认本次是环境探测、构建目录扫描,还是执行分析。
2. 若不确定工具是否可用,先运行 [scripts/memory_analyzer.py](scripts/memory_analyzer.py) 的 `--detect` 模式确认。
3. 使用 `--scan <build_dir>` 自动查找可分析的文件。
4. 使用 `--map-file` 或 `--elf` 执行内存分析。
5. 可选使用 `--linker-script` 获取总容量并计算使用率。
6. 使用 `--top <N>` 查看占用最大的符号。
7. 使用 `--compare` 对比两个 `.map` 文件的差异。

## 失败分流

- 当 `arm-none-eabi-size` 或 `arm-none-eabi-readelf` 不可用且需要 ELF 分析时,返回 `environment-missing`。
- 当指定的 `.map` 或 ELF 文件不存在时,返回 `artifact-missing`。
- 当 `.map` 文件格式无法识别或解析失败时,返回 `project-config-error`。
- 当内存使用率超过告警阈值时,在成功结果中附带告警信息。

## 平台说明

- `.map` 文件解析使用纯正则,无需外部工具,全平台可用。
- ELF 分析需要 `arm-none-eabi-size`,通常随交叉编译工具链安装。
- 链接脚本解析使用纯正则,支持 GCC LD 格式。

## 输出约定

- 输出各 section(.text, .rodata, .data, .bss)的大小和地址。
- 输出 Flash 使用量(.text + .rodata + .data)和 RAM 使用量(.data + .bss)。
- 若有总容量信息,输出使用率百分比和告警状态。
- 输出按大小排序的 Top-N 符号列表。
- 对比模式输出各 section 和符号的增减变化。

## 交接关系

- 当内存即将溢出需要优化时,建议用户审查 Top-N 大符号。
- 当需要定位具体函数在代码中的位置时,可配合 IDE 或 `grep` 使用。

Excerpt, first 1,532 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit f2eee4d

Download folder ↗
git clone https://github.com/leokemp223/embed-ai-tool
git -C embed-ai-tool checkout f2eee4d05246

The author documents no install command, so this uses the repository directly. Our verdict covers commit f2eee4d05246 only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source f2eee4d05246

README badge

For maintainers · shows the latest audit

ModelsAtlas: SAFE BMODELSATLASSAFE · B
[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/leokemp223/memory-analysis/badge.svg)](https://modelsatlas.com/skills/leokemp223/memory-analysis/)

The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.

Add this badge to your README

[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/leokemp223/memory-analysis/badge.svg)](https://modelsatlas.com/skills/leokemp223/memory-analysis/)

Questions about memory-analysis

What does the memory-analysis skill do?
面向 AI 编程助手的嵌入式开发技能集,为大模型提供 MCU 固件开发全流程能力。涵盖多工具链构建(Keil / IAR / CMake / PlatformIO)、烧录、GDB 调试、串口监视、Modbus / CAN / VISA 协议调试、外设驱动适配及流水线编排,支持 Linux、macOS、Windows 三平台。
Is memory-analysis safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can memory-analysis access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (f2eee4d05246), read on 2026-10-31. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.