# Check Result

> Verify the expected effect of a step actually happened before moving to the next.

- Skill: `jcaiagent7143-ui/check-result` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jcaiagent7143-ui/check-result`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jcaiagent7143-ui/check-result/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: jcaiagent7143-ui (https://skillmd.com/u/jcaiagent7143-ui)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/jcaiagent7143-ui/check-result

---


# Check Result

## Steps

1. Read `step.expected_effect` — what observable thing should be true now?
2. Probe for it independently: re-read the file, GET the API endpoint,
   query the DB. Don't trust the call's return value alone.
3. If observed matches expected → `ok=true` + cite the evidence.
4. If not → `ok=false` with the specific mismatch. Decide: retry this step,
   roll back, or escalate to the user.

## Output shape

```jsonc
{
  "ok": true,
  "evidence": "GET /things/42 returned 200 with name='new-thing'"
}
// or
{
  "ok": false,
  "mismatch": "expected file out.json present; got ENOENT",
  "action": "retry-step"
}
```

## Failure modes

- Trusting the tool's own success signal — many APIs return 200 + body
  saying "queued" while the side effect never lands.
- Re-checking via the same code path that just wrote — use an independent probe.
- Treating "looks ok" as "is ok"; the verdict is binary.