agentleFS
LocalKinAILocalKinAI/kinclaw/skills/web/SKILL.md

web

Skill9 starsChanged 6 months agoApache-2.0View on GitHub

Universal web tool — fetches and interacts with web pages through real Chromium (Playwright). Renders JavaScript, follows redirects, handles cookies, bypasses many anti-scrape stubs that block plain `web_fetch`. Each call launches a fresh browser, executes the requested flow, closes. ~2-3s cold start; no persistent state.

  • Installs packages

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No sidecar, no port management, no lifecycle skill.

    line 223

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

web — universal Playwright-backed page tool

Single skill, single Python script (web.py), single Chromium per call. Drop-in replacement for web_fetch when JS rendering / dynamic content / minor interaction is needed.

Why one cold start per call is fine

Most web tasks the agent runs are one-shot: "fetch this page", "click this and read the result", "screenshot this URL". Cold start ~2s amortizes over a single useful task. Multi-step flows where state needs to persist (login → navigate → fill form → submit → read) are rare in agent usage; if you need them, write the whole flow as one web call by chaining click=... type_text=... wait_for=....

Architecture

agent → kinclaw shell skill → python3 web.py <args>
                              → Playwright launches Chromium
                              → executes flow
                              → closes Chromium
                              → prints result
                              → exits

No sidecar, no port management, no lifecycle skill. Just pip install playwright && playwright install chromium once per machine, then web works whenever the agent needs it.

What it doesn't do

  • Persistent session (cookies, login state) across calls — each call is a fresh browser. For real-account tasks, drive the user's actual Safari via osascript activate Safari + ui skill.
  • Anti-bot bypass on Cloudflare / DataDome / advanced fingerprinting — Playwright defaults are detectable. Closed-source web_scrape via WEB_ENDPOINT env is the answer when this matters.
  • Sub-agent autonomy — this skill executes literal instructions, it doesn't plan multi-step research. For "find me cheapest X" the agent itself drives the loop (web_search → pick URLs → web fetch each → synthesize).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.