doc-extract Skill
Extract plain text from a document file - PDF, DOCX, XLSX, PPTX, RTF, or plain text/markdown/HTML. Use when a binary document needs to be turned into text, for example a contract PDF or an EHR DocumentReference attachment. Other skills (fhir) invoke scripts/extract.ts directly; the contracts MCP server bundles its own Published by anthropics in healthcare.
Decision snapshot
Is this a fit?
Documentation, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
13 days ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is doc-extract Skill?
Extract plain text from a document file - PDF, DOCX, XLSX, PPTX, RTF, or plain text/markdown/HTML. Use when a binary document needs to be turned into text, for example a contract PDF or an EHR DocumentReference attachment. Other skills (fhir) invoke scripts/extract.ts directly; the contracts MCP server bundles its own Published by anthropics in healthcare. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Documentation use cases
Declared skill metadata
- Source file: plugins/healthcare/skills/doc-extract/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use doc-extract Skill
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/healthcare
- Skill file: plugins/healthcare/skills/doc-extract/SKILL.md
What it does
Extract plain text from a document file - PDF, DOCX, XLSX, PPTX, RTF, or plain text/markdown/HTML. Use when a binary document needs to be turned into text, for example a contract PDF or an EHR DocumentReference attachment. Other skills (fhir) invoke scripts/extract.ts directly; the contracts MCP server bundles its own
Skill instructions
doc-extract Shared document-to-text extraction. One script, no state: reads an input file, prints JSON to stdout, writes nothing to disk (PHI-safe — no caches, no temp files; callers own any caching). Setup (once) bash cd <this skill dir && bun install This pulls liteparse (the lit bin, used for PDF/DOCX/XLSX/PPTX, OCR included) and rtf-to-text (RTF). Without it, PDFs still work via a pdftotext -layout fallback if poppler is installed; other binary formats require liteparse. Use bash bun <this skill dir/scripts/extract.ts <input-file [--content-type <mime] Output on stdout: json { "text": "...", "method": "liteparse | pdftotext | rtf-to-text | passthrough", "pages": 12 } - text is page-anchored for paged formats: === [page N] === markers between pages. - pages is present when page markers exist. - method is the extractor that actually produced the text. - Format is taken from the file extension; pass --content-type (e.g. application/pdf) when the file has no useful extension, as with d
Verified compatibility and discovery
Frequently asked questions
What is doc-extract?
doc-extract is a open-source AI agent skill with Copy skill directory. Extract plain text from a document file - PDF, DOCX, XLSX, PPTX, RTF, or plain text/markdown/HTML.
Who is doc-extract best for?
doc-extract is best for reusing agent instructions, scripts, and references, documentation workflows.
How do I install doc-extract?
Install or run doc-extract using Copy skill directory. Check doc-extract for the latest setup command.
Is doc-extract actively maintained?
doc-extract may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
