report-memory
Skill135 starsChanged 2 months agoMITView on GitHub
Retrieve knowledge base memories created in a date range. Use for: memory report, show memories, new memories, memories for March, what memories were created, knowledge base additions, KB entries.
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Language: All languages (do not pass --language unless user specifies one)
- Very specific: line 31
When only a month name is given without a year, use the current year.
- Very specific: line 44
After the command completes, read the output file with read_file to get the JSON results.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Report Memory
When to Use
- Reviewing what knowledge base memories were created during a period
- Auditing KB growth for a specific language
- Checking what the system has learned from resolved threads
Defaults
Unless the user says otherwise, always apply these defaults:
- Environment:
production - Language: All languages (do not pass
--languageunless user specifies one) - Format: JSON (do not pass
--format)
Date Resolution
The user will typically specify a calendar month by name (e.g. "March", "January 2025"). Resolve to the full month date range:
| User says | start_date | end_date |
| "March" (current year) | YYYY-03-01 | YYYY-03-31 |
| "January 2025" | 2025-01-01 | 2025-01-31 |
| "March 1 to March 15" | YYYY-03-01 | YYYY-03-15 |
When only a month name is given without a year, use the current year. Be careful with month lengths (28/29/30/31 days).
Running the Command
Step 1: Run the Command
Show the resolved command and run it immediately in a foreground terminal with a 60-second timeout (timeout: 60000). Redirect to a file since output can be large.
Full terminal command (cleanup + run):
New-Item -ItemType Directory -Path output -Force | Out-Null; if (Test-Path output/memory_output.json) { Remove-Item output/memory_output.json }; python cli.py report memory -s <start_date> -e <end_date> | Out-File -Encoding UTF8 output/memory_output.jsonAfter the command completes, read the output file with read_file to get the JSON results. Summarize the findings for the user (total count, breakdown by language, etc.).
Step 2: Answer Follow-up Questions
For follow-up questions about the same data (filtering, counting, searching), read the output file with read_file instead of re-running the command. The file is at output/memory_output.json.
Examples
# All memories for March 2025
python cli.py report memory -s 2025-03-01 -e 2025-03-31
# Python memories only
python cli.py report memory -s 2025-03-01 -e 2025-03-31 -l python
# YAML output
python cli.py report memory -s 2025-03-01 -e 2025-03-31 --format yaml
# Staging environment
python cli.py report memory -s 2025-03-01 -e 2025-03-31 --environment stagingAvailable Flags
| Flag | Type | Default | Description |
--start-date / -s | string | required | Start date (YYYY-MM-DD) |
--end-date / -e | string | required | End date (YYYY-MM-DD) |
--language / -l | string | all | Language to filter by (e.g., python, csharp, C#) |
--environment | string | production | production or staging |
--format / -f | string | json | Output format: json or yaml |
Output
Each memory object includes:
id— Cosmos DB document IDlanguage— Language the memory applies tocreated_at— Human-readable timestamp (converted from Cosmos_ts)- Memory content fields (rule, context, etc.)
Gotchas
- Date filtering uses Cosmos
_ts: Filters by when the document was created/modified in Cosmos DB, not by any explicit date field in the memory content. - Output can be large: Redirect to file and use
read_filerather than relying on terminal output. - Use
python cli.pynot.\avc: Theavc.batscript may resolve to system Python. - Do NOT use
2>&1: Merges stderr into stdout, corrupting JSON. Only redirect stdout. - Do NOT use
>: Produces UTF-16 in PowerShell 5.1. Use| Out-File -Encoding UTF8. - Month end dates: February has 28/29 days, April/June/Sept/Nov have 30 days.
In this repository43 other files it gives its agents.
- packages/python-packages/apiview-copilot/AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- azsdk-common-apiview-feedback-resolutionSkill
- azsdk-common-generate-sdk-locallySkill
- azsdk-common-generate-sdk-pipelineSkill
- azsdk-common-pipeline-analysisSkill
- azsdk-common-pipeline-fixerSkill
- azsdk-common-prepare-release-planSkill
- azsdk-common-sdk-breaking-changeSkill
- azsdk-common-sdk-releaseSkill
- azsdk-common-typespec-namingSkill
- azure-typespec-assessmentSkill
- azure-typespec-authorSkill
- code-reviewSkill
- eval-authoring-skillSkill
- eval-authoring-toolSkill
- eval-authoring-workflowSkill
- markdown-token-optimizerSkill
- sdk-ai-bot-eval-datasetSkill
- sdk-ai-bot-run-evaluationSkill
- skill-authoringSkill
- add-endpointSkill
- audit-filtersSkill
- dev-setupSkill
- kb-searchSkill
- report-active-reviewsSkill
- report-apiview-metricsSkill
- report-architect-commentsSkill
- report-feedbackSkill
- report-revisionsSkill
- run-evalsSkill
- run-metricsSkill
- update-guidelinesSkill
- apiview-feedback-resolutionSkill
- azure-typespec-authorSkill
- generate-sdk-locallySkill
- azsdk-common-live-and-recorded-testsSkill
- markdown-token-optimizerSkill
- pipeline-troubleshootingSkill
- azsdk-common-prepare-release-planSkill
- azsdk-common-sdk-releaseSkill
- skill-authoringSkill
- pr-review-helpSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

