Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →thedaviddias/blocked-links
Use when reviewing HTML source and JavaScript for links or resource URLs pointing to domains listed in common adblocker filter lists.
Passed 22 of 23 test cases with the skill, and 18 of 23 without it.
and 2 more in the full report
5 fixed17 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Name two well-known vendor domain names that are commonly included in default browser adblocker filter lists and blocked at the network layer.
| Checked | Without skill | With skill |
|---|---|---|
| Mentions googletagmanager.com as a commonly blocked tracking domain | Missed | Passed |
The instructions your model reads when the skill loads.
When a navigation link's URL matches a tracking domain pattern, the adblocker may block the request entirely — the user clicks the link and nothing happens, breaking core site functionality.
Identify external script sources, image src URLs, iframe src URLs, and anchor href values that point to known tracking domains (googletagmanager.com, hotjar.com, facebook.net, doubleclick.net, etc.). Test whether these resources load successfully with uBlock Origin enabled.
Self-host critical external scripts on your own domain. Use a reverse proxy or server-side route to forward requests to third-party analytics APIs. For navigation links, avoid using tracking redirect URLs — use direct destination URLs with UTM parameters appended instead.
Explain how domain-level adblocker filter lists work, which domains are commonly blocked, how blocked resources affect site functionality and analytics accuracy, and the self-hosting approach to bypass domain blocks.
Review server config, headers, forms, and integration points related to Blocked Tracking Links. Flag exact responses, cookies, or browser behaviors that violate the rule, and verify them against the effective production-like response.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/security/blocked-links
test cases passed, vs 18 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.