Skip to content

domain-skills: add Dynadot DNS editing skill#440

Open
idigitalpro1 wants to merge 1 commit into
browser-use:mainfrom
idigitalpro1:contribute/dynadot-dns-skill
Open

domain-skills: add Dynadot DNS editing skill#440
idigitalpro1 wants to merge 1 commit into
browser-use:mainfrom
idigitalpro1:contribute/dynadot-dns-skill

Conversation

@idigitalpro1

@idigitalpro1 idigitalpro1 commented Jun 13, 2026

Copy link
Copy Markdown

Adds a domain skill for editing DNS records on dynadot.com.

Captures the durable shape of the site so the next agent doesn't pay the discovery tax:

  • Auth wall — every DNS/account page is gated; the isolated harness profile only ever sees the public marketing SPA. Don't type credentials from a screenshot.
  • Navigation map — public site is a Vue SPA; the Login control isn't a light-DOM text node; guessed login URLs (/account/sign_in, /login, etc.) all return the 200 SPA 404 shell, not redirects.
  • js() helper gotchas — single-expression only; IIFEs and arrays-of-objects come back as None; empty arrays also surface as None; screenshots are DPR 2 while click_at_xy uses CSS pixels.
  • Record-setting flow — Dynadot DNS vs Custom Nameservers, save, verify.
  • Shell verificationdig/whois (no login needed).
  • Trap log — including the 🟢 tab-title marker and the isolated-profile warning.

No secrets, coordinates, or task narration — just the map.

🤖 Generated with Claude Code


Summary by cubic

Adds a Dynadot DNS editing skill with a durable site map and clear steps to update records. This reduces discovery time and avoids auth and harness pitfalls.

  • New Features
    • Auth/session prerequisites for using a logged-in Chrome; do not type credentials.
    • Notes that no Dynadot API key is provided; prefer the API if a key exists.
    • Navigation map for the Vue SPA: guessed login URLs 404; how to reach DNS via the domain manager.
    • Harness js() quirks: single-expression only; arrays of objects and empty arrays return None; DPR 2 screenshots vs CSS-pixel clicks.
    • Record flow: choose Dynadot DNS vs Custom Nameservers, add/edit rows, save, verify.
    • Shell verification with dig/whois; trap log includes tab-title emoji and isolated-profile warning.

Written for commit 06aaa45. Summary will update on new commits.

Review in cubic

Durable site map for editing DNS records on dynadot.com: auth-wall
prerequisites, the Vue SPA navigation map (guessed login URLs 404),
js() helper gotchas specific to this harness, the record-setting flow,
shell verification with dig/whois, and a trap log.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Re-trigger cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant