web-region-capture
Skill32 starsChanged 7 days agoMITView on GitHub
Capture explicit, purity-checked web regions into folders or Excel; official lark-cli Base adapter is dry-run by default. Use for repeatable local browser/Excel evidence, not arbitrary one-click website automation.
In this repository20 other files it gives its agents.
- baidu-hot-cnSkill
- coze_workflowSkill
- douyin-hot-trendSkill
- ec_creatorSkill
- geopulseSkill
- glm-asrSkill
- glm-visionSkill
- image_gen_cozeSkill
- longtask_systemSkill
- minimax-avSkill
- rss_fetcherSkill
- scribeSkill
- skills-hubSkill
- style-fingerprintSkill
- toutiao-news-trendsSkill
- weibo-hot-searchSkill
- weibo-publisherSkill
- weixin-connectorSkill
- xhs-dlSkill
- zhihu-fetcherSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
All relative paths (including local HTML and workbooks) resolve from --root.
- Very specific: line 32
Default --dry-run: capture evidence into data/runs/<run-id>/, but do not write final folder/Excel targets and invoke Base only with …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
web-region-capture
Run from a client-independent project root
This is a Python CLI, not a Codex/Claude/WorkBuddy plugin. Read README.md, config/local.example.json, and config/tasks.m2-example.json. Do not use client-specific APIs. Current working directory does not affect relative project paths.
python -m web_region_capture --root /path/to/project doctor
python -m web_region_capture --root /path/to/project run --config config/tasks.m2-example.json --run-id "我的 任务"With a fresh checkout run scripts/bootstrap.sh on macOS/Linux or scripts/bootstrap.ps1 on Windows. If the package is not installed, use PYTHONPATH=<root>/src (shell) or $env:PYTHONPATH=<root>/src (PowerShell). Default browser is Playwright-managed Chromium; never assume Chrome or OpenCLI. OpenCLI is not an implemented runner in M2.
Required task contract
version: 1; either inlinesiteorsite_file.site.start_url: HTTPS or project-root-relative HTML file; optional explicitactions,identity,viewport,headless.- Each task has a unique safe
task_id,subject_query, nonemptyregions; all regions must have site recipes. - Folder:
destination.type=folder,path. - Excel:
source_path,path, exactsheet, andcellsmapping every region to an A1 cell. Source is never overwritten..xlsxonly; output images are floating cell anchors, not Microsoft 365 Place-in-Cell values. - Base:
base_token,table_id,record_id,fieldsmapping every region to an attachment field. Only officiallark-cli base +record-upload-attachment --as useris used. Base is not Excel; no A1 coordinates.
All relative paths (including local HTML and workbooks) resolve from --root; Unicode and spaces are supported. No cookie/password/secret belongs in config or logs. Never require a client-provided proprietary browser or Feishu SDK.
Run, evidence and safe rerun
Default --dry-run: capture evidence into data/runs/<run-id>/, but do not write final folder/Excel targets and invoke Base only with lark-cli --dry-run. --execute-local enables local folder/Excel output; it does not authorize Base.
Every run has manifest.json with config fingerprint, region purity evidence, hashes, per-task state. Reusing a run ID without --resume is blocked. --resume skips completed artifacts only if hashes/config fingerprints still match; failed or changed work requires explicit diagnosis/new run. Output conflicts stop instead of overwriting. A dry-run manifest cannot be mistaken for delivered.
needs_readback after a real Base upload is not delivered: official record readback and attachment download/hash comparison must be completed. Real write additionally requires task allow_live_write=true, allow_replace=false, and CLI --authorize-lark-write. Default append only. Never use real Base data for smoke tests; ask Noah to provide an authorized test target.
Validate before declaring completion
python tests/run-offline-poc.pyEvidence must name the activated tests and skipped environments. Windows, OpenCLI, live Base, and external clients are not verified by a macOS local run. For public-site acceptance, use a separate explicitly supplied site/task config; a local fixture is not public-site proof.
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
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.

