Individual skill

debug-failed-action

When your last `vs_act` returned an unexpected result (NOT_FOUND, no visible state change, suspected silent failure), run this skill with the action's pre-token. Pulls console errors, network failures, and current performance into one report.

skills/debug-failed-action/SKILL.md

Read pinned source

Source commit 4851123193006a26cda3836fcad5a9bf96fb9c9c

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
17
Repository last updated
Sep 24, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# debug-failed-action

## When to use

You ran `vs_act` and one of:

- The next `vs_view` looks identical to the previous one (no DOM change).
- You got `! NOT_FOUND ref=N` even though the ref was in the most recent tree.
- A button you clicked appears `disabled` / `aria-busy` / `pointer-events: none` in the DOM but not in the semantic tree.
- A form submission completed in the UI but the underlying API call returned 4xx/5xx silently.

## What it does

Runs three on-demand inspections in sequence against the page that owns the failed action: