Claude DuetNo income, hours or cost disclosed in the source.Public · Free

Break a large quarterly PDF into short documents, requisitions and summary tables

r/ClaudeAI 讨论串发帖人(原帖不可读,未取得用户名)Reddit · Date not disclosed

Read original

Saved text / editorial summary

采集站 agentusecases.ai 的编辑摘要(原帖 Reddit 线程在本次采集时不可读,以下为转述而非引文):发帖人描述了一项每三个月处理一次的工作:收到一份很大的 PDF,在普通聊天窗口里用 Claude 把它转成许多短文档、基于 Excel 的请购单和汇总表。他说关键的一步是学会为这套工作流做一个可复用的技能,同时由于无法给 Claude 开通工作网盘权限,整个流程仍保持手工。结果方面,他说这套做法对这项季度工作而言好到令人惊讶,但没有给出数量、节省时间或错误率;他还说尚未让 Claude 参与更多其他工作。限制在于访问权限:他无法把工作网盘开放给 Claude,也没有描述 Google Drive 或 OneDrive 的接入方式。

Business model

A user describes a job they repeat every three months: they receive a large PDF and use Claude in an ordinary chat window to turn it into many short documents, Excel-based requisitions and summary tables. They say the key step was learning to build a reusable skill for that workflow, while keeping the process manual because Claude was not given access to work drives. The result was, in their words, mind-blowing for that quarterly job, but they give no page counts, hours saved or error rates. What transfers is not splitting a PDF; it is the decision to freeze a recurring task into a reusable skill rather than re-describing it every quarter.

A reusable instruction can preserve the split boundaries and field rules for the next quarter. Whether it saves time depends on how similar the next document is and how much review is needed; no timing comparison was reported or tested here.

Workflow

  1. Do one round by hand first and note three things: where to cut, which fields each short document needs, and which columns the requisition needs.
  2. Freeze those rules into a reusable skill: cut boundaries, naming, field list, and how to mark anything uncertain.
  3. After uploading the PDF, ask only for a table of contents and a proposed split, with titles, page ranges and key figures per part.
  4. Generate the short documents in batches once the split is approved, keeping original section numbers and leaving gaps blank.
  5. Extract requisition lines from the text, each with a source page number, writing NOT AVAILABLE rather than inventing amounts.
  6. Have a human check the money and quantity figures against the source, then file the outputs and fold any problems back into the skill.

Adaptation plan

The source gives no page count, no processing time, no error rate and no cost. It is unclear how large the PDF is, how many documents result, or how much manual checking the author does. The author says they have not extended this to other work. The original text could not be read at collection time (Reddit returned HTTP 403 on every public endpoint; no Wayback snapshot). The workflow, prompt and pitfalls here are AgentFlow proposals, untested.

Starter prompt

Written by AgentFlow; not the original author’s prompt. Not independently deployed in Muse or Grok.

You are a document splitting assistant. Break one large file into distributable pieces. Do not judge content and do not fill gaps.

[INPUT]
Attachment: one large PDF, contents [description, e.g. quarterly report or annual purchasing manual]
Split by: [section / topic / department]
Requisition columns: Item | Specification | Quantity | Estimated amount | Source page | Notes
Summary metrics: [list 3 to 6 metric names]

[EXECUTION STEPS]
1) First output only a table of contents and a proposed split: title, page range and key figures for each part. Do not generate any body text yet.
2) After I confirm the split, generate the short documents in batches, each keeping its original section number.
3) Leave anything the source does not state blank. Never fill it in from common formats, industry practice or your own inference.
4) Produce the requisition separately: only items the source explicitly says need to be requested or purchased, each row with a source page.
5) Produce the summary table last: only the metrics I named, each cell annotated with its source page.
6) Close with an output manifest and an uncertainty list: what you produced, which figures you are unsure about, and which pages were unreadable.

[OUTPUT REQUIREMENTS]
- Short documents: one file each, title includes the original section number, no content from other sections.
- Requisition: one item per row, source page always filled; write "not available" if the amount is not stated.
- Summary table: only the metrics I specified. Do not add metrics of your own.
- Uncertainties listed separately, never embedded in the body text or tables.

[HUMAN CONFIRMATION POINTS]
- The split plan needs my approval before any body text is generated.
- Amounts and quantities in the summary and requisition are mine to verify against the source before use.
- Filing and distribution are mine to do; no drive or system write access is granted.

[COMPLETE SMALL SYNTHETIC INPUT AND OUTPUT — not real business data; no model execution]
The JSON contains all demo inputs and a manually authored reference output. Do not invent facts from files not supplied. This reference covers only this minimal input and is not a business reproduction.
{
  "input": {
    "pages": [
      {
        "page": 1,
        "text": "Section A: current spend 110; previous spend 100."
      },
      {
        "page": 2,
        "text": "Section B: request A4 paper, 40 packs. Amount not stated."
      }
    ],
    "split_by": "section",
    "summary_metrics": [
      "current_spend",
      "previous_spend",
      "change_pct",
      "requisition_count"
    ]
  },
  "expected_output": {
    "split_plan": [
      {
        "section": "A",
        "pages": [
          1
        ]
      },
      {
        "section": "B",
        "pages": [
          2
        ]
      }
    ],
    "requisitions": [
      {
        "item": "A4 paper",
        "quantity": 40,
        "unit": "packs",
        "amount": "not available",
        "source": "page 2"
      }
    ],
    "summary": {
      "current_spend": 110,
      "previous_spend": 100,
      "change_pct": 10,
      "requisition_count": 1
    },
    "uncertainties": [
      "Requisition amount not stated on page 2."
    ],
    "files_written": 0,
    "next_action": "human approves split and checks figures before file creation"
  },
  "mode": "synthetic_read_only_reference_not_model_execution"
}

Running costs and pitfalls

The source gives no page count, no processing time, no error rate and no cost. It is unclear how large the PDF is, how many documents result, or how much manual checking the author does. The author says they have not extended this to other work. The original text could not be read at collection time (Reddit returned HTTP 403 on every public endpoint; no Wayback snapshot). The workflow, prompt and pitfalls here are AgentFlow proposals, untested. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.

Author-reported results are not independently audited.

The breakdown and starter prompt are AgentFlow’s analysis and adaptation; results are not guaranteed.

Original text and media remain attributed to their authors.

Break a large quarterly PDF into short documents, requisitions and summary tables — AgentFlow