validate-app

Validate Resident Lua apps locally with permissive stubs and exit codes.

91|4|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/inanimate-tech/resident --skill validate-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-app
Source: https://github.com/inanimate-tech/resident/tree/main/tools/agent-plugin/skills/validate-app
Command: npx skills add https://github.com/inanimate-tech/resident --skill validate-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates Resident Lua apps on your workstation before deployment, catching syntax errors, missing lifecycle functions, and runtime issues to reduce device failures.

Core Features & Use Cases

  • Local Lua interpretation with auto-deduced stubs to simulate device APIs.
  • Checks for compile errors, missing lifecycle functions, and runtime errors during a short simulated run.
  • Triggered by /resident:validate-app or user request; ideal for pre-flash validation before pushing to a device.

Quick Start

Run the tool against your Lua app file to validate it locally.

Frequently Asked Questions about validate-app

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

FAQPage Schema
How do I validate Resident Lua apps locally before pushing to a device?

Local validation of Resident Lua apps runs your code through a Lua interpreter with permissive stubs to simulate device APIs. It checks for compile errors, missing lifecycle functions, and runtime issues before deployment.

What is the best way to catch syntax and runtime errors in Lua apps before flashing?

The best way to catch syntax and runtime errors in Lua apps before flashing is to run a local validation tool. It simulates a short device run to identify missing lifecycle functions and runtime crashes safely on your workstation.

How does local Lua validation deduce device modules for sandbox stubs?

Local Lua validation deduces device modules for sandbox stubs by reading the DEVICE-SKILL.md file alongside optional refs. This allows the interpreter to accurately simulate the specific device APIs your app requires.

Do I need a physical device to test for missing lifecycle functions in my Lua code?

You do not need a physical device to test for missing lifecycle functions in Lua code. Local validation tools use auto-deduced stubs to simulate the device environment and verify your code directly on your workstation.

Why does my Lua app pass local validation but still fail on the device?

Your Lua app might pass local validation but fail on the device because validation uses permissive stubs. These stubs simulate device APIs but may not perfectly replicate actual hardware behavior and edge cases.