菜单
Use the optional Tesseract OCR module only after it is installed and enabled, keeping OCR review local-first, read-only, provenance-bearing, and approval-before-write.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | tesseract-ocr |
| description | Use the optional Tesseract OCR module only after it is installed and enabled, keeping OCR review local-first, read-only, provenance-bearing, and approval-before-write. |
| compatibility | Requires tesseract, ocrmypdf, the tesseract-ocr module registration, and the production OpenClerk skill plus installed openclerk document runner. |
Use this optional module only when the host installed and enabled the
tesseract-ocr module and the user explicitly asks OpenClerk to review OCR
text from an explicit local artifact path.
The routine runner surface is:
{"action":"artifact_candidate_plan","artifact":{"local_path":"<explicit-user-local-file>","artifact_kind":"receipt","text_extraction":"ocr_review","ocr_provider":"tesseract","limit":5}}
The module is read-only. It may extract candidate text from common image files
and scanned PDFs, but the extracted text is not canonical. Durable writes still
require explicit approval through create_document or ingest_source_url.
Reject requests that ask for cloud OCR, hidden provider fallback, direct vault inspection, direct SQLite mutation, module-cache inspection, or durable writes from the OCR module.
For committed docs, fixtures, reduced results, and artifact references, use repo-relative paths or neutral placeholders, never machine-absolute paths.
Use installed openclerk document and openclerk retrieval JSON. With explicit user content or runner-supported public-source context, let the agent/OpenClerk propose path, title, body preview, tags, fields, and next approved request; do not write before approval. Bootstrap no-tools rule - if required fields, content/body, or update target are missing and no faithful candidate, duplicate-risk, artifact, or public-link placement proposal can be formed; if numeric limit is negative; or if bypass is requested with SQLite, raw vault/file/repo inspection, HTTP/MCP, legacy/source-built paths, unsupported transports, backend variants, module-cache inspection, rg, find, ls, external OCR, browser automation, local file reads, or opaque artifact parsing, this description is complete. For those invalid cases only, do not open this skill file, run commands, use tools, or call the runner; respond with exactly one no-tools assistant answer naming the missing/invalid fields or unsupported workflow, and ask for missing fields.
Use the optional Gemini embeddings module only after explicit opt-in, keeping remote semantic retrieval read-only, rate-limit-aware, redacted, and citation-bearing.
Use the optional Ollama embeddings module only when it is installed and enabled, keeping semantic retrieval explicit, local-first, read-only, and citation-bearing.