CtrlK
BlogDocsLog inGet started
Tessl Logo

open-web

Resilient public-page reading and OSINT keyword search — web_search (allowlisted-provider OSINT) and web_fetch (curl_cffi TLS-impersonation grid + headless-browser fallback that gets past WAF/403/anti-bot). Use when a fetch is blocked, a page is JS-rendered, or you need open-web OSINT about a target/org.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

A well-structured, action-oriented skill body with clear escalation workflow and validation discipline, organized into clean sections without external file dependencies. Minor conciseness trims and a concrete example call would push it to the top tier.

Suggestions

Tighten the vendor-name lists (e.g. 'Cloudflare, Akamai, DataDome') into one consolidated mention to save tokens without losing signal.

Add one concrete web_fetch example call (e.g. web_fetch(url, selector='#content')) so the recommended selector/device knobs are shown in use.

Consider moving the platform fast-path table into a reference file if the table grows, to keep the overview lean.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence, with tight rule framing (R2, R6); a few explanatory passages about WAF vendors and escalation phrasing could be trimmed slightly.

4 / 5

Actionability

Provides concrete guidance (knobs: selector/device, fast-path table, specific retry recipe with device='mobile'), but no executable code/command examples — acceptable for this instruction/tool skill, with only minor gaps.

4 / 5

Workflow Clarity

Clear sequenced flow (web_search -> web_fetch), explicit escalation ladder with phases, and a robust validation/retry feedback loop (terminal vs non-terminal stop_reason, retry with mobile+selector) — strong checkpoints.

5 / 5

Progressive Disclosure

Well-organized single-file skill (~90 lines) with clear section headers and no nested references; appropriately self-contained for a skill that needs no external bundle files.

5 / 5

Total

18

/

20

Passed

Description

88%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.

A strong, specific description that clearly states capabilities and concrete usage triggers, distinguishing it well from generic fetch/search skills. It is dense but accurately scoped with minimal overlap risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'web_search (allowlisted-provider OSINT)' and 'web_fetch (curl_cffi TLS-impersonation grid + headless-browser fallback that gets past WAF/403/anti-bot)', giving comprehensive, specific coverage of capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (resilient reading + OSINT search with named mechanisms) and 'when' ('Use when a fetch is blocked, a page is JS-rendered, or you need open-web OSINT about a target/org').

5 / 5

Trigger Term Quality

Strong natural trigger phrases ('blocked page, 403/402, WAF, JS-rendered page, open-web OSINT') that users would say, though the term list leans technical and could include a few more plain-language synonyms.

4 / 5

Distinctiveness Conflict Risk

Clear niche (WAF/anti-bot bypass + open-web OSINT) with distinct triggers that are unlikely to fire for unrelated skills; conflict risk is minimal.

5 / 5

Total

19

/

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
PurpleAILAB/Decepticon
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.