chore(agent-browser): re-sync the vendored stub with the 0.33.2 CLI #43

Merged
jercik merged 1 commit from align/agent-browser into main 2026-08-07 07:01:17 +00:00
Owner

The central copy drifted from the discovery stub the CLI ships: it was hand-rewrapped at import, and agent-browser 0.33.2 now serves a derive-client skill (record a HAR, derive a standalone API client) the enumeration omits. This replaces the file with a byte-for-byte copy of the shipped stub, so future refreshes are plain diff-checkable copies instead of merges.

The central copy drifted from the discovery stub the CLI ships: it was hand-rewrapped at import, and agent-browser 0.33.2 now serves a `derive-client` skill (record a HAR, derive a standalone API client) the enumeration omits. This replaces the file with a byte-for-byte copy of the shipped stub, so future refreshes are plain diff-checkable copies instead of merges.
chore(agent-browser): re-sync the vendored stub with the 0.33.2 CLI
Some checks failed
Node tests / node:test (pull_request) Successful in 15s
commit-msg / commitlint (pull_request) Successful in 21s
PR Review / Prepare immutable review tools (pull_request_target) Successful in 1m35s
PR Review / forgejo-review-code-smart-2 generator (pull_request_target) Failing after 48s
PR Review / forgejo-review-approach-3 generator (pull_request_target) Failing after 49s
PR Review / forgejo-review-approach-smart-2 generator (pull_request_target) Failing after 50s
PR Review / forgejo-review-approach-smart-1 generator (pull_request_target) Successful in 2m17s
PR Review / forgejo-review-code-smart-1 generator (pull_request_target) Successful in 2m29s
PR Review / Dispatch and observe exact review writers (pull_request_target) Failing after 3m40s
14a5967c2d
forgejo-actions left a comment

Approach review: The approach looks good.

Approach review by Codex GPT-5.6 SOL (gpt-5.6-sol)

**Approach review:** The approach looks good. _Approach review by Codex GPT-5.6 SOL (gpt-5.6-sol)_ <!-- axrecipe-review:v1:eyJzY2hlbWFWZXJzaW9uIjoxLCJzdGF0ZSI6InB1Ymxpc2hlZCIsInJlcG9zaXRvcnkiOiJqNGstb3NzL2FnZW50LXNraWxscyIsIm51bWJlciI6IjQzIiwiaGVhZFNoYSI6IjE0YTU5NjdjMmQ2MmY0YmExMTY1Y2Y5ZjZiNGI5YmI0OTlmYWM2YjciLCJzbG90IjoiZm9yZ2Vqby1yZXZpZXctYXBwcm9hY2gtc21hcnQtMSIsInNvdXJjZVdvcmtmbG93UnVuSWQiOiIxNzcyMyIsInNvdXJjZUdlbmVyYXRvckF0dGVtcHQiOiIxIiwicmVzdWx0SWQiOiI2ZjE4MDI3Ni0xZTg3LTRlMTMtOWZhMi1lNGJmNzQyNjJkZmYifQ== -->
forgejo-actions left a comment

Summary: No actionable issues found; 1 informational note.

The PR's central claim checks out. I downloaded agent-browser@0.33.2 from npm and compared package/skills/agent-browser/SKILL.md against the vendored skills/agent-browser/SKILL.md with cmp: byte-identical. The rewrapping to single-line paragraphs and the added derive-client line are both exactly what upstream ships, so future refreshes really do become plain diff-checkable copies.

Spot checks:

  • derive-client is a real skill in the 0.33.2 tarball (package/skill-data/derive-client/SKILL.md), and the one-line gloss in the enumeration matches its purpose.
  • The enumeration now covers every specialized skill the package ships (agentcore, derive-client, dogfood, electron, slack, vercel-sandbox); only core is omitted, which the "Start here" section already handles.
  • No markdown formatter is wired into CI (.forgejo/workflows/node-test.yml runs node:test only) and .githooks/pre-commit only runs git diff --cached --check, so nothing will re-wrap the file and silently break byte parity.

Code review by Claude Code Opus (opus)

