CtrlK
BlogDocsLog inGet started
Tessl Logo

ultimate-browsing

Escalation skill for blocked or hard-to-reach web access — load it when a normal browse/fetch is blocked (WAF, 403, Cloudflare, JS-only render, login-gated, or a platform a generic fetcher cannot read). Tiered router: TIER 1 insane-search (headless extraction + WAF bypass via curl_cffi TLS impersonation, yt-dlp, Jina Reader, public APIs, Playwright real-Chrome fallback); TIER 1.5 agent-reach (platform-native readers for Chinese and social platforms: Xiaohongshu, Douyin, Weibo, Bilibili, V2EX, WeChat, plus Twitter/Reddit/LinkedIn/GitHub); TIER 2 Chrome stealth (CloakBrowser stealth Chromium + agent-browser CDP for clicks, forms, screenshots, video, cookie login). Triggers: blocked site, bypass bot detection, cloudflare/WAF bypass, scrape, stealth browser, import cookies, fill form, screenshot, play youtube, xiaohongshu, douyin, weibo, bilibili, v2ex, wechat article, podcast transcript. NOT for simple searches (use web-search) or plain fetches (use webfetch).

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 well-structured with an explicit routing phase, executable per-tier commands, and clean one-level-deep progressive disclosure to real reference files. Its main weakness is mild verbosity in rationale prose and implicit rather than explicit validation loops for the fragile Tier-2 interaction flow.

Suggestions

Tighten or remove restated tier rationale prose (e.g. '~10x faster than a browser, no process spin-up') since the routing table already conveys ordering.

Add an explicit validate->fix->retry checkpoint for the Tier-2 cookie-login flow (e.g. 'after injecting cookies, reload and verify the logged-in state before proceeding').

Inline one fully complete Tier-1 command example with all common flags to reduce reliance on the reference for the most common case.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands and a compact routing diagram, but includes some explanatory prose (e.g. '~10x faster than a browser, no process spin-up' and restated tier descriptions) that could be trimmed. Not a 5 because a few sentences restate concepts or tier rationale already implied by the diagram.

4 / 5

Actionability

Provides concrete, copy-pasteable commands for each tier (`python3 -m engine`, `yt-dlp`, `mcporter call`, `curl`, `agent-browser --cdp 9242 ...`) with flags explained inline. Not a 5 because Tier 1/1.5 rely partly on references for the full command surface and a few examples are illustrative rather than complete.

4 / 5

Workflow Clarity

The mandatory Phase 0 routing table clearly sequences decision branches across tiers, and escalation conditions are explicit ('Escalate to Tier 1.5 or Tier 2 when ...'). Not a 5 because validation checkpoints for the fragile Tier-2 cookie/login flow are implied (reload after inject) rather than framed as an explicit validate-retry loop.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview pointing to one-level-deep references (insane-search/README.md, agent-reach/README.md, chrome-stealth.md, plus per-category subfiles), all of which exist in the bundle, with a summary reference table; navigation is well-signaled and content is appropriately split.

5 / 5

Total

17

/

20

Passed

Description

100%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 highly specific, covers natural trigger terms comprehensively, explicitly answers both what and when with concrete trigger phrases, and clearly distinguishes itself from adjacent skills. It is somewhat long, but the length reflects genuine technical specificity rather than fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across three tiers — 'headless extraction + WAF bypass via curl_cffi TLS impersonation, yt-dlp, Jina Reader, public APIs, Playwright real-Chrome fallback' and 'platform-native readers ... click, forms, screenshots, video, cookie login' — with comprehensive coverage matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers both 'what' (tiered router with named tools per tier) and 'when' ('load it when a normal browse/fetch is blocked (WAF, 403, Cloudflare, JS-only render, login-gated...)') plus explicit exclusion guidance ('NOT for simple searches ... use web-search'), satisfying the score-5 anchor.

5 / 5

Trigger Term Quality

Includes natural user phrases and platform synonyms users actually say: 'blocked site', 'bypass bot detection', 'cloudflare/WAF bypass', 'scrape', 'stealth browser', 'import cookies', 'fill form', 'screenshot', plus platform names (xiaohongshu, douyin, weibo, bilibili, v2ex, wechat), matching comprehensive synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (blocked/hard-to-reach web escalation) and explicitly differentiates from web-search and webfetch ('NOT for simple searches ... NOT for ... plain fetches'), minimizing conflict risk as the score-5 anchor describes.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 12 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 25 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
code-yeongyu/lazycodex
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.