Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
Excellent actionability — every example is runnable as written and the core withBrowser pattern handles credentials, snapshot branching, and cleanup correctly. The main costs are the verbatim duplication of the Chromium dependency list and install steps, and the absence of any validation or error-recovery checkpoints around command output parsing.
Suggestions
Define CHROMIUM_SYSTEM_DEPS and the install sequence once (e.g. a small scripts/install-chromium.sh or a shared code block) and reference it from both the Core Pattern and the snapshot-creation sections.
Add a brief error-handling note for JSON.parse of agent-browser --json output (check the exit code / stderr before parsing) to close the workflow-validation gap.
Clarify in the fillAndSubmitForm example how element refs are obtained from the a11y snapshot, since "// Parse snapshot to find element refs..." is the one non-executable placeholder.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Code-heavy and lean with almost no concept padding — the Docker-image analogy is one sentence and earns its place. The 24-package CHROMIUM_SYSTEM_DEPS list and the dnf/npm install sequence are duplicated verbatim between "Core Pattern" and "Creating a sandbox snapshot", which is pure token cost. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready TypeScript throughout: withBrowser with credential resolution and snapshot branching, screenshot/a11y-snapshot/form-fill/cron examples, snapshot creation, an env-var table, and a framework table covering the common cases. No key details are missing — even cleanup (finally { sandbox.stop() }) and base64 readback are shown. | 5 / 5 |
Workflow Clarity | Sequences are explicit and ordered (create → install deps → run → guaranteed stop via finally) with fail-fast && chaining in the install command. Missing explicit validation: JSON.parse of command stdout has no error handling, and there is no verification that the Chromium install succeeded or recovery guidance when a runCommand fails mid-workflow. | 4 / 5 |
Progressive Disclosure | A self-contained skill (no bundle files exist) with clear section headers, an env-var table, and one clearly signaled external pointer (examples/environments/ in the agent-browser repo). At ~275 lines with a duplicated dependency list, the snapshot-creation section is a candidate for a separate file, keeping it below the clear-overview-with-split-content anchor. | 4 / 5 |
Total | 17 / 20 Passed |