メニュー
This skill should be used when the user types "/from-run", "/from-run 42", or "/from-run clear". It exposes Retriever's visible slash-command surface for scoping results to a processing run.
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 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.
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.
| name | from-run |
| description | This skill should be used when the user types "/from-run", "/from-run 42", or "/from-run clear". It exposes Retriever's visible slash-command surface for scoping results to a processing run. |
| 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 for /from-run, /from-run <run-id>, and /from-run clear.
For the exact read-only form /from-run:
/from-run: python3 skills/tool-template/tools.py slash . /from-runRETRIEVER_CANONICAL_TOOL_PATH pointed at ../tool-template/tools.py.For /from-run <run-id> and /from-run clear:
/from-run.