webapp-testing-static-html
Sub-skill of webapp-testing: Static HTML (+2).
Best use case
webapp-testing-static-html is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of webapp-testing: Static HTML (+2).
Teams using webapp-testing-static-html should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/static-html/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How webapp-testing-static-html Compares
| Feature / Agent | webapp-testing-static-html | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of webapp-testing: Static HTML (+2).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Static HTML (+2) ## Static HTML 1. Read files directly to find selectors 2. Then automate with Playwright ## Dynamic Webapps 1. Check if server runs 2. If not, start with helper script 3. Perform reconnaissance (screenshots/DOM) 4. Then automate ## Running Servers 1. Perform reconnaissance first 2. Take screenshots 3. Inspect DOM 4. Then automate
Related Skills
static-site-build-artifact-plan-review
Plan-review pattern for static-site fixes where the deployed artifact is generated from source files (e.g. sitemap/robots/static assets). Prevents review churn by separating durable regression checks from one-time migration verification and by validating built output, not just source files.
static-site-brand-identity-migration-tdd
Execute approved static-site brand identity/logo migrations with TDD across canonical content sources, generated deploy output, legacy checked-in HTML, existing stale tests, and build/docs contracts.
orcaflex-static-debug
Troubleshoot and resolve OrcaFlex static analysis convergence issues. Diagnose common problems including line connectivity, tensions, environmental conditions, and numerical instabilities.
webapp-testing
Web application testing toolkit using Playwright with Python. Use for verifying frontend functionality, debugging UI behavior, capturing browser screenshots, viewing browser logs, and automating web interactions.
testing-tdd-london
TDD London School (mockist) specialist for mock-driven, outside-in development. Use for behavior verification testing, contract-driven development, testing object collaborations, or when focusing on HOW objects interact rather than WHAT they contain.
testing-production
Production validation specialist ensuring applications are fully implemented and deployment-ready. Use to verify no mock/stub/fake implementations remain, validate against real databases and APIs, perform end-to-end testing with actual systems, and confirm production readiness.
github-actions-2-matrix-builds-for-cross-platform-testing
Sub-skill of github-actions: 2. Matrix Builds for Cross-Platform Testing.
orcawave-aqwa-benchmark-single-page-html-report-structure
Sub-skill of orcawave-aqwa-benchmark: Single-Page HTML Report Structure (+3).
orcawave-aqwa-benchmark-html-report-structure
Sub-skill of orcawave-aqwa-benchmark: HTML Report Structure (+1).
orcaflex-static-debug-quick-checks
Sub-skill of orcaflex-static-debug: Quick Checks (+3).
orcaflex-static-debug-minimal-reproducible-model
Sub-skill of orcaflex-static-debug: Minimal Reproducible Model (+1).
orcaflex-static-debug-incremental-static-testing
Sub-skill of orcaflex-static-debug: Incremental Static Testing (+1).