Tell agents to read error.detail and error.hint on every failure

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: gersham

plugins/screenrig/skills/screenrig/SKILL.md

@@ -405,8 +405,10 @@ compatible explicit choice. Use `--human` only for manual inspection, never
 together with `--json`. Help and bare command groups are readable by default;
 `--json --help` returns structured help. Progress stays on stderr; parse stdout
 separately. `events follow` emits one JSON envelope per line (NDJSON).
-Branch on `ok`, `error.status`, `error.code` and `warnings[].code`,
-not prose. Follow an applicable `error.next.command` without inventing flags,
+Branch on `ok`, `error.status`, `error.code` and `warnings[].code`.
+On any failure, read `error.detail` (what was wrong, specifically) and
+`error.hint` (what to do about it) before deciding the next step, and pass the
+gist to the user when they need to act. Follow an applicable `error.next.command` without inventing flags,
 except do not follow a connect or dashboard next-step on first setup unless the
 user said this installation should join an existing screenRIG project.
 Revision guards are optional for most writes: omit `--expect-rev` to write the

skills/screenrig/SKILL.md

@@ -405,8 +405,10 @@ compatible explicit choice. Use `--human` only for manual inspection, never
 together with `--json`. Help and bare command groups are readable by default;
 `--json --help` returns structured help. Progress stays on stderr; parse stdout
 separately. `events follow` emits one JSON envelope per line (NDJSON).
-Branch on `ok`, `error.status`, `error.code` and `warnings[].code`,
-not prose. Follow an applicable `error.next.command` without inventing flags,
+Branch on `ok`, `error.status`, `error.code` and `warnings[].code`.
+On any failure, read `error.detail` (what was wrong, specifically) and
+`error.hint` (what to do about it) before deciding the next step, and pass the
+gist to the user when they need to act. Follow an applicable `error.next.command` without inventing flags,
 except do not follow a connect or dashboard next-step on first setup unless the
 user said this installation should join an existing screenRIG project.
 Revision guards are optional for most writes: omit `--expect-rev` to write the