Individual skill
octocode-scraping
Use when extracting or mapping public web content into a local cited corpus: scrape or crawl a URL/docs site, pull tables/pricing/product fields, diagnose blocked or thin pages, or answer from saved pages. Phrases like scrape this URL, crawl the docs, build a corpus, extract pricing. Prefer keyless fetch; ask before hosted spend. Live clicks/HAR/perf → octocode-chrome-devtools.
skills/octocode-scraping/SKILL.md
Source commit c265e3f9413161c900cbf4aa70d451b8e6b3920a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 958
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- claude-ai Repository topic
- cursor-ai Repository topic
- development Repository topic
- mcp Repository topic
- modelcontextprotocol Repository topic
- octocode Repository topic
- ai-agents Repository topic
- ai-tools Repository topic
- code-intelligence Repository topic
- writing Derived category
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 965 bytesSKILL.mdcore · 5,283 bytesdocs/ADDING_A_VENDOR.mddoc · 4,134 bytesdocs/PROVIDERS.mddoc · 2,325 bytesreferences/browser-scraping.mddoc · 1,953 bytesreferences/data-contract.mddoc · 2,494 bytesreferences/extraction-quality.mddoc · 1,105 bytesreferences/failure-recovery.mddoc · 1,531 bytesreferences/providers.mddoc · 1,040 bytesreferences/route-selection.mddoc · 1,068 bytesreferences/scraping-policy.mddoc · 1,336 bytesreferences/scrapingant.mddoc · 1,716 bytesreferences/session-corpus.mddoc · 1,465 bytesreferences/user-inputs.mddoc · 1,109 bytesreferences/website-analysis.mddoc · 2,975 bytesscripts/README.mddoc · 1,270 bytesscripts/corpus-find.mjsruns · 4,079 bytesscripts/corpus-inspect.mjsruns · 2,028 bytesscripts/corpus-run.mjsruns · 8,997 bytesscripts/dom-find.mjsruns · 2,130 bytesscripts/fetch-and-brief.mjsruns · 1,457 bytesscripts/fetch.mjsruns · 4,741 bytesscripts/graph-navigate.mjsruns · 2,715 bytesscripts/har-ingest.mjsruns · 12,933 bytesscripts/lib/analyzers.mjsruns · 14,654 bytesscripts/lib/args.mjsruns · 5,535 bytesscripts/lib/bridge.mjsruns · 9,927 bytesscripts/lib/client.mjsruns · 12,276 bytesscripts/lib/corpus.mjsruns · 19,298 bytesscripts/lib/extractors.mjsruns · 10,751 bytesscripts/lib/providers.mjsruns · 1,508 bytesscripts/lib/text.mjsruns · 3,858 bytesscripts/provider-check.mjsruns · 2,173 bytesscripts/provider-usage.mjsruns · 1,445 bytesscripts/resource-list.mjsruns · 2,274 bytesscripts/schema-helper.mjsruns · 2,090 bytesscripts/schemas/graph.schema.jsonasset · 2,582 bytesscripts/schemas/provider.schema.jsonasset · 2,352 bytesscripts/scrapingant-check.mjsruns · 436 bytesscripts/scrapingant-fetch.mjsruns · 418 bytesscripts/scrapingant-usage.mjsruns · 436 bytes
Read excerpt
# Octocode Scraping
Flow: `FRAME → POLICY → ROUTE → FETCH → CORPUS → SEARCH → CITE → RECOVER`.
FRAME before the first fetch: fix target URL/domain, goal, depth, and output shape — vague ask → `references/user-inputs.md`.
Defaults: one public URL, `--mode html`, omit `--provider` (keyless `cdp`→`direct`), session `.octocode/tmp/scrape/{sessionId}`, compact stdout. Search corpus before refetch. Live interaction → chrome-devtools on one port, then `har-ingest` + `corpus-run` into the same session. Ask before auth, hosted spend, crawl widen, CAPTCHA/MFA, destructive actions. Cite paths + URL metadata — not raw dumps.
Stop when: two same-class failures (report evidence, route tried, sanitized status, next approval); hosted `403` (wrong key or credits gone — status only, no retry); CAPTCHA/MFA, auth wall, or cookie/profile transfer needed; still blocked after one `cdp` try (ask before `--provider scrapingant`); personal data, form submits, purchases, sends, deletes, or account changes in scope; the saved corpus already proves the claim (cite it, do not refetch); crawl widen before `reports/summary.md` is useful. Recovery table: `references/failure-recovery.md`.
## Route (pick one)
| Need | Do | Skip |
|---|---|---|
| Vague scrape | `--mode html`, omit `--provider` | markdown / auto hosted |