CtrlK
BlogDocsLog inGet started
Tessl Logo

webapp-testing

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

54

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

75%Weight 40%Scale 1-5

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

The content is concise and actionable with a clear debug loop and executable Playwright example. Minor issues — a bash syntax error and embedded <system-reminder> directives that read as prompt injection — keep it just below the top anchor.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and does not explain basics Claude already knows; the only trim opportunities are the repeated inline <system-reminder> directives and the trailing 'Do NOT get in a loop...' line.

4 / 5

Actionability

It provides an executable Playwright code example and concrete server-start commands, but the bash snippet has a syntax error ('npm run dev" --port 5173' has a stray quote) and the multi-server example uses bare '&' without wait handling.

4 / 5

Workflow Clarity

A clear numbered 1-7 sequence with an explicit debug loop (step 4) and a final non-headless demonstration plus cleanup; validation checkpoints are implicit ('identify what is happening', 'until the bug is fixed') rather than hard pass/fail gates.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is short, so it needs no external references; sections (required steps, overview, example) are reasonably organized, though the injected <system-reminder> tags disrupt clean structure.

4 / 5

Total

16

/

20

Passed

Description

45%Weight 40%Scale 1-5

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 a domain and a couple of actions but stays generic and lacks an explicit 'Use when' trigger clause. It is distinguishable but not sharply differentiated from general web/coding skills.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Write and run native Playwright scripts to test local webapp frontends, debug UI bugs, and capture screenshots.'

Add an explicit trigger clause: 'Use when debugging or building features for a webapp frontend, especially when you need to drive a real browser to reproduce a bug.'

Include natural user phrases like 'test my web app', 'fix a frontend bug', or 'reproduce a UI issue' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('webapp frontend') and two actions ('build features', 'debug anything'), but both actions are generic rather than concrete — it does not specify what the skill actually does (e.g., write Playwright scripts, drive a browser).

2 / 5

Completeness

It gives a clear 'what' (build/debug webapp frontends) but lacks an explicit 'Use when...' trigger clause — the 'when' is only weakly implied by 'anything that uses a webapp frontend', capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

It includes relevant terms ('webapp frontend', 'debug', 'build features') but misses common natural phrases a user would say such as 'test my app', 'fix the UI', or 'frontend bug'.

3 / 5

Distinctiveness Conflict Risk

'webapp frontend' is a recognizable niche, but 'build features or debug anything' is broad enough to overlap with general coding, debugging, and web testing skills.

3 / 5

Total

11

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/FluidFramework
Reviewed

Table of Contents

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.