agentleFS
wangge-aiwangge-ai/wangge-skills/skills/webbridge-archive-publisher/SKILL.md

webbridge-archive-publisher

Skill4 starsChanged 39 days agoMITView on GitHub

Use when crawling, archiving, exporting, or packaging a URL, logged-in

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Kimi WebBridge for the user's real logged-in browser session.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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 Archive Publisher

Archive browser-only sources without persisting credentials or session secrets.

Workflow

  1. Confirm the source URL, authorization state, scope, and desired artifacts.
  2. Use Kimi WebBridge for the user's real logged-in browser session. Use the current Browser/Chrome surface when the user selects it or when Kimi is unavailable.
  3. Capture source URL, title, collected time, visible content, attachments, and failure reasons.
  4. Save raw evidence separately from cleaned Markdown and presentation HTML.
  5. Generate screenshots or PDF when visual layout matters.
  6. Build a folder reader with scripts/build_archive_reader.py only for the legacy page-JSON plus screenshot layout.
  7. For rich Feishu archives, multi-batch deduplication, or a self-contained HTML likely to exceed 100 MB, return the verified per-document HTML/assets layout to web-collection-orchestrator; use its streaming bundle builder and cold first-open QA. Do not embed the whole archive in one JSON object or place the catalog script after the asset payload.
  8. Store output under ./outputs/collection\web-archive\<date-task>.

Never save passwords, cookies, tokens, authenticated request headers, or sensitive session URLs. Stop at CAPTCHA or access restrictions. The old PowerShell scripts are compatibility helpers only; prefer the installed Kimi WebBridge v1.11.6 workflow. Treat “works after refresh” as a failed first-open check until the directory renders on a cold open.

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.