Buscar habilidades.../

Lag Detector | Skills Pool

Archivo del skill

Lag Detector

Performance profiler for Oracle of Secrets. Samples the CPU Program Counter (PC) to identify code hotspots and laggy routines using statistical analysis.

scawful0 estrellas28 ene 2026

Ocupación
Categorías: Análisis de Datos

Contenido de la habilidad

Scope

Profiling: Statistical sampling of CPU execution.
Hotspot Analysis: Identify which routines consume the most cycles.
Source Mapping: Map hotspots back to ASM files.

Core Capabilities

1. Profile execution

run --duration 10: Sample CPU for 10 seconds.
Output: A heatmap of the most executed routines.

2. Identify Bottlenecks

"Routine Update_Sprites executed 5000 times (40% of samples)."
Helps pinpoint inefficient loops or heavy logic.

Workflow

Setup: Navigate to a laggy area (e.g., room with many enemies).
Profile: .

Skills relacionados

Instalación rápida

Lag Detector

npx skills add scawful/afs_scawful

Descargar Skill Abrir repositorio

Autor: scawful
estrellas: 0
Actualizado: 28 ene 2026
Ocupación

En esta página

lag-detector run --duration 5

Analyze: "Top hotspot is Sprite_Draw in Sprites.asm."

Dependencies

Tool: ~/src/hobby/yaze/scripts/ai/profiler.py.
Mesen2: Running with socket server.
z3ed: For symbol resolution.

Example Prompts

"Profile the game for 10 seconds to find lag sources."
"What routine is taking up the most CPU time right now?"

Troubleshooting

No Hotspots: Ensure the game is not paused.
Unknown Symbols: Ensure the ROM has a valid .mlb or sourcemap.json.

02

Core Capabilities

031. Profile execution

042. Identify Bottlenecks

07Example Prompts

08Troubleshooting

Analistas y testers de aseguramiento de calidad de software

Openclaw Secret Scanning Maintainer

Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.

Session Logs

Search and analyze your own session logs (older/parent conversations) using jq.

Node Connect

Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

Openclaw Qa Testing

Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.

OpenClaw Test Heap Leaks

Investigate `pnpm test` memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw using the `scripts/test-parallel.mjs` heap snapshot tooling. Use when Codex needs to reproduce test-lane memory growth, collect repeated `.heapsnapshot` files, compare snapshots from the same worker PID, triage likely transformed-module retention versus likely runtime leaks, and fix or reduce the impact by patching cleanup logic or isolating hotspot tests.

Flags

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

Analistas y testers de aseguramiento de calidad de software