webapp-testing

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

Quality

45%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agency/plugins/nori/skills/webapp-testing/SKILL.md

Quality

Content

50%

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

The content delivers a concrete, loop-based Playwright testing workflow with executable code, but it is weakened by a broken example command, conflicting headless guidance, duplicate workflow descriptions, and noise from injected <system-reminder> tags. It is functional but not polished.

Suggestions

Fix the broken single-server command (remove the stray quote in "npm run dev\" --port 5173") and reconcile the headless contradiction between the code example and the step-5 non-headless demo.

Remove the injected <system-reminder> tags and consolidate the duplicated workflow so the <required> steps and the "Web Application Testing" section are a single coherent sequence.

Make the validation checkpoint explicit (e.g., a concrete "bug reproduced / resolved" check) rather than relying on the implicit "until the bug is fixed" loop condition.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean instructions and executable code without explaining concepts Claude already knows, but it is padded with redundant injected <system-reminder> tags and a verbose TodoWrite directive that add little value.	2 / 3
Actionability	It provides a real Playwright code example and server commands, but the single-server example command is broken ("npm run dev\" --port 5173" has a stray quote) and headless guidance conflicts between the code example and step 5.	2 / 3
Workflow Clarity	A debug loop with a feedback cycle is present (add logs, run, identify, update, repeat) plus a final demo and "other tests pass" check, but validation checkpoints are implicit ("until the bug is fixed") and the structure is muddied by injected reminders.	2 / 3
Progressive Disclosure	It is a single concise file with no external bundle files, which is appropriate, but the <required> block and the "Web Application Testing" section duplicate the same workflow rather than being cleanly organized.	2 / 3
	Total	8 / 12 Passed

Description

40%

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 is short and names a domain plus two actions, but it uses second-person imperative voice, omits an explicit "Use when..." trigger, and relies on generic verbs that overlap with broader coding skills. It clears a minimal bar but misses the clarity and trigger guidance of strong examples.

Suggestions

Rewrite in third person with an explicit trigger clause, e.g. "Builds and debugs web application frontends. Use when the user asks to add features to or debug a web app UI, frontend bug, or browser-based application."

Add natural trigger variations users would actually say ("web app", "UI", "frontend bug", "browser testing") to improve trigger term coverage and distinctiveness.

Replace generic verbs ("build features", "debug anything") with more specific actions to lift specificity above anchor 2.

Dimension	Reasoning	Score
Specificity	Names the domain ("webapp frontend") and two actions ("build features", "debug"), which is anchor-2 level, but the second-person imperative voice ("Use this skill to build features...") triggers the rubric's -1 specificity penalty, dropping it to 1.	1 / 3
Completeness	It states what the skill does (build features / debug webapp frontends) but lacks an explicit "Use when..." trigger clause, so the "when" is only implied, capping completeness at 2.	2 / 3
Trigger Term Quality	"webapp frontend", "build features", and "debug" are terms a user might say, but common variations like "web application", "UI", or "browser testing" are missing, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	"webapp frontend" gives a partial niche, but "build features or debug anything" is generic and would overlap with general coding/debugging skills.	2 / 3
	Total	7 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: microsoft/FluidFramework
Path: .agency/plugins/nori/skills/webapp-testing/SKILL.md
Commit: f9f2007

Reviewed: about 7 hours 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.