菜单
Use this skill when the user wants Retriever to ingest a processed litigation or eDiscovery production such as a DAT/OPT/TEXT/IMAGES set, a Bates-numbered volume, or explicitly asks to run ingest-production.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill when the user wants to export the current active scope or result set as a CSV table or archive, inspect export progress, or otherwise "save", "download", "bundle", or "hand off" Retriever results — or when the user types "/export".
Use this skill when the user wants to ingest, index, import, load, add, upload, or process files or folders into Retriever, or to refresh changed files, ingest a processed production, or explain what was ingested — including phrasings like "index this folder", "import these files", "load the Downloads directory", "add this PST to the collection", "upload and process this batch", "re-index the gmail-max mbox", or "what did you ingest". It bootstraps the workspace if needed, chooses between ingest and ingest-production, and summarizes the results.
Use this skill when the user wants Retriever to ingest or inspect Outlook PST mail archives. It covers the first-class libpff-python / pypff-backed PST container pipeline, where one PST source expands into message documents plus attachment children.
Use this skill when a Retriever task needs the shared routing ladder, result presentation contract, filesystem safety rules, or Tier 1-to-Tier 3 fallback policy. This is the shared operating surface that other Retriever skills reference as `retriever:routing`.
Use this skill when the user wants to execute a planned Retriever processing run inline or in the background — including natural-language phrasings like "run OCR", "start the image-description job", "kick off the OCR worker", "process the queue", "execute run 42", "resume the stalled run", or "finish processing". It decides between inline execution and spawning a subagent, and drives the claim / complete / heartbeat loop against the processing DB.
Use this skill when working with Retriever's canonical tool bundle. It defines the pinned generated tools.py bundle, checksum expectations, and the current command surface.
| name | ingest-production |
| description | Use this skill when the user wants Retriever to ingest a processed litigation or eDiscovery production such as a DAT/OPT/TEXT/IMAGES set, a Bates-numbered volume, or explicitly asks to run ingest-production. |
| metadata | {"version":"1.1.17"} |
Operates under
retriever:routing. If the user's intent actually fits a different tier — anotherretriever:*skill, a Tier 2 slash, a Tier 3tools.pysubcommand, or (last resort) direct DB access — stop and re-route against the ladder before continuing.
Use this skill when the user says things like:
python3 skills/tool-template/tools.py workspace status --quick <workspace> before the first ingest. For already-known workspaces, run it whenever runtime state is unclear.workspace init or the first ingest fails with SQLite WAL, journal-mode, mount, or sandbox wording, stop normal production-ingest execution and follow the mounted/sandboxed SQLite bootstrap troubleshooting.df, mount, or host filesystem labels alone..retriever/retriever.db path.python3 skills/tool-template/tools.py ingest <workspace> --recursive --path <production-root-relative-path> --budget-seconds 35next_recommended_commands while more_work_remaining: true; stop only on completed, failed, or canceled.ingest-production only when the user explicitly asks for that command, when running outside the normal bounded Claude Code command window, or when debugging production-only parity.ingest without --file-types should detect and route the production through the production pipeline.control_number and that linked TEXT/, IMAGES/, and NATIVES/ files remain source parts rather than top-level documents.