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.

54

Quality

61%

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

61%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 body is actionable and well-structured with a real progressive-disclosure reference, but redundancy and a partly irrelevant Code Review section reduce conciseness, and the workflow lacks an explicit post-fix validation step.

Suggestions

De-duplicate the blocked-pattern list between Quick Reference and Check, and drop the irrelevant server-config/headers/cookies framing from Code Review.

Add an explicit re-test-with-uBlock step after the Fix section to close the validation loop.

Tighten the Explain section to a sentence rather than restating Quick Reference content.

DimensionReasoningScore

Conciseness

Mostly efficient, but the blocked-pattern list is repeated across Quick Reference and Check, and the Code Review section (server config, headers, cookies) is boilerplate largely irrelevant to adblock element hiding.

3 / 5

Actionability

Provides concrete, executable guidance — specific patterns to scan for, 'test with uBlock Origin enabled', and concrete rename alternatives like .privacy-controls and .cookie-preferences — with only minor gaps.

4 / 5

Workflow Clarity

A Check-then-Fix sequence is present with an implicit verification (test with uBlock), but there is no explicit re-test-after-rename checkpoint, leaving validation implicit.

3 / 5

Progressive Disclosure

Well-organized sections with a clearly signaled, verified one-level-deep reference to references/rule.md; minor organization gaps from the templated Explain/Code Review sections.

4 / 5

Total

14

/

20

Passed

Description

62%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 is well-targeted to a clear niche with an explicit 'Use when' trigger, but its action coverage is narrow and the trigger phrasing is more technical than naturally user-spoken.

Suggestions

Add 1-2 more concrete actions (e.g., 'identifies hidden elements and suggests semantic class renames') to lift specificity.

Soften the trigger with natural user phrasing such as 'when elements disappear for adblock users' alongside the technical clause.

DimensionReasoningScore

Specificity

Names the domain (adblocker filter rules) and one concrete action ('reviewing a website for layout and functionality issues'), but does not enumerate multiple distinct actions, fitting the 'domain + 1-2 concrete actions' anchor.

3 / 5

Completeness

Has an explicit 'Use when...' clause and states both what (reviewing for adblocker-caused issues) and when (reviewing a website for such issues), though the 'when' could be more specific with concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes some natural terms ('reviewing a website', 'layout and functionality issues', 'adblocker') but leans technical ('filter rules targeting common ad-related class names and IDs') and lacks common synonyms a user would naturally say.

3 / 5

Distinctiveness Conflict Risk

The adblocker-element-hiding niche is mostly distinct with specific triggers, with only minor overlap risk against general web-layout review skills.

4 / 5

Total

14

/

20

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.