agentsclimarketplace
Sign in

Playwright automation fill in form

Skill mouadja02/skills/skills/testing/playwright-automation-fill-in-form

Automate filling in a form using Playwright MCPFrom its SKILL.md

Install
npx -y skills add mouadja02/skills --skill playwright-automation-fill-in-form

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 9 stars9 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

0.6 KB, 134 tokens by cl100k_base, as published. Nobody here has run it

Automating Filling in a Form with Playwright MCP

Your goal is to automate the process of filling in a form using Playwright MCP.

Specific Instructions

Navigate to https://forms.microsoft.com/url-of-my-form

Fill in the form with the following details:

  1. Show: playwright live

  2. Date: 15 July

  3. Time: 1:00 AM

  4. Topic: Playwright Live - Latest updates on Playwright MCP + Live Demo

  5. Upload image: /Users/myuserName/Downloads/my-image.png

DO NOT SUBMIT THE FORM.

Ask for a review of the form before submitting it.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most automation workflows skills give in 134 tokens

Counted across 813 of the 1,214 authors here whose files we hold, read 2026-09-06

  • Use conventional commit message formatin 38 of 813, across 34 files
  • Write tests before implementing codein 26 of 813, across 12 files
  • Achieve at least 80 percent test coveragein 24 of 813, across 11 files
  • Mock external dependencies for unit testsin 22 of 813, across 10 files
  • Read product marketing context before asking questionsin 21 of 813, across 6 files
  • Implement rollback plans for every deploymentin 21 of 813, across 9 files
  • Follow the arrange-act-assert patternin 20 of 813, across 9 files
  • Delete branches after mergingin 20 of 813, across 18 files
  • Test all edge cases and error scenariosin 20 of 813, across 8 files
  • Use semantic selectors for UI testsin 19 of 813, across 7 files
  • Define sequence type and audience contextin 18 of 813, across 5 files
  • Monitor feature drift and prediction distribution driftin 18 of 813, across 5 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. 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.