Start with the minimum information needed for the selected question. Pasted text, Markdown tables and delimited text exports are sufficient for many workflows.
Explain the records
State the reporting period, units, currency if relevant, what each row represents, key field definitions and how the records were obtained. Include source freshness and known omissions.
Use neutral record identifiers to connect related tables. Do not replace distinct records with the same placeholder; that can destroy the ability to reconcile them.
Share only necessary details
Use role labels instead of personal names when identity is irrelevant. Remove unnecessary contact details, credentials and private notes before building a reusable example.
The real business may need some identifying information for an authorized task. Keep that information in its working documents, not in a publicly shared skill template.
Preserve interpretation
Keep original records distinguishable from corrected or summarized versions. Record filters, exclusions and assumptions.
For document images, verify extracted dates, amounts, units and reference numbers against the source. Unreadable text stays unknown.
For spreadsheets, include the calculation logic or values needed for the task. A screenshot can omit hidden rows, formulas and precision; identify these limits.
If the host cannot open the file
Paste the relevant rows or sections and explain their meaning. Use a small representative sample for planning, clearly labeled as a sample. Do not claim it establishes totals or patterns for unseen records.
If the dataset exceeds the host's reliable calculation ability, return a method, required fields and validation plan. Use a suitable authorized computation tool before claiming large-scale results.