CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

73%

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 a compact, well-sectioned overview with genuinely actionable check and fix guidance and an appropriate one-level reference bundle. Its weaknesses are duplicated content between sections, vague boilerplate 'Explain' and 'Code Review' sections, and a workflow that lacks an explicit post-fix verification checkpoint.

Suggestions

Deduplicate the blocked-pattern list (Quick Reference vs. Check) into a single authoritative list, or move the full list to references/rule.md and keep only a few examples inline.

Trim or rewrite the generic 'Explain' and 'Code Review' sections, which describe rather than instruct, or fold them into Check/Fix.

Add an explicit post-fix verification step, e.g., 'After renaming, reload the page with uBlock Origin enabled and confirm the element is visible.'

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the blocked-name list is duplicated ("Common blocked names: .ad, .ads, .advertisement, .banner..." in Quick Reference vs. ".ad, .ads, .advertisement, .banner, .sponsor, #ad, #banner..." in Check), the cookie-banner warning appears twice (intro paragraph and Fix section), and the "Explain" and "Code Review" sections describe rather than instruct. This fits the 'mostly efficient but could be tightened' anchor rather than the noticeably padded one.

3 / 5

Actionability

Concrete, executable guidance is present: specific patterns to scan for (.ad, .banner, #ad, .cookie-notice), a named test tool ("Test the page with uBlock Origin enabled in a browser"), and specific safe renames ("use class names like .privacy-controls or .cookie-preferences"). Minor gaps remain — no grep/scan command or detection snippet in the body, and the executable examples live only in references/rule.md.

4 / 5

Workflow Clarity

The Check → Fix sequence is present but unnumbered, and validation is incomplete: testing with uBlock Origin is positioned only inside Check, with no post-fix re-test checkpoint to confirm renamed elements are no longer hidden. This matches 'steps listed but validation gaps; checkpoints missing or implicit' rather than the anchor-4 example with numbered steps and an explicit verify step.

3 / 5

Progressive Disclosure

The body is a well-organized overview and the single reference is one level deep, clearly signaled ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md"), and the file exists with that content. Minor gaps: the reference is only mentioned in a bottom footer rather than contextually from the Check/Fix sections, and some body content (blocked names, rename suggestions) duplicates rule.md.

4 / 5

Total

14

/

20

Passed

Description

73%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 a strong, niche-specific trigger sentence with an explicit 'Use when' clause and good natural keywords. Its main weaknesses are a single embedded action (review only) with no explicit statement of remediation or testing capabilities, and a few missing common trigger synonyms like 'uBlock Origin' or 'ad blocker'.

Suggestions

Add an explicit capability statement before the trigger clause, e.g., 'Identifies HTML elements hidden by adblocker filter rules (EasyList/uBlock) and recommends safe class and ID renames.'

Include common trigger synonyms such as 'uBlock Origin', 'EasyList', 'ad blocker', and 'hidden elements' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ("adblocker filter rules targeting common ad-related class names and IDs") and one concrete action ("reviewing a website for layout and functionality issues"), matching the anchor for 1-2 concrete actions without comprehensive coverage. It falls short of 4 because it lists only a single review action and omits other capabilities like renaming elements or testing with an adblocker.

3 / 5

Completeness

An explicit "Use when..." trigger clause is present ("Use when reviewing a website for layout and functionality issues caused by adblocker filter rules..."), and a concrete 'what' is embedded in that clause. Not 5 because the 'what' is never stated as a standalone capability and omits the fix/rename and testing actions the skill actually covers.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "adblocker", "filter rules", "class names", "IDs", "layout", "functionality issues", "website". A few natural terms users would say are missing, such as "ad blocker" (spaced variant), "uBlock Origin", "EasyList", or "hidden/missing elements", so it does not reach the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

"Adblocker filter rules targeting common ad-related class names and IDs" is a clear niche with distinct triggers; virtually no other skill category would match this description, so conflict risk is minimal.

5 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/element-hiding/SKILL.md

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.