Skills › Knowledge Work Plugins › report-builder › saved_reports.md

saved_reports.md

50 lines · small-business/skills/report-builder/reference/saved_reports.md at 2574e29

1# Saved Reports

3Report definitions the owner has already built. **Read this file before asking any questions** — re-interviewing someone about a report they defined last month is the fastest way to make this skill feel broken.

5Append a new entry after each Step 7. Never overwrite an entry; if a report changes, add a revision line beneath it with the date.

7**When this file can't be written to, save the definition next to the owner's work instead.** In an installed runtime the skill folder is often read-only, so appending here fails. Don't drop the definition and don't pretend it saved. Write it to `report-definitions.md` in the working directory, and tell the owner exactly where it went and what to do with it:

9> "Saved the definition to report-definitions.md in this folder. Keep that file with your reports — drop it back in the chat next time and I'll rerun this without asking you anything."

11On the next run, check both places: this file first, then `report-definitions.md` in the working directory, then anything the owner attached.

13---

Saved Reports

Report definitions the owner has already built. Read this file before asking any questions — re-interviewing someone about a report they defined last month is the fastest way to make this skill feel broken.

Append a new entry after each Step 7. Never overwrite an entry; if a report changes, add a revision line beneath it with the date.

When this file can't be written to, save the definition next to the owner's work instead. In an installed runtime the skill folder is often read-only, so appending here fails. Don't drop the definition and don't pretend it saved. Write it to report-definitions.md in the working directory, and tell the owner exactly where it went and what to do with it:

"Saved the definition to report-definitions.md in this folder. Keep that file with your reports — drop it back in the chat next time and I'll rerun this without asking you anything."

On the next run, check both places: this file first, then report-definitions.md in the working directory, then anything the owner attached.

Raw lines 1 to 14

15## How to match a request to a saved report

17Owners rarely use the report's exact name. Match on intent:

19| Owner says | Match to |

20|---|---|

21| "run the weekly one" | The only report with weekly cadence, or ask which if several |

22| "same as last time" | Most recently run report |

23| "the Monday numbers" | Report whose cadence is Monday |

24| "my sales report" | Report whose primary metric is sales |

26If two or more reports plausibly match, list them by name and ask which — one short question, not a re-interview.

28If nothing matches, treat it as a new report and go to Step 2.

30---

How to match a request to a saved report

Owners rarely use the report's exact name. Match on intent:

Owner says	Match to
"run the weekly one"	The only report with weekly cadence, or ask which if several
"same as last time"	Most recently run report
"the Monday numbers"	Report whose cadence is Monday
"my sales report"	Report whose primary metric is sales

If two or more reports plausibly match, list them by name and ask which — one short question, not a re-interview.

If nothing matches, treat it as a new report and go to Step 2.

Raw lines 15 to 31

32## Entry format

34```

35### <Report name>

36Created: <YYYY-MM-DD>

37Last run: <YYYY-MM-DD>

38Cadence: <one-off | weekly | monthly | quarterly>

40<the full spec, in the format from report_spec.md>

42Revisions:

43 <YYYY-MM-DD> — <what changed and why>

44```

46---

Entry format

### <Report name>
Created:   <YYYY-MM-DD>
Last run:  <YYYY-MM-DD>
Cadence:   <one-off | weekly | monthly | quarterly>

<the full spec, in the format from report_spec.md>

Revisions:
  <YYYY-MM-DD> — <what changed and why>