Skip to content
TrustedSkillsbeta
Back to all skills

Webapp Testing

Checked
project-n-e-k-o·vlatest·testing·Apache-2.0

Automates comprehensive web application testing for project-n-e-k-o, identifying bugs and ensuring functionality across browsers.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add project-n-e-k-o/n.e.k.o --skill webapp-testing -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

project-n-e-k-o

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned project-n-e-k-o/n.e.k.o at 4e45b30d1c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
4e45b30d1c
Manifest
.agent/skills/webapp-testing/SKILL.md
Scanned
6 files, 300 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

webapp-testing

What it does

This skill enables AI agents to perform automated testing on web applications. It allows agents to interact with browsers, execute test scripts, and validate application behavior against defined criteria to ensure functionality and reliability.

When to use it

  • Regression Testing: Automatically re-run test suites after code deployments to catch unintended side effects.
  • Accessibility Audits: Simulate user interactions to verify compliance with accessibility standards like WCAG.
  • E2E Validation: Execute end-to-end workflows across multiple pages to confirm the complete user journey functions correctly.
  • Performance Checks: Run load tests or simulate concurrent users to identify bottlenecks in web application responsiveness.

Key capabilities

  • Browser automation and control for executing test scenarios.
  • Script execution support for various testing frameworks.
  • Result reporting and validation of application states.

Example prompts

  • "Run the full regression suite on the checkout flow and report any failures."
  • "Simulate a user logging in, searching for products, and adding an item to the cart."
  • "Check if the website meets WCAG 2.1 AA standards by testing keyboard navigation."

Tips & gotchas

Ensure the target web application is accessible via a stable URL before initiating tests. Limit concurrent test runs to avoid overloading the application server during critical operations.