How do I install the Orbitdock Memory Profiling skill?

Run npx skillmds@latest add tomevault-io/orbitdock-memory-profiling in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Orbitdock Memory Profiling safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Orbitdock Memory Profiling?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Orbitdock Memory Profiling free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Orbitdock Memory Profiling?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Orbitdock Memory Profiling by tomevault-io

Name: Orbitdock Memory Profiling
Author: tomevault-io

Orbitdock Memory Profiling

Profile OrbitDock memory and runtime behavior using macOS CLI tools. Use when investigating high memory usage, memory growth over time, Core Animation or mmap/vm_allocate-heavy stacks, leak suspicion, or regressions that need reproducible vmmap/sample/xctrace evidence. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

OrbitDock Memory Profiling

Overview

Capture reproducible OrbitDock memory artifacts from the command line, then map hotspots back to likely UI or rendering causes.

Workflow

Identify the target process.
Capture baseline snapshots.
Reproduce the issue.
Capture post-repro snapshots.
Compare outputs and form hypotheses.

Prefer using scripts/capture_memory_profile.sh for consistency.

Run The Script

Run a full capture for the latest OrbitDock process:

scripts/capture_memory_profile.sh

Run a targeted capture:

scripts/capture_memory_profile.sh \
  --pid 9718 \
  --sample-seconds 5 \
  --trace-seconds 10 \
  --out-dir /tmp/orbitdock-profile

Manual Commands

Use these directly when you need finer control:

pgrep -lf OrbitDock
ps -o pid,ppid,rss,vsz,%mem,etime,command -p <PID>
vmmap -summary <PID>
sample <PID> 5 1
xctrace record --template 'Allocations' --attach <PID> --time-limit 10s --output /tmp/orbitdock-alloc.trace
xctrace export --input /tmp/orbitdock-alloc.trace --toc

Permission Handling

If vmmap, sample, leaks, or xctrace fails with permission errors, request elevated execution and rerun the same command.

Interpretation Guide

Read references/interpretation.md for quick heuristics on:

CoreAnimation and image-backed growth
MALLOC_SMALL and fragmentation signals
Peak vs current footprint interpretation
Stack patterns that implicate rendering, focus rings, or image decode paths

Output Expectations

The capture script writes:

ps.txt
vmmap-summary.txt
sample.txt
allocations.trace and xctrace-toc.xml (if tracing enabled)
capture-summary.txt

Use these artifacts to compare before/after repro windows and support fixes with evidence.

Source: Robdel12/OrbitDock — distributed by TomeVault.

---name: orbitdock-memory-profilingdescription: Profile OrbitDock memory and runtime behavior using macOS CLI tools. Use when investigating high memory usage, memory growth over time, Core Animation or mmap/vm_allocate-heavy stacks, leak suspicion, or regressions that need reproducible vmmap/sample/xctrace evidence. Use when this capability is needed.---# OrbitDock Memory Profiling## OverviewCapture reproducible OrbitDock memory artifacts from the command line, then map hotspots back to likely UI or rendering causes.## Workflow1. Identify the target process.2. Capture baseline snapshots.3. Reproduce the issue.4. Capture post-repro snapshots.5. Compare outputs and form hypotheses.Prefer using `scripts/capture_memory_profile.sh` for consistency.## Run The ScriptRun a full capture for the latest OrbitDock process:```bashscripts/capture_memory_profile.sh```Run a targeted capture:```bashscripts/capture_memory_profile.sh \ --pid 9718 \ --sample-seconds 5 \ --trace-seconds 10 \ --out-dir /tmp/orbitdock-profile```## Manual CommandsUse these directly when you need finer control:```bashpgrep -lf OrbitDockps -o pid,ppid,rss,vsz,%mem,etime,command -p <PID>vmmap -summary <PID>sample <PID> 5 1xctrace record --template 'Allocations' --attach <PID> --time-limit 10s --output /tmp/orbitdock-alloc.tracexctrace export --input /tmp/orbitdock-alloc.trace --toc```## Permission HandlingIf `vmmap`, `sample`, `leaks`, or `xctrace` fails with permission errors, request elevated execution and rerun the same command.## Interpretation GuideRead `references/interpretation.md` for quick heuristics on:- CoreAnimation and image-backed growth- MALLOC_SMALL and fragmentation signals- Peak vs current footprint interpretation- Stack patterns that implicate rendering, focus rings, or image decode paths## Output ExpectationsThe capture script writes:- `ps.txt`- `vmmap-summary.txt`- `sample.txt`- `allocations.trace` and `xctrace-toc.xml` (if tracing enabled)- `capture-summary.txt`Use these artifacts to compare before/after repro windows and support fixes with evidence.---> Source: [Robdel12/OrbitDock](https://github.com/Robdel12/OrbitDock) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions