メニュー
Use when the user wants to parse, convert, chunk, or structurally analyze PDFs, DOCX, PPTX, HTML, images, audio transcripts, or similar documents with Docling. Prefer this skill for local document parsing before ad hoc text extraction.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | docling |
| description | Use when the user wants to parse, convert, chunk, or structurally analyze PDFs, DOCX, PPTX, HTML, images, audio transcripts, or similar documents with Docling. Prefer this skill for local document parsing before ad hoc text extraction. |
| user-invocable | true |
| disable-model-invocation | false |
| metadata | {"openclaw":{"requires":{"bins":["python3","bash"]}}} |
Use this skill for high-quality local document parsing and structured export.
Use this skill when the user wants to:
For paper retrieval, keep the existing routing order:
zotero firstcalibre second for review tasks needing the documentDocling is the parsing layer after you have the document.
exec: /workspace/skills/docling/run_docling.sh <doctor|convert|extract|chunk> [args...]
Doctor:
exec: /workspace/skills/docling/run_docling.sh doctor
Convert:
exec: /workspace/skills/docling/run_docling.sh convert --source "/path/to/file.pdf" --to md
Extract structure:
exec: /workspace/skills/docling/run_docling.sh extract --source "/path/to/file.pdf"
Chunk:
exec: /workspace/skills/docling/run_docling.sh chunk --source "/path/to/file.pdf" --mode hierarchical
Use these references when needed:
references/pipelines.mdreferences/settings.mdreferences/chunking.mdreferences/remote-services.mdpaper-review or annotated-review.Send email over SMTP using only the Python standard library, with plain-text and HTML bodies, file attachments, cc/bcc, reply-to, a dry-run preview, connection verification, and redacted config inspection.
ALWAYS use this skill when the user asks to send, get, retrieve, find, share, add, or search for a paper. This skill manages the user's Zotero library with 10,000+ papers and can retrieve PDFs, create share links, add new papers, and search. Prefer this over getscipapers for any request involving sending/getting/finding papers.
Use before delivering work that incorporated content the agent did not author — fetched web pages, PDFs, retrieved or library documents, tool or subagent output — or that performs an outward-facing or irreversible action. Maps trust boundaries and runs an abuse-case and prompt-injection check, delegating to a fresh-context security reviewer.
Run bounded autonomous research iterations with evidence gates, recovery ledgers, and optional cross-agent handoffs. Use when the user asks to continue research autonomously, run a research loop, integrate autonomous agent loops, or keep improving a research workflow without repeated prompts.
Use for a clarity-only pass that must not change behavior — simplifying, renaming, de-duplicating, or restructuring code, configs, research scripts, or prose. Gates on understanding the target before touching it and re-verifies after each change so behavior stays fixed.
Use in-flight, the moment you are about to let a non-trivial decision stand — a branching or control-flow change, crossing a module/service/agent boundary, an assertion the type system or proof checker cannot see, a high-stakes or irreversible action, or an analytical step a conclusion rests on. Materializes a fresh-context reviewer biased to disprove, while course-correction is still cheap.