CtrlK
BlogDocsLog inGet started
Tessl Logo

web-search-and-fetch

Run Google searches and fetch JS-rendered web pages as Markdown via `google-search-cli`, a Patchright-based CLI invoked through `uvx` from its GitHub repo (no local install needed). Use when the agent needs (1) fresh Google search results from a query, (2) the Markdown of a URL that plain HTTP fetch (curl/WebFetch) cannot render because it requires JavaScript or evades bots, or (3) inspection of the raw HTML of a Google results page. Trigger phrases include "google for ...", "search the web for ...", "fetch this page as markdown", "this page needs JS to render". Do not use for static doc URLs that WebFetch handles cleanly, or when Chromium cannot be installed on the machine.

77

Quality

96%

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

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

Tight, executable, and well-structured: exact command templates, a clear sequenced workflow with feedback loops, and an explicit failure policy. The only weakness is minor verbosity in a few editorial sections that could be condensed.

Suggestions

Collapse the duplicated 'do not loop' guidance so it appears once rather than restated across the Workflow and command-flag sections.

Tighten 'Critical default quirks' to a compact bulleted contrast (search=headless, fetch-markdown=headed) without the editorial framing.

DimensionReasoningScore

Conciseness

Mostly lean with no concept over-explanation, but contains minor padding — the 'Critical default quirks' framing, a restated install rationale, and repeated 'Do not loop' phrasing across sections — that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready uvx command templates with all flags documented and concrete example invocations (e.g. '-w 5 or -w 10', '--max-n-chars 500000') covering common cases.

5 / 5

Workflow Clarity

Numbered workflow with explicit checkpoints: parse output, re-invoke once with a larger limit or higher -w (no looping), and a separate Failure Policy with exit-code branching and a Chromium-missing handoff.

5 / 5

Progressive Disclosure

A single self-contained SKILL.md with no bundle files, well-organized into Prerequisites / Commands / Output contract / Quirks / Workflow / Failure policy / Examples — clear navigation with no nested references.

5 / 5

Total

19

/

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.

A precise, third-person description that names the tool and mechanism, enumerates concrete capabilities, and gives explicit trigger phrases plus a negative-scope boundary. It is slightly dense and padded with parentheticals but every element earns its place.

Suggestions

Trim the parenthetical '(no local install needed)' and the 'Trigger phrases include' framing to tighten the description without losing triggers.

Consider moving the 'Do not use for ... when Chromium cannot be installed' boundary closer to the 'Use when' clause so what/when/anti-when read as one block.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Run Google searches', 'fetch JS-rendered web pages as Markdown', 'inspection of the raw HTML of a Google results page' — via a named tool, giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (run searches / fetch JS-rendered pages as Markdown) and 'when' with a numbered 'Use when' clause and concrete trigger phrases, plus a 'Do not use for' boundary.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms and variants: 'google for ...', 'search the web for ...', 'fetch this page as markdown', 'this page needs JS to render'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (JS-rendered / anti-bot page fetching via patchright) with distinct triggers and an explicit 'Do not use for static doc URLs that WebFetch handles' boundary, minimizing conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ceshine/ceshine-agent-skills
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.