webapp-testing

Web application testing principles. E2E, Playwright, deep audit strategies.

Quality

41%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/webapp-testing/SKILL.md

Quality

Discovery

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies the testing domain and key technology (Playwright) but reads as a topic list rather than a functional skill description. It lacks concrete actions, explicit trigger conditions, and natural language variations that would help Claude reliably select this skill when appropriate.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when writing Playwright tests, debugging E2E failures, or setting up browser automation'

List specific concrete actions such as 'Write Playwright test scripts, debug test failures, configure test fixtures, generate coverage reports'

Include natural keyword variations users would say: 'end-to-end tests', 'browser tests', 'test automation', '.spec.ts', 'page objects'

Dimension	Reasoning	Score
Specificity	Names the domain (web application testing) and mentions specific technologies (E2E, Playwright) and concepts (deep audit strategies), but doesn't list concrete actions like 'write tests', 'debug failures', or 'generate test reports'.	2 / 3
Completeness	Only addresses 'what' at a high level with no 'Use when...' clause or explicit trigger guidance. The description is a fragment listing topics rather than explaining when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes some relevant keywords users might say ('E2E', 'Playwright', 'testing'), but missing common variations like 'end-to-end', 'browser testing', 'test automation', 'integration tests', or file extensions like '.spec.ts'.	2 / 3
Distinctiveness Conflict Risk	'Playwright' provides some distinctiveness, but 'web application testing' and 'E2E' are broad enough to potentially overlap with other testing-related skills or general web development skills.	2 / 3
	Total	7 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a reasonable overview of web testing principles with good structural organization using tables. However, it leans toward explaining general testing concepts Claude already knows rather than providing project-specific, executable guidance. The runtime scripts section is the strongest part, but the rest lacks concrete code examples and validation workflows.

Suggestions

Add executable Playwright test code examples (actual spec files) instead of just conceptual tables describing what to test

Include a concrete Page Object Model implementation example that can be copy-pasted and adapted

Add validation checkpoints to the systematic testing workflow (e.g., 'verify coverage report shows >80% before proceeding')

Remove or condense sections explaining concepts Claude knows (testing pyramid, general anti-patterns) and focus on project-specific configurations and patterns

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient with good use of tables, but includes some concepts Claude already knows (testing pyramid, basic CI pipeline steps, general anti-patterns). Some sections like 'Visual Testing Strategy' and 'API Testing Coverage Areas' explain fundamentals rather than project-specific guidance.	2 / 3
Actionability	The runtime scripts table provides concrete executable commands, but most other content is conceptual guidance rather than executable code. Missing actual Playwright test examples, Page Object Model implementations, or specific configuration files that could be copy-pasted.	2 / 3
Workflow Clarity	The 'Systematic Testing' section provides a basic 3-step workflow (Map, Scan, Test), but lacks validation checkpoints or feedback loops. No explicit verification steps between stages or error recovery guidance for when tests fail.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but everything is in one file. No references to separate detailed files for Playwright configuration examples, Page Object Model templates, or CI pipeline configurations that would benefit from being split out.	2 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: lchenrique/politron-ide
Commit: 7114206

Reviewed: 29 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.