How do I install the Managing Parsers skill?

Run npx skillmds@latest add xberg-io/managing-parsers in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Managing Parsers safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Managing Parsers?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Managing Parsers free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Managing Parsers?

xberg-io (@xberg-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Managing Parsers by xberg-io — Agent Skill

Name: Managing Parsers
Author: xberg-io

Managing Parsers

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`.

xberg-io Updated Sep 17, 2026

File contents

Managing parsers

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 the ts-pack CLI directly. The OpenCode tools expose only parse/process/info.

Prefetch (offline / CI)

ts-pack download python rust typescript   # specific languages
ts-pack download --all                    # every available language
ts-pack download --groups all             # by group
ts-pack download python --fresh           # clean cache first, then download

The manifest currently defines exactly one group, all. Group names are manifest data, not a fixed list — enumerate them with manifest_groups() rather than hardcoding. Run download in your CI setup step so later parse/process calls hit the cache instead of the network.

Inspect

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

Clean

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.

Config file (init)

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 is given, init also triggers the download for those languages. (init takes only --languages and --cache-dir — for group-based prefetch use ts-pack download --groups <names>.) Commit language-pack.toml to pin the parser set across a team or CI.

Typical CI flow

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

When to reach for the other skills

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.

---name: managing-parsersdescription: 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`.---# Managing parsersParser libraries download on demand the first time a language is used andare cached on disk. Manage that cache explicitly for offline work, CIprefetch, reproducible builds, or to reclaim space.> Note: parser cache management (`download`, `clean`, `init`) is done via the> `ts-pack` CLI directly. The OpenCode tools expose only parse/process/info.## Prefetch (offline / CI)```bashts-pack download python rust typescript # specific languagests-pack download --all # every available languagets-pack download --groups all # by groupts-pack download python --fresh # clean cache first, then download```The manifest currently defines exactly one group, `all`. Group names aremanifest data, not a fixed list — enumerate them with `manifest_groups()`rather than hardcoding. Run `download` in your CI setup step so later`parse`/`process` calls hit the cache instead of the network.## Inspect```bashts-pack list # all available languagests-pack list --downloaded # only languages currently cachedts-pack list --manifest # everything in the remote manifestts-pack list --filter script # filter by name substringts-pack info python # known? downloaded? cache path?ts-pack cache-dir # print the effective cache directory```## Clean```bashts-pack clean # prompts for confirmationts-pack clean --force # skip the prompt (use in scripts/CI)````clean` removes all cached parser libraries; they re-download on next use.## Config file (init)`ts-pack init` writes a `language-pack.toml` to the current directorypinning a cache location and/or a language set. This **writes a file** tothe working directory.```bashts-pack init --languages python,rust --cache-dir .ts-pack-cache```Resulting `language-pack.toml`:```tomlcache_dir = ".ts-pack-cache"languages = ["python", "rust"]```With no flags, `init` writes a commented template. When `--languages` is given,`init` also triggers the download for those languages. (`init` takes only`--languages` and `--cache-dir` — for group-based prefetch use`ts-pack download --groups <names>`.) Commit `language-pack.toml` to pin theparser set across a team or CI.## Typical CI flow```bashts-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```## When to reach for the other skillsOnce parsers are cached, use `parsing-source` to get syntax trees and`extracting-code-structure` to pull metadata. `info`/`list` here also servethe language-support checks described in `detecting-languages`.

Frequently asked questions