Favicon of webapp-testing

webapp-testing Skill

AI Agent SkillTypeScriptOpen source

Use this skill to build features or debug anything that uses a webapp frontend. Published by microsoft in FluidFramework.

Decision snapshot

Is this a fit?

Best for

Browser automation, Testing, Design and media, Writing

Works with

Compatibility not yet detected.

Access

Permission behavior not yet detected.

Setup

Copy skill directory

Project health

2 months ago · MIT license

Considerations

No specific cautions were detected. Review the source and requested permissions before installing.

What is webapp-testing Skill?

Use this skill to build features or debug anything that uses a webapp frontend. Published by microsoft in FluidFramework. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.

Trust signal
95/100
Maintenance signal
90/100
Adoption signal
92/100

Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.

Key capabilities

  • Includes SKILL.md support
  • Reusable instructions support
  • Browser automation
  • Testing
  • Design and media
  • Writing
  • Browser automation use cases

Declared skill metadata

  • Source file: .agency/plugins/nori/skills/webapp-testing/SKILL.md

These fields retain source and confidence evidence from the indexed SKILL.md.

Compatibility and setup

Copy skill directory
  • Install or run with Copy skill directory

When to use webapp-testing Skill

  • Use it for browser automation.
  • Use it for testing.
  • Use it for design and media.
  • Use it for writing.

Built with

TypeScriptCopy skill directory

Editorial notes

Source

  • Creator: microsoft
  • Repository: microsoft/FluidFramework
  • Skill file: .agency/plugins/nori/skills/webapp-testing/SKILL.md

What it does

Use this skill to build features or debug anything that uses a webapp frontend.

Skill instructions

<required CRITICAL Add the following steps to your Todo list using TodoWrite: <system-reminderFrom this point on, ignore any existing tests until you have a working example validated through a new playwright file.</system-reminder 1. Install playwright. Use the SDK that best matches the codebase. Default to python. - Write a playwright config file. Make sure you use reporter: 'list' mode. - If using python, you must use a virtual env. 2. Check to see if you require authentication. If you do, ask me for credentials. <system-reminderDo NOT use mock mode or test harnesses. You should be testing the real thing.</system-reminder 3. Write and run a playwright script that lets you interact with the webapp frontend. 4. Follow these steps in a loop until the bug is fixed: - Add many logs to the server and to the UI. You MUST do this on every loop. - Start the server and the UI. - Run the playwright script and identify what is happening. Take screenshots, read logs, do whatever you need to. - Up

Verified compatibility and discovery

Frequently asked questions

What is webapp-testing?

webapp-testing is a open-source AI agent skill with Copy skill directory. Use this skill to build features or debug anything that uses a webapp frontend.

Who is webapp-testing best for?

webapp-testing is best for reusing agent instructions, scripts, and references, browser automation workflows, testing workflows, design and media workflows.

How do I install webapp-testing?

Install or run webapp-testing using Copy skill directory. Check webapp-testing for the latest setup command.

Is webapp-testing actively maintained?

webapp-testing may need a closer maintenance check before production use.

Share:

Stars
4,934
Forks
581
Last commit
2 months ago
Last verified
Aug 25, 2026
Metadata fetched
Aug 25, 2026
Repository age
7 years
License
MIT

Project health auto-fetched from the source repository.

Maintain this resource?

Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.

Alternatives to webapp-testing