doc-scraper_skill

This skill helps you extract and organize Snowflake documentation efficiently with cached, configurable scraping and depth control.
  • Python

26

GitHub Stars

4

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill sfc-gh-dflippo/snowflake-dbt-demo --skill doc-scraper

  • .gitignore182 B
  • pyproject.toml798 B
  • requirements.txt380 B
  • SKILL.md2.1 KB

Overview

This skill scrapes sections of docs.snowflake.com and converts pages to organized Markdown files with frontmatter. It uses a local SQLite cache with a configurable expiration to avoid re-downloading unchanged pages. The spider depth and base path are configurable to control crawl scope and volume.

How this skill works

Run the scraper with an output directory and optional flags to set the base path and spider depth. The tool crawls allowed paths, follows links up to the specified depth, converts pages to Markdown, and stores metadata. A SQLite cache stores fetched pages for the configured expiration period to speed repeated runs and reduce load. Rate-limiting and thread settings control concurrency.

When to use it

  • When you need an offline, searchable copy of Snowflake documentation sections.
  • To build documentation sites, knowledge bases, or data platform playbooks from Snowflake docs.
  • When auditing or tracking changes to specific Snowflake docs over time.
  • To extract docs for inclusion in internal developer portals or training materials.

Best practices

  • Set --base-path to limit the crawl to only the documentation area you need.
  • Start with --spider-depth=0 or 1 to verify scope before increasing depth.
  • Use the --limit flag for testing large sections to avoid long runs.
  • Inspect and tune scraper_config.yaml for max threads and allowed paths to balance speed and site load.
  • Use --dry-run to preview which pages will be processed before writing files.
  • Remove the .cache directory only if you suspect cache corruption; otherwise rely on expiration_days to refresh content.

Example use cases

  • Export the SQL reference section to Markdown for integration into an internal docs site using --base-path="/en/sql-reference/".
  • Create a weekly snapshot of a migrations guide by running the scraper with caching and storing output in a version control repo.
  • Generate a trimmed, offline copy of admin and security docs by adjusting allowed_paths and spider depth.
  • Test new scraping rules on a small set using --limit and --dry-run before full extraction.

FAQ

Cached pages expire after the configured expiration_days (default 7 days) in the scraper config.

How do I restrict the crawl to a small area?

Set --base-path to the desired docs path and lower --spider-depth to limit link traversal; the config allowed_paths also controls scope.

Can I preview actions without writing files?

Yes. Use --dry-run to see which URLs would be processed without creating output files.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational