agentsclimarketplace

Browser automation

Skill lensetek/Digital-Marketing-Agent_Skills/capabilities/browser-automation

Digital-Marketing-Agent_Skills

Install
npx -y skills add lensetek/Digital-Marketing-Agent_Skills --skill browser-automation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, as published. Nobody here has run it

Browser Automation Capability

When to Use

Use this capability for opening pages, navigating web apps, clicking UI, filling forms, taking screenshots, testing landing pages, checking responsive behavior, and verifying served frontend behavior.

Preferred Implementation

  • Chrome DevTools MCP (chrome-devtools-mcp): Use the chrome-devtools MCP server tools (e.g., chrome-devtools/navigate_page, chrome-devtools/click, chrome-devtools/take_screenshot) as the primary method for browser automation.
    • Responsive Testing: Always use chrome-devtools/emulate or chrome-devtools/resize_page to verify page layouts using a mobile-view first approach.
    • Performance & QA: Use performance tracing or Lighthouse audits to verify loading speed.
    • Credential Safety: Ensure that browser sessions do not cache sensitive credentials (e.g., run the server with --isolated or avoid saving cookies/auth headers in public scopes) to prevent credential leaks.
  • Use programmatic scripts (e.g., Puppeteer, Playwright) or in-app connectors when repeatable, custom QA flows are required.
  • Use OS-level Computer Use only as a last resort if standard API/protocol-based automation fails.

Inputs

  • URL or local file path.
  • Objective.
  • Viewport/device targets.
  • Allowed actions.
  • Credentials policy and login state.
  • Expected evidence: screenshot, notes, or test result.

Outputs

  • Browser QA Report.
  • Screenshots or visual findings.
  • Interaction log.
  • Broken links, console errors, layout issues, or accessibility concerns.
  • Recommendation and next action.

Security and Ethics

  • Do not enter secrets unless the user explicitly approves a secure login flow.
  • Do not expose cookies, tokens, private URLs, or account details in reports.
  • Treat public frontend, browser JavaScript, and public assets as non-secret surfaces.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.