菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Extract people, organizations, dates, amounts, or custom labels from a document through the connected Superlinked MCP edge, returning a compact table instead of reading the full document into context. Use when the user asks to list, extract, or tabulate entities from a file.
Redact personal data from a document through the connected Superlinked MCP edge before working with the content. Use when the user asks to redact, anonymize, scrub, de-identify, or remove PII/sensitive data from a document.
Summarize a long PDF, scan, office file, text file, or markdown file through the connected Superlinked MCP edge instead of reading the whole source into model context. Use when the user asks for a summary, overview, digest, or "what does this document say" about a large file.
Offload document, image, and structured-output work to the Superlinked inference cluster: convert PDF/DOCX/PPTX/XLSX/HTML/scans to clean markdown, describe an image (caption + tags), or produce schema/grammar-constrained JSON off the cluster — instead of ingesting the file directly, which can reduce the tokens billed in many cases for document- and image-heavy work. Use whenever the user drops or references a document or image file to read, summarize, extract from, describe, or answer questions over, or when they need reliable structured (schema-valid) output.
| name | parse-document |
| description | 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. |
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.
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 bytesfilename: the original filenameengine: auto unless the user explicitly asks to force docling or
vl-ocrocr: leave false unless forcing the docling OCR pathWrite 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.
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.