Playwright Go Automation Expert

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/go-playwright

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Playwright Go Automation Expert

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Safety & Risk, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Use when the user asks to "scrape," "automate," or "test" a website using Go.
• Use when the target site has complex dynamic content (SPA, React, Vue) requiring a real browser.
• Use when the user mentions "stealth," "avoiding detection," "cloudflare," or "human-like" behavior.
• Use when debugging existing Playwright scripts.
• Use when the request clearly matches the imported source intent: Expert capability for robust, stealthy, and efficient browser automation using Playwright Go.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.

Operating Table

metadata.json

ORIGIN.md

resources/implementation-playbook.md

resources/implementation-playbook.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Overview

This skill provides a comprehensive framework for writing high-performance, production-grade browser automation scripts using

github.com/playwright-community/playwright-go

Imported: Safety & Risk

Risk Level: 🔵 Safe

• Sandboxed Execution: Browser contexts are isolated; they do not persist data to the host machine unless explicitly saved.
• Resource Management: Designed to close browsers and contexts via

  defer

  to prevent memory leaks.
• No External State-Change: Default behavior is read-only (scraping/testing) unless the script is explicitly designed to submit forms or modify data.

Examples

Example 1: Ask for the upstream workflow directly

Use @go-playwright to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @go-playwright against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @go-playwright for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @go-playwright using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Pattern: Launch the Browser once (singleton). Create a new BrowserContext for each distinct session or task.
• Why: Contexts are lightweight and created in milliseconds. Browsers take seconds to launch.
• Isolation: Contexts provide complete isolation (cookies, cache, storage) without the overhead of a new process.
• Library: Use go.uber.org/zap exclusively.
• Rule: Do not use fmt.Println.
• Modes:
• Dev: zap.NewDevelopment() (Console friendly)

Imported Operating Notes

Imported: Strategic Implementation Guidelines

1. Architecture: Contexts vs. Browsers

CRITICAL: Never launch a new

Browser

• Pattern: Launch the

  Browser

  once (singleton). Create a new

  BrowserContext

  for each distinct session or task.
• Why: Contexts are lightweight and created in milliseconds. Browsers take seconds to launch.
• Isolation: Contexts provide complete isolation (cookies, cache, storage) without the overhead of a new process.

2. Logging & Observability

• Library: Use

  go.uber.org/zap

  exclusively.
• Rule: Do not use

  fmt.Println

  .
• Modes:
  • Dev:

    zap.NewDevelopment()

    (Console friendly)
  • Prod:

    zap.NewProduction()

    (JSON structured)
• Traceability: Log every navigation, click, and input with context fields (e.g.,

  logger.Info("clicking button", zap.String("selector", sel))

  ).

3. Error Handling & Stability

• Graceful Shutdown: Always use

  defer

  to close Pages, Contexts, and Browsers.
• Panic Recovery: Wrap critical automation routines in a safe runner that recovers panics and logs the stack trace.
• Timeouts: Never rely on default timeouts. Set explicit timeouts (e.g.,

  playwright.PageClickOptions{Timeout: playwright.Float(5000)}

  ).

4. Stealth & Human-Like Behavior

To bypass anti-bot systems (Cloudflare, Akamai), the generated code must imitate human physiology:

• Non-Linear Mouse Movement: Never teleport the mouse. Implement a helper that moves the mouse along a Bezier curve with random jitter.
• Input Latency: never use

  Fill()

  . Use

  Type()

  with random delays between keystrokes (50ms–200ms).
• Viewport Randomization: Randomize the viewport size slightly (e.g., 1920x1080 ± 15px) to avoid fingerprinting.
• Behavioral Noise: Randomly scroll, focus/unfocus the window, or hover over irrelevant elements ("idling") during long waits.
• User-Agent: Rotate User-Agents for every new Context.

5. Documentation Usage

• Primary Source: Rely on your internal knowledge of the API first to save tokens.
• Fallback: Refer to the official docs playwright-go documentation ONLY if:
  • You encounter an unknown error.
  • You need to implement complex network interception or authentication flows.
  • The API has changed significantly.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/go-playwright

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @github-issue-creator

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @github-workflow-automation

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @gitlab-automation

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @gitlab-ci-patterns

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

• implementation-playbook.md

Imported Reference Notes

Imported: Resources

• resources/implementation-playbook.md

  for detailed code examples and implementation patterns.

Summary Checklist for Agent

• Is Debug Mode on? ->

  Headless=false

  ,

  SlowMo=100+

  .
• Is it a new user identity? ->

  NewContext

  , apply new Proxy, rotate

  User-Agent

  .
• Is the action critical? -> Wrap in

  SafeAction

  with Zap logging.
• Is the target guarded (Cloudflare/Akamai)? -> Enable

  HumanType

  ,

  BezierMouse

  , and Stealth Scripts.

Imported: Limitations

• Environment Dependencies: Requires Playwright drivers and browsers to be installed (

  go run github.com/playwright-community/playwright-go/cmd/playwright@latest install --with-deps

  ).
• Resource Intensity: Launching full browser instances (even headless) consumes significant RAM/CPU. Use single-browser/multi-context architecture.
• Bot Detection: While this skill includes stealth techniques, extremely strict anti-bot systems (e.g., rigorous Cloudflare settings) may still detect automation.
• CAPTCHAs: Does not include built-in CAPTCHA solving capabilities.