OpenParable
Skip to content
← Back to skills

Error

Testing & Quality
error

Error is an Agent Skill for testing & quality published in the crbnos/carbon repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Capture a screenshot plus element snapshot of the current browser page when an error appears during e2e testing, saved to gitignored .ai/scratch/e2e/. Use whenever an agent-browser snapshot shows "Something went wrong", an auth error, a blank page, or an unexpected redirect. Building block — it captures and returns; the caller decides whether to continue.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/crbnos/carbon/blob/HEAD/.ai/skills/error/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/error, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

error — capture browser failure diagnostics

Capture artifacts when the browser shows a failure, then hand control back to the calling skill. Never stops the calling run by itself.

When to invoke

Any agent-browser snapshot that reveals:

  • a "Something went wrong" heading
  • "Authentication Error" or similar
  • a blank page or unexpected redirect
  • any content indicating the page failed to render

Steps

1. Resolve the slug

Use CARBON_WORKTREE from .env.local if present; otherwise the current branch name:

SLUG=$(grep '^CARBON_WORKTREE' .env.local | cut -d= -f2)
[ -z "$SLUG" ] && SLUG=$(git branch --show-current | tr '/' '-')

2. Capture both artifacts

Save to .ai/scratch/e2e/ — it is gitignored (.ai/scratch/ in .gitignore). Never save captures under docs/ (that's the documentation app, and it is tracked).

mkdir -p .ai/scratch/e2e/${SLUG}
STAMP=$(date +%Y%m%d-%H%M%S)
agent-browser screenshot .ai/scratch/e2e/${SLUG}/${module}-${STAMP}.png
agent-browser snapshot -i > .ai/scratch/e2e/${SLUG}/${module}-${STAMP}.txt

${module} = a short name for the route/feature under test (e.g. accounting). The .txt snapshot lets you debug element structure without reopening a browser.

3. Report and return

Log both file paths and continue — the caller decides whether to abort. Include the paths in the caller's final report so a human can open them.

Output

  • .ai/scratch/e2e/{slug}/{module}-{timestamp}.png — screenshot
  • .ai/scratch/e2e/{slug}/{module}-{timestamp}.txt — element snapshot