Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Parse, read, search, navigate, summarize, extract, or check images and documents for manipulation through xparse-cli.
Install Xparse Parse
$ npx skills add infometa/workbuddyskills --skill xparse-parse -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install infometa/workbuddyskills xparse-parse --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/connectors/textin-xparse/skills/xparse-parse .claude/skills/xparse-parse && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "xparse-parse" agent skill from https://github.com/infometa/workbuddyskills/tree/main/connectors/textin-xparse/skills/xparse-parse into .claude/skills/xparse-parse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xparse-parse", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/infometa/workbuddyskills/tree/main/connectors/textin-xparse/skills/xparse-parseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add infometa/workbuddyskills --skill xparse-parse -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install infometa/workbuddyskills xparse-parse --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/connectors/textin-xparse/skills/xparse-parse .agents/skills/xparse-parse && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "xparse-parse" agent skill from https://github.com/infometa/workbuddyskills/tree/main/connectors/textin-xparse/skills/xparse-parse into .agents/skills/xparse-parse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xparse-parse", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add infometa/workbuddyskills --skill xparse-parse -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install infometa/workbuddyskills xparse-parse --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/connectors/textin-xparse/skills/xparse-parse .cursor/skills/xparse-parse && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "xparse-parse" agent skill from https://github.com/infometa/workbuddyskills/tree/main/connectors/textin-xparse/skills/xparse-parse into .cursor/skills/xparse-parse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xparse-parse", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/infometa/workbuddyskills.git --path connectors/textin-xparse/skills/xparse-parse--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add infometa/workbuddyskills --skill xparse-parse -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install infometa/workbuddyskills xparse-parse --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/connectors/textin-xparse/skills/xparse-parse .gemini/skills/xparse-parse && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "xparse-parse" agent skill from https://github.com/infometa/workbuddyskills/tree/main/connectors/textin-xparse/skills/xparse-parse into .gemini/skills/xparse-parse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xparse-parse", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install infometa/workbuddyskills xparse-parseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add infometa/workbuddyskills --skill xparse-parse -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/connectors/textin-xparse/skills/xparse-parse .github/skills/xparse-parse && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "xparse-parse" agent skill from https://github.com/infometa/workbuddyskills/tree/main/connectors/textin-xparse/skills/xparse-parse into .github/skills/xparse-parse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xparse-parse", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add infometa/workbuddyskills --skill xparse-parse -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install infometa/workbuddyskills xparse-parse --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/connectors/textin-xparse/skills/xparse-parse .opencode/skills/xparse-parse && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "xparse-parse" agent skill from https://github.com/infometa/workbuddyskills/tree/main/connectors/textin-xparse/skills/xparse-parse into .opencode/skills/xparse-parse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xparse-parse", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
xparse-parse- GitHub stars
- 342
- Token cost
- ~12k tokens
- SKILL.md length
- 6,525 words
- Files
- 10 (incl. references, assets)
- Skills in repo
- 235
- Repo updated
- First seen
- Licence
- None found
At a glance
Parse, read, search, navigate, summarize, extract, or check images and documents for manipulation through xparse-cli.
- Works in 4 steps: Run get_doc_info and retain its exact… → Run parse --api auto without… → Use get_outline, search_text, or… → …
- Document conversion and navigation
- SKILL.md covers WorkBuddy Connector contract, Task context, Command integrity and… and Free, free-package, and paid…, plus 6 more sections
- Calls npm; reaches registry.npmmirror.com
What it does
Xparse Parse is an agent skill from infometa/workbuddyskills. Parse, read, search, navigate, summarize, extract, or check images and documents for manipulation through xparse-cli. Use for document conversion and navigation, durable Task workflows, structured extraction, and domestic TextIn manipulation/AIGC detection of a local file or URL. Prefer it over raw PDF readers or custom OCR scripts.
Its SKILL.md is about 12k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files and assets (for example `agents/openai.yaml`, `references/api-reference.md` and `references/authentication.md`).
It sits in Documents & Office, covering Document parsing. The repository describes itself as: WorkBuddy skills / connectors / experts archive for offline study.
When your agent uses it
- Document conversion and navigation
- Durable Task workflows
- Structured extraction
- Domestic TextIn manipulation/AIGC detection of a local file
Example prompts
- “/xparse-parse”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Run get_doc_info and retain its exact doc_id.
- Run parse --api auto without --page-range. A successful complete
- Use get_outline, search_text, or read_pages to locate relevant content.
- Batch the required read_content calls after navigation is complete.
What it can do on your machine
Read from SKILL.md and the folder at commit 9830caf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
registry.npmmirror.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Xparse Parse loads about 12k tokens when it runs, and up to ~25k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 6,525 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 6,525 words (~12,356 tokens).
“Use the installed xparse-cli as the only parsing, authentication, quota, and document-navigation execution kernel. Do not reproduce its HTTP, OAuth, quota, PDF splitting, or result-merging logic in the Skill.”
- name
- xparse-parse
Files
SKILL.md and 9 other files (references, assets) in connectors/textin-xparse/skills/xparse-parse of infometa/workbuddyskills.
- SKILL.md
- agents/openai.yaml
- assets/logo.png
- references/api-reference.md
- references/authentication.md
- references/cli-guidance.md
- references/error-handling.md
- references/navigation.md
- references/task-runtime.md
- references/textin-key-setup.md
Open the folder on GitHubat commit 9830caf
Compare with similar skills
Xparse Parse next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Xparse Parse this skillinfometa/workbuddyskills | 342 | — | ~12k | Automated safety check: Pass | None | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| DOCX ToolkitXiaomiMiMo/MiMo-Code | 14k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Huashu Markdown Publishing Pipelinealchaincyf/huashu-md-html | 908 | — | ~4.8k | Automated safety check: Pass | MIT | |
| Markitdownjimmc414/Kosmos | 594 | 2 repos | ~1.7k | Automated safety check: Pass | None | |
| Liteparsebastani-inc/atomic | 846 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
DOCX Toolkit
XiaomiMiMo/MiMo-Code
Produces, edits and reads Microsoft Word files through python-docx and lxml, with a decision table for picking the lightest workflow for a given task.
Huashu Markdown Publishing Pipeline
alchaincyf/huashu-md-html
Converts files and web pages into clean Markdown, then turns Markdown into polished HTML, Word, PDF and EPUB using four templates.
Markitdown
jimmc414/Kosmos
Convert various file formats (PDF, Office documents, images, audio, web content, structured data) to Markdown optimized for LLM processing.
Liteparse
bastani-inc/atomic
A skill your agent uses whenever a task involves a document file (PDF, DOCX, PPTX, XLSX, or image) and you need to read it or pull text, tables, or specific values out of it — to answer a question…
Beautiful Article
ConardLi/garden-skills
Turns a URL, PDF, DOCX, Markdown file, text or screenshots into a designed, shareable single-file HTML article through a staged review workflow.
More from infometa/workbuddyskills
All 235 skills in this repoCampus Event Playbook
infometa/workbuddyskills
This skill should be used when planning, coordinating, running, or reviewing student-led campus events, including club recruitment, freshman mixers, welcome activities, small talks, competitions…
Teachany
infometa/workbuddyskills
K-12 interactive courseware creation. An agent skill from infometa/workbuddyskills.
Weight Management HTML
infometa/workbuddyskills
A skill your agent uses when the adult weight-management MCP needs to be installed/set up in WorkBuddy (connector) or its result must be rendered as a standalone Chinese HTML plan.
Agent Browser
infometa/workbuddyskills
A skill your agent uses when the user needs browser automation, including opening web pages, taking screenshots, extracting page content, clicking elements, filling forms, or testing web flows.
AI Research Radar
infometa/workbuddyskills
定时任务：每日研究简报。漏掉重要论文和行业报告？每天帮你盯着，关键信息一条不漏 This skill should be used when the user asks about 定时任务：每日研究简报.
Check Deck
infometa/workbuddyskills
Investment banking presentation quality checker. An agent skill from infometa/workbuddyskills.
Related
Categories
Questions about Xparse Parse
What does Xparse Parse do?
Parse, read, search, navigate, summarize, extract, or check images and documents for manipulation through xparse-cli. Xparse Parse is an agent skill from infometa/workbuddyskills. Parse, read, search, navigate, summarize, extract, or check images and documents for manipulation through xparse-cli.
When should I use Xparse Parse?
Xparse Parse fits situations like: document conversion and navigation; durable Task workflows; structured extraction; domestic TextIn manipulation/AIGC detection of a local file.
How do I install Xparse Parse in Claude Code?
Run `npx skills add infometa/workbuddyskills --skill xparse-parse -a claude-code`. Or copy the skill folder (connectors/textin-xparse/skills/xparse-parse in infometa/workbuddyskills) into .claude/skills/xparse-parse in your project. Claude Code loads it when a task matches its description.
How do I install Xparse Parse in Codex?
Run `npx skills add infometa/workbuddyskills --skill xparse-parse -a codex`. Or copy the skill folder (connectors/textin-xparse/skills/xparse-parse in infometa/workbuddyskills) into .agents/skills/xparse-parse in your project. Codex loads it when a task matches its description.
Can I use Xparse Parse in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add infometa/workbuddyskills --skill xparse-parse -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/xparse-parse, .gemini/skills/xparse-parse, .github/skills/xparse-parse and .opencode/skills/xparse-parse in your project.
What does Xparse Parse need to run?
Going by SKILL.md and its folder, Xparse Parse needs the command-line tools its instructions call (npm).
Does Xparse Parse access the network?
SKILL.md names 1 domain. In commands or code: registry.npmmirror.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Xparse Parse safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Xparse Parse use?
No licence was found for Xparse Parse or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Xparse Parse use?
About 12k tokens (SKILL.md is roughly 49k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 12k tokens, read only when the agent opens those files.
What are the alternatives to Xparse Parse?
Skills that share tags, products or a category with Xparse Parse: Markitdown (ImCa0/just-laws, 781 stars), DOCX Toolkit (XiaomiMiMo/MiMo-Code, 14k stars), Huashu Markdown Publishing Pipeline (alchaincyf/huashu-md-html, 908 stars) and Markitdown (jimmc414/Kosmos, 594 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Xparse Parse?
infometa (a GitHub user) maintains it in infometa/workbuddyskills, which has 342 GitHub stars. The repository holds 235 skills in this directory. The repository was last updated on October 6, 2026.
Source: infometa/workbuddyskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.