openskills-runtime-debug
Scannednpx machina-cli add skill Geeksfino/openskills/openskills-runtime-debug --openclawOpenSkills Runtime Debug
Use this skill when debugging runtime failures in runtime/ and execution paths used by run_skill_target, native scripts, or sandbox enforcement.
Primary Targets
runtime/src/executor.rsruntime/src/native_runner.rsruntime/src/wasm_runner.rsruntime/src/permissions.rsruntime/tests/*sandbox*runtime/tests/seatbelt_tests.rs
Workflow
- Reproduce with the smallest command that fails.
- Classify failure bucket:
- sandbox policy issue
- feature/config mismatch
- script/tool resolution issue
- wasm runtime issue
- Confirm behavior against tests and existing fallback logic.
- Propose the smallest safe fix that preserves security boundaries.
- Re-run focused tests, then broader runtime tests.
Recommended Commands
cargo check -p openskills-runtime
cargo test -p openskills-runtime
cargo test -p openskills-runtime seatbelt_tests -- --nocapture
Debug Heuristics
- Treat silent degradation in sandbox setup as high risk.
- Prefer explicit error propagation over ignored
Result. - If fallback behavior is intentional, confirm it is visible in logs and tests.
- Keep macOS and Linux behavior differences explicit in findings.
Output Format
Return:
- Root cause
- Impact surface
- Fix proposal
- Verification evidence
- Residual risks
Source
git clone https://github.com/Geeksfino/openskills/blob/main/.cursor/skills/openskills-runtime-debug/SKILL.mdView on GitHub Overview
OpenSkills Runtime Debug helps diagnose failures in the runtime/execution paths used by run_skill_target, native scripts, or sandbox enforcement. It guides you to identify root causes (sandbox policy, config mismatch, tool resolution, or wasm issues) and propose the smallest safe remediation while preserving security.
How This Skill Works
Follow the workflow: reproduce with the smallest failing command, classify the failure into a bucket (sandbox policy, feature/config mismatch, script/tool resolution issue, wasm runtime issue), and confirm behavior against tests and existing fallbacks. Then propose the smallest safe fix and re-run focused and broader runtime tests.
When to Use It
- Debugging a failed run_skill_target due to sandbox policy denial (Landlock, seatbelt, or wasm sandbox).
- Encountering a feature/config mismatch that causes a runtime path to fail.
- Script/tool resolution issues where a required script or binary cannot be located or loaded.
- WASM runtime issues during execution in wasm_runner.rs.
- Silent degradation or divergent sandbox setup where logs/tests should surface the risk.
Quick Start
- Step 1: Reproduce with the smallest command that fails.
- Step 2: Classify the failure bucket and collect tests/logs that prove the behavior.
- Step 3: Propose the smallest safe fix, then re-run focused tests followed by broader runtime tests.
Best Practices
- Start with the smallest reproducible command that fails.
- Classify the failure first into a bucket (sandbox policy, config fault, resolution issue, wasm problem).
- Prefer explicit error propagation over ignored Result values.
- If a fallback is intentional, verify it is visible in logs and tests.
- Document macOS vs Linux behavior differences in findings.
Example Use Cases
- Sandbox policy issue blocks run_skill_target execution due to a Landlock denial.
- Feature/config mismatch between the runtime and test harness leads to incorrect permission decisions.
- Native script resolution fails because the required tool path is missing or misconfigured.
- WASM runner encounters a runtime error when loading or executing a module.
- Degraded sandbox setup with no clear error in logs; behavior diverges from tests.
