메뉴
Use when the user needs to manage the tree-sitter parser cache — prefetch parsers for offline or CI runs, list what is downloaded, inspect a language, find the cache directory, or clean it. Covers `ts-pack download`, `list`, `info`, `cache-dir`, `clean`, and `init`.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Use when extracting a page needs scripted interaction first — click, type, press a key, scroll, wait, screenshot, or run JS before capturing the DOM. Covers `crawlberg interact <url> --actions` with the real action schema, result shape, limits, and external-CDP options.
Crawl, scrape, and convert websites to Markdown using the local crawlberg CLI and its MCP server. Use when the user wants to fetch a page, follow links across a domain, enumerate URLs, or drive a real browser. Covers installation, the subcommands (scrape, crawl, map, interact, mcp, serve), output formats (JSON + Markdown), browser fallback, and when to prefer the MCP server over shelling out.
Use when the user wants to follow links across a domain and capture every reachable page as Markdown. Covers `crawlberg crawl` with depth, page caps, concurrency, rate limiting, domain scoping, robots, and output selection.
Use when a static fetch returns nothing useful and the page needs a real browser. Covers `--browser-mode auto|always|never`, external CDP via `--browser-endpoint`, symptoms of JS-only pages and WAF blocks, and the performance cost.
Use when the user wants the list of URLs on a site rather than the page content — sitemap analysis, link planning, or seeding another tool. Covers `crawlberg map <url>` with `--limit`, `--search`, robots, output, and how it differs from a full crawl.
Use when the user wants a single page rendered as clean Markdown plus structured metadata. Covers `crawlberg scrape <url>`, JSON vs Markdown output, what metadata is returned, and how to handle JS-heavy pages.
| name | managing-parsers |
| description | Use when the user needs to manage the tree-sitter parser cache — prefetch parsers for offline or CI runs, list what is downloaded, inspect a language, find the cache directory, or clean it. Covers `ts-pack download`, `list`, `info`, `cache-dir`, `clean`, and `init`. |
Parser libraries download on demand the first time a language is used and are cached on disk. Manage that cache explicitly for offline work, CI prefetch, reproducible builds, or to reclaim space.
Note: parser cache management (
download,clean,init) is done via thets-packCLI directly. The OpenCode tools expose only parse/process/info.
ts-pack download python rust typescript # specific languages
ts-pack download --all # every available language
ts-pack download --groups web,systems # by group
ts-pack download python --fresh # clean cache first, then download
Available groups: web, systems, scripting, data, jvm,
functional (comma-separated for --groups). Run download in your CI
setup step so later parse/process calls hit the cache instead of the
network.
ts-pack list # all available languages
ts-pack list --downloaded # only languages currently cached
ts-pack list --manifest # everything in the remote manifest
ts-pack list --filter script # filter by name substring
ts-pack info python # known? downloaded? cache path?
ts-pack cache-dir # print the effective cache directory
ts-pack clean # prompts for confirmation
ts-pack clean --force # skip the prompt (use in scripts/CI)
clean removes all cached parser libraries; they re-download on next use.
ts-pack init writes a language-pack.toml to the current directory
pinning a cache location and/or a language set. This writes a file to
the working directory.
ts-pack init --languages python,rust --cache-dir .ts-pack-cache
Resulting language-pack.toml:
cache_dir = ".ts-pack-cache"
languages = ["python", "rust"]
With no flags, init writes a commented template. When --languages (or a
group set) is given, init also triggers the download for those languages.
Commit language-pack.toml to pin the parser set across a team or CI.
ts-pack init --languages python,rust,typescript --cache-dir .ts-pack-cache
# ... later steps run parse/process offline against the warm cache ...
ts-pack list --downloaded # assert the expected parsers are present
Once parsers are cached, use parsing-source to get syntax trees and
extracting-code-structure to pull metadata. info/list here also serve
the language-support checks described in detecting-languages.