CtrlK
BlogDocsLog inGet started
Tessl Logo

blocked-links

Use when reviewing HTML source and JavaScript for links or resource URLs pointing to domains listed in common adblocker filter lists.

60

Quality

71%

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/blocked-links/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 well-structured overview that defers detail to a clearly signaled one-level-deep reference, with concrete and actionable review guidance. The weakest area is workflow clarity, where the review sequence lacks explicit numbered steps and in-body validation checkpoints.

Suggestions

Convert Check/Fix/Code Review into a short numbered sequence so the review workflow order is explicit rather than implied by section order.

Surface a compact in-body verification checkpoint (e.g., 'Confirm each flagged URL is actually blocked by loading the page with uBlock Origin and checking the Network tab for blocked requests') instead of relying solely on the reference.

Trim the restatement of the problem that appears in both the intro paragraph and the first Quick Reference bullet to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is lean with short sections and bullets and mostly assumes Claude's competence; the main issue is minor redundancy where the problem is restated across the intro, Quick Reference, and Explain sections.

4 / 5

Actionability

Concrete, specific guidance is given (named tracking domains, uBlock Origin testing, reverse proxy, server-side routes, direct UTM URLs), with executable code appropriately deferred to the reference file.

4 / 5

Workflow Clarity

The Check/Fix/Explain/Code Review sections provide a loose sequence, but steps are not numbered and validation is only hinted ('verify them against the effective production-like response') with the bulk delegated to the reference.

3 / 5

Progressive Disclosure

A clean one-level-deep structure: SKILL.md is an overview and the single well-signaled `references/rule.md` holds implementation details, code, and framework guidance, making navigation easy.

5 / 5

Total

16

/

20

Passed

Description

70%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 concise, uses an explicit 'Use when...' trigger in acceptable third-person imperative voice, and carves out a distinct niche. Its main limitation is fusing the 'what' and 'when' into a single clause instead of separately enumerating concrete actions.

Suggestions

Lead with a short clause of concrete actions before the trigger (e.g., 'Identifies links and resource URLs pointing to adblocker-blocked tracking domains. Use when reviewing HTML source or JavaScript...').

Add common synonyms users might say, such as 'tracking domains' or 'adblock', to broaden natural trigger coverage.

Optionally name one or two representative blocked domains (e.g., googletagmanager.com, doubleclick.net) to sharpen distinctiveness from sibling security rules.

DimensionReasoningScore

Specificity

Names the domain (reviewing HTML/JS for links and resource URLs on adblocker filter-list domains) and one concrete action, but does not enumerate multiple actions, so coverage is not comprehensive.

3 / 5

Completeness

An explicit and specific 'Use when...' trigger is present, and the 'what' (reviewing for blocked-domain links) is conveyed, but the 'what' is fused into the when clause rather than stated as distinct enumerated actions.

4 / 5

Trigger Term Quality

Good natural keywords a frontend reviewer would say (HTML source, JavaScript, links, resource URLs, domains, adblocker filter lists), though common synonyms like 'tracking domains' or 'adblock' are absent.

4 / 5

Distinctiveness Conflict Risk

The adblocker filter-list framing is a clear niche with minimal conflict risk, but as one of presumably several sibling frontendchecklist security rules there is minor overlap risk with closely related review skills.

4 / 5

Total

15

/

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.