CtrlK
BlogDocsLog inGet started
Tessl Logo

element-hiding

Use when reviewing a website for layout and functionality issues caused by adblocker filter rules targeting common ad-related class names and IDs.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/element-hiding/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

A well-structured, lean overview that delegates detail appropriately to a single real reference file. Its weak spots are content duplication, the absence of executable code in the body, and an implicit rather than explicit verification workflow.

Suggestions

Remove the duplicated blocked-name list and rename guidance — keep them in one section (or only in references/rule.md) and cross-reference instead of restating.

Add a small executable snippet to the body (e.g., a DevTools/console check for display:none on a consent selector) so the guidance is copy-paste ready, or move the existing reference code example up.

Make the workflow explicit with numbered steps and a validation checkpoint, e.g. '1. Inspect source for ad-named selectors; 2. Rename; 3. Reload with uBlock Origin enabled and confirm the consent banner is visible'.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but blocked-name lists and rename guidance are repeated across 'Quick Reference' and the 'Check'/'Fix' sections, so it could be tightened past the anchor-2 level.

2 / 3

Actionability

It gives concrete specifics (exact class names to avoid, safe renames like '.privacy-controls', test with uBlock Origin), but the body lacks executable code/commands and the test step is high-level ('Test the page with uBlock Origin enabled'), leaving guidance incomplete rather than copy-paste ready.

2 / 3

Workflow Clarity

The Check/Fix/Code Review sections imply a loose identify→rename→verify sequence and mention verifying 'against the effective production-like response', but steps are not crisply numbered with explicit validation checkpoints, fitting anchor-2.

2 / 3

Progressive Disclosure

The body is a concise overview with a clearly signaled one-level-deep pointer ('see references/rule.md') to an existing reference file, matching anchor-3's 'clear overview with well-signaled one-level-deep references'.

3 / 3

Total

9

/

12

Passed

Description

75%

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

A focused, well-triggered description with an explicit 'Use when...' clause and a clear niche. Its main weakness is single-action specificity and somewhat incomplete natural-keyword coverage.

DimensionReasoningScore

Specificity

It names the domain and a concrete action ('reviewing a website for layout and functionality issues caused by adblocker filter rules targeting common ad-related class names and IDs'), but only lists one action rather than multiple distinct concrete actions, so it falls short of the anchor-3 'extract/fill/merge' level.

2 / 3

Completeness

It opens with an explicit 'Use when...' trigger and states both what the skill does (review for adblocker-caused layout/functionality issues from class names/IDs) and when to use it, satisfying the anchor-3 'both what AND when' requirement.

3 / 3

Trigger Term Quality

Relevant keywords like 'adblocker', 'layout and functionality issues', 'website', and 'class names and IDs' are present and fairly natural, but coverage is incomplete — missing common variations such as 'ad blocker' (two words), 'uBlock', or 'consent banner'.

2 / 3

Distinctiveness Conflict Risk

The niche — adblocker filter rules hiding elements via ad-related class names and IDs — is specific and unlikely to trigger for unrelated skills, matching the anchor-3 'clear niche with distinct triggers'.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.