**Summary:** No actionable issues found; 1 informational note. The PR's central claim checks out. I downloaded `agent-browser@0.33.2` from npm and compared `package/skills/agent-browser/SKILL.md` against the vendored `skills/agent-browser/SKILL.md` with `cmp`: byte-identical. The rewrapping to single-line paragraphs and the added `derive-client` line are both exactly what upstream ships, so future refreshes really do become plain diff-checkable copies. Spot checks: - `derive-client` is a real skill in the 0.33.2 tarball (`package/skill-data/derive-client/SKILL.md`), and the one-line gloss in the enumeration matches its purpose. - The enumeration now covers every specialized skill the package ships (`agentcore`, `derive-client`, `dogfood`, `electron`, `slack`, `vercel-sandbox`); only `core` is omitted, which the "Start here" section already handles. - No markdown formatter is wired into CI (`.forgejo/workflows/node-test.yml` runs `node:test` only) and `.githooks/pre-commit` only runs `git diff --cached --check`, so nothing will re-wrap the file and silently break byte parity. _Code review by Claude Code Opus (opus)_ <!-- axrecipe-review:v1:eyJzY2hlbWFWZXJzaW9uIjoxLCJzdGF0ZSI6InB1Ymxpc2hlZCIsInJlcG9zaXRvcnkiOiJqNGstb3NzL2FnZW50LXNraWxscyIsIm51bWJlciI6IjQzIiwiaGVhZFNoYSI6IjE0YTU5NjdjMmQ2MmY0YmExMTY1Y2Y5ZjZiNGI5YmI0OTlmYWM2YjciLCJzbG90IjoiZm9yZ2Vqby1yZXZpZXctY29kZS1zbWFydC0xIiwic291cmNlV29ya2Zsb3dSdW5JZCI6IjE3NzIzIiwic291cmNlR2VuZXJhdG9yQXR0ZW1wdCI6IjEiLCJyZXN1bHRJZCI6IjJkYTcxN2Q1LTNhNTUtNDg4MS05ZWYzLTM5YzE0YTRjOTgwMyJ9 -->
@ -34,12 +30,12 @@ Load a specialized skill when the task falls outside browser web pages:
agent-browser skills get electron # Electron desktop apps (VS Code, Slack, Discord, Figma, ...)
agent-browser skills get slack # Slack workspace automation
agent-browser skills get dogfood # Exploratory testing / QA / bug hunts
agent-browser skills get derive-client # Record a HAR, derive a standalone API client for a site

ℹ️ Info: The body now advertises derive-client, but the frontmatter description — which is what the axskills picker shows and what drives skill triggering — still enumerates only Electron, Slack, dogfood/QA, Vercel Sandbox, and AgentCore. An agent that never loads the body won't associate "reverse engineer this site's API" or "record a HAR" with this skill.

No action needed here: editing the description would break the byte-for-byte parity with the shipped stub that this PR exists to establish, and the gap is upstream's to close. Flagging only so it's a known tradeoff rather than a surprise.

ℹ️ **Info:** The body now advertises `derive-client`, but the frontmatter `description` — which is what the axskills picker shows and what drives skill triggering — still enumerates only Electron, Slack, dogfood/QA, Vercel Sandbox, and AgentCore. An agent that never loads the body won't associate "reverse engineer this site's API" or "record a HAR" with this skill. No action needed here: editing the description would break the byte-for-byte parity with the shipped stub that this PR exists to establish, and the gap is upstream's to close. Flagging only so it's a known tradeoff rather than a surprise.
jercik marked this conversation as resolved
@ -34,12 +30,12 @@ Load a specialized skill when the task falls outside browser web pages:
agent-browser skills get electron # Electron desktop apps (VS Code, Slack, Discord, Figma, ...)
agent-browser skills get slack # Slack workspace automation
agent-browser skills get dogfood # Exploratory testing / QA / bug hunts
agent-browser skills get derive-client # Record a HAR, derive a standalone API client for a site
Author
Owner

Acknowledged, no change — and agreed on both halves.

The observation is correct: the frontmatter description names the Electron, Slack, dogfood/QA, Vercel Sandbox, and AgentCore use cases but nothing HAR- or API-derivation-shaped, so a picker that never loads the body won't route "record a HAR" here on the new line alone.

Deliberately leaving it: parity with the shipped stub is whole-file (your cmp against the agent-browser@0.33.2 tarball covered the frontmatter too), so editing the description locally would reintroduce exactly the drift class this PR exists to remove. The right home for the trigger phrase is upstream's own description; if they add it, the next refresh picks it up as a plain diff. Meanwhile the description's broad clauses ("extracting data", "any task requiring programmatic web interaction") still catch most derive-client-adjacent asks, so the gap is narrow.

Acknowledged, no change — and agreed on both halves. The observation is correct: the frontmatter `description` names the Electron, Slack, dogfood/QA, Vercel Sandbox, and AgentCore use cases but nothing HAR- or API-derivation-shaped, so a picker that never loads the body won't route "record a HAR" here on the new line alone. Deliberately leaving it: parity with the shipped stub is whole-file (your `cmp` against the `agent-browser@0.33.2` tarball covered the frontmatter too), so editing the description locally would reintroduce exactly the drift class this PR exists to remove. The right home for the trigger phrase is upstream's own `description`; if they add it, the next refresh picks it up as a plain diff. Meanwhile the description's broad clauses ("extracting data", "any task requiring programmatic web interaction") still catch most derive-client-adjacent asks, so the gap is narrow.
jercik marked this conversation as resolved
jercik merged commit c82e8ca3c8 into main 2026-08-07 07:01:17 +00:00
jercik deleted branch align/agent-browser 2026-08-07 07:01:17 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
j4k-oss/agent-skills!43
No description provided.