sentinel

Detect Mesen2 crashes and softlocks and trigger crash-dump investigations.

Updated Dec 30, 2025
One-click install
npx skills add https://github.com/scawful/afs_scawful --skill sentinel-scawful
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentinel
Source: https://github.com/scawful/afs_scawful/tree/main/skills/sentinel
Command: npx skills add https://github.com/scawful/afs_scawful --skill sentinel-scawful

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Background watchdog that automatically detects emulator crashes and softlocks in Mesen2 and triggers a crash-dump investigation to preserve state for debugging.

Core Features & Use Cases

  • Continuous monitoring alongside games and automated tests to catch pauses and input stagnation.
  • Detection logic for crashes (emulator paused), softlocks (stuck in transition or input stagnation), and triggering crash_dump processes.
  • Use Case: during long pathfinding or game-testing sessions, ensure crash data is captured without manual intervention.

Quick Start

Launch sentinel to begin monitoring Mesen2 for crashes and softlocks and automatically invoke crash-investigator on detection.

Frequently Asked Questions about sentinel

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

FAQPage Schema
How do I detect emulator crashes and softlocks automatically in Mesen2?

You can detect Mesen2 crashes and softlocks automatically by running a background watchdog that monitors for emulator paused states, input stagnation, and stuck transitions during gameplay or testing sessions.

What is a softlock and how does watchdog monitoring catch it during game testing?

A softlock occurs when a game gets stuck in a transition or experiences input stagnation. Watchdog monitoring catches it by actively tracking game and submode conditions to identify when normal progress halts unexpectedly.

Can I capture crash dumps in Mesen2 without manual intervention during long play sessions?

Yes, continuous monitoring alongside long pathfinding or game-testing sessions captures crash data without manual intervention by automatically triggering crash-dump investigations when a crash or softlock is detected.

How do I trigger a crash-dump investigation when an emulator pauses or freezes?

Triggering a crash-dump investigation when an emulator pauses involves using detection logic that identifies the paused state and automatically invokes an integrated crash-investigator process to generate and store reports.

Does background crash detection work with automated tests in Mesen2?

Yes, background crash detection applies during automated tests in Mesen2, continuously monitoring for input stagnation and emulator pauses to ensure any crash data is captured throughout the automated testing process.