vbcherepanov/total-agent-memory/report

/report — activity report from memory

The report is built by the memory_report tool (your client may prefix it, e.g. mcp__memory__memory_report). It is deterministic: numbers, decisions, fixes, errors, open next steps, files and a daily timeline come straight from stored records, each with source IDs. If no memory_report tool is available, say the memory server is not connected (or is older than this skill) and stop.

1. Read the request

Take the period and project from $ARGUMENTS or the user's words:

• Project: "for project X", "in X", or the current repository/folder name when the

user says "this project". Omit project for "all projects".

• Timezone: pass tz (IANA name, e.g. Europe/Berlin) only when the user names a

zone or city; otherwise the server uses the machine's zone.

• Team server only: "department X report" → scope: "team", team_id: "X";

"company report" → scope: "company"; otherwise scope: "personal". A Forbidden error means the user lacks the department head / company viewer role: say so plainly.

2. Call the tool

Call memory_report with those arguments and format: "markdown". Add include_llm_summary: true only when the user asks for a written summary or narrative; it needs a configured LLM and the report is complete without it.

3. Present it concisely

Do not paste the whole report unless asked. Give:

1. One line with the period (as the report labels it) and the headline numbers

with their change against the previous period (records, decisions, errors, active days).

1. The 3–5 most important decisions with their WHY, and the main fixes.
2. Recurring error patterns (count this period vs all time) and lessons learned.
3. Open next steps and pitfalls that were not picked up yet.
4. Anything notable in files, technologies or the timeline (e.g. one very busy day).

Keep the #id references so the user can ask for details; fetch full records with memory_get(ids=[...]) when they do (on the team server: memory_get with the scope and id). If the report says there was no activity, say so and offer a longer period.

4. Offer to save

End by offering to save it. On yes, call memory_report again with the same arguments and save: true, then show the returned file path (<memory dir>/reports/<project>/<period>-<date>.md). The same report is available from a terminal: tam report --project X --period week [--format json] [--out FILE].