Parse Document

Documents

parse-document

Parse Document is an Agent Skill for documents published in the superlinked/sie repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Convert a PDF, scan, image of a page, or office file to clean markdown through the connected Superlinked MCP edge, so the source document is not read into model context directly. Use when the user asks to read, parse, OCR, extract from, summarize, or answer questions about a document.

View on GitHub ↗

QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

Open your project in Codex.
Copy and paste the prompt below.
Review files and risks before approving any action.

Prompt to paste

Inspect the Agent Skill at https://github.com/superlinked/sie/blob/HEAD/packages/sie_mcp/plugin/claude-code/parse-document/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/parse-document, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Parse a Document with Superlinked MCP

Use the connected Superlinked MCP server to convert the source file to markdown, then work from the markdown artifact. This mirrors the parse-document flow from the sie_tools plugin in PR #1336, but uses the MCP docs_to_markdown tool instead of the gateway-backed ~/.sie/bin/sie wrapper.

Steps

Do not open, view, attach, or read the source document into context. Read its raw bytes only and base64-encode those bytes.
Call the Superlinked MCP docs_to_markdown tool with:
- document_base64: the base64-encoded source bytes
- filename: the original filename
- engine: auto unless the user explicitly asks to force docling or vl-ocr
- ocr: leave false unless forcing the docling OCR path
Write the returned markdown to processed/<source-stem>.md. Create processed/ if it does not exist.
Your next message must begin with a short receipt, then answer from the artifact selectively:
```
Parsed <source> -> processed/<source-stem>.md (<chars> chars)
```
If the MCP metadata includes token-saving figures, include those figures directly under the receipt. Keep estimates marked as estimates.
Answer the user's question from the artifact. Grep or read specific sections; do not read the whole markdown file unless it is small.

Errors

If the MCP call fails, relay the tool error and do not retry blindly. For auth or connector errors, tell the user to reinstall the generated MCP plugin pack or rerun the generated claude mcp add ... --header 'Authorization: Bearer ...' command from INSTALL.md.