memory-documentary
/memory-documentary
Generate evidence-based documentary reports by searching across all 3 memory systems (Claude-Mem, Serena, DeepWiki), .agents/ artifacts, and GitHub issues. Produces investigative journalism-style analysis with full citation chains. Use when you ask for an "evidence-based report", "investigate across all memory systems", "what happened with X over time". Do NOT use for a single semantic recall (use memory) or for citation hygiene (use memory-enhancement).
- Author
- rjmurillo ↗
- Repository
- ai-agents ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 1
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
Generate evidence-based documentary reports by searching across all 3 memory systems (Claude-Mem, Serena, DeepWiki), .agents/ artifacts, and GitHub issues. Produces investigative journalism-style analysis with full citation chains. Use when you ask for an "evidence-based report", "investigate across all memory systems", "what happened with X over time". Do NOT use for a single semantic recall (use memory) or for citation hygiene (use memory-enhancement).
Triggers from the description
Original author description
Generate evidence-based documentary reports by searching across all 3 memory systems (Claude-Mem, Serena, DeepWiki), .agents/ artifacts, and GitHub issues. Produces investigative journalism-style analysis with full citation chains. Use when you ask for an "evidence-based report", "investigate across all memory systems", "what happened with X over time". Do NOT use for a single semantic recall (use memory) or for citation hygiene (use memory-enhancement).
How it works
- Quick Start
- Triggers
- When to Use
- Quick Reference
- Process
- Commands
- Report Structure
- Evidence Standards
- Anti-Patterns
- Verification
SKILL.md preview
---
name: memory-documentary
version: 1.0.0
description: Generate evidence-based documentary reports by searching across all 3
memory systems (Claude-Mem, Serena, DeepWiki), .agents/ artifacts, and
GitHub issues. Produces investigative journalism-style analysis with full citation
chains. Use when you ask for an "evidence-based report", "investigate across all
memory systems", "what happened with X over time". Do NOT use for a single semantic
recall (use memory) or for citation hygiene (use memory-enhancement).
license: MIT
metadata:
timelessness: 8/10
category: analysis
routing:
role: nested-helper
invoker: memory
trigger: memory routes narrative cross-system report requests to memory-documentary
user-facing: false
---
# Memory Documentary Skill
Generate comprehensive documentary-style reports from your memory systems with full evidence chains.
<!-- vendor-portability: declared. This skill searches the consumer's .agents/ artifacts (sessions, retrospectives, analysis) alongside the three memory systems as evidence inputs, and writes the report under .project-toolkit/. The .project-toolkit/ reads are best-effort evidence sources; a vendored install without that tree produces a report from whatever memory systems and artifacts the consumer repo does have, not a silent no-op. -->
---
## Quick Start
```text
/memory-documentary [topic]
```
Example topics:
- "recurring frustrations"
- "coding patterns not codified"
- "evolution of thinking on testing"
- "decisions I second-guessed"
- "what I complain about most"
---
## Triggers
Use this skill when:
- `Search my memories for patterns about...`
- `What does my history say about...`
- `Generate a documentary on my topic`
- `Cross-reference all systems for...`
- `Evidence-based analysis across memory systems`
---
## When to Use
Use this skill when:
- You need cross-system evidence for a pattern or recurring theme
- Investigating historical decisions and their evolution over time
- Building a cited, verifiable narrative from memory data
Use `memory` skill instead when:
- You need a simple search for a known fact or pattern
- The query targets a single memory tier, not cross-system synthesis
## Quick Reference
| Phase | Action | Output |
|-------|--------|--------|
| 1 | Topic Comprehension | Search variants, scope boundaries |
| 2 | Investigation Planning | Explicit queries per system |
| 3 | Data Collection | Evidence with retrieval keys and dates |
| 4 | Report Generation | Documentary with citations |
| 5 | Memory Updates | Store meta-pattern discovered |
---
## Process
The skill searches ALL available data sources systematically:
**Memory Systems (3 MCP servers)**:
- Claude-Mem: Timeline observations via 3-layer workflow
- Serena: Project-specific lexical memory
- DeepWiki: Documentation resources
**Project Artifacts**:
- `.project-toolkit/retrospective/` - Learning extractions
- `.project-toolkit/sessions/` - Session logs
- `.project-toolkit/analysis/` - Research reports
- `.project-toolkit/architecture/` - ADRs
- `.project-toolkit/planning/` - Plans and PRDs
**GitHub Issues**:
- Open and closed issues
- Comments and related PRs
---
## Commands
```bash
# Standard invocation
/memory-documentary "recurring frustrations"
# With explicit time range
/memory-documentary "testing patterns" --since 2025-12-01
```
---
## Report Structure
### Executive Summary
- Key finding in one sentence
- Timeline span (earliest to most recent)
- Evidence count (memories + observations + issues + files)
- Major pattern categories
### Evidence Trail
Full citation for each finding:
- Source system (Claude-Mem/Serena/DeepWiki)
- Retrieval key with its command: an observation id for Claude-Mem, a memory file name for Serena
- Date, from the source for Claude-Mem, from git history for a Serena file
- Direct quote from source
- Links to related evidence
### Pattern Evolution
Timeline showing how thinking changed:
```text
YYYY-MM-DD: [Observation #ID] - Initial state
YYYY-MM-DD: [Serena memory-name] - First iteration
YYYY-MM-DD: [Issue #NNN] - Technical response
```
### Unexpected Patterns
Cross-system synthesis revealing:
- Frequency patterns (time clustering)
- Correlation patterns (X happens before Y)
- Avoidance patterns (conspicuous absence)
- Contradiction patterns (saying vs doing)
- Evolution patterns (recursive loops)
- Emotional patterns (frustration markers)
### Synthesis
- What all systems agree on
- What's recent (Claude-Mem) vs durable (Serena)
- Actionable recommendations
---
## Evidence Standards
| Standard | Requirement |
|----------|-------------|
| Citation | Every claim has a retrieval key, a date, and a quote |
| Quotes | Direct quotes, not paraphrases |
| Verification | Retrieval commands for all evidence |
| Cross-links | Related evidence connected |
---
## Anti-Patterns
| Avoid | Why | Instead |
|-------|-----|---------|
| Partial searches | Miss critical evidence | Search ALL systems |
| Paraphrasing | Loses verifiability | Direct quotes only |
| Single query | Miss variations | 3+ query variants per system |
| Skipping systems | Incomplete picture | Check all 3 MCP servers |
---
## Verification
After execution:
- [ ] Report saved to `.project-toolkit/analysis/[topic]-documentary-[date].md`
- [ ] Every claim has a citation with source system, retrieval key, and direct quote
- [ ] All 3 MCP servers were queried (or documented as unavailable)
- [ ] Meta-pattern stored in memory (Phase 5)
## Output Location
Reports saved to: `.project-toolkit/analysis/[topic]-documentary-[date].md`
---
## Related Skills
| Skill | Relationship |
|-------|--------------|
| memory | Operations (search, update) |
| retrospective | Learning extraction |
| skillbook | Pattern → skill conversion |
---
## On Invocation
**Read**: `references/execution-protocol.md`
This contains the full 5-phase execution protocol with detailed instructions for each data source.
Files in this package (2)
- SKILL.md 6 KB
- references/execution-protocol.md 7 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
Database snapshot: 13.11.2026 · package version 7e339029c860 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100memory-enhancement
Manage memory citations, verify code references, and track confidence scores. Use when adding citations to memories, checking memory health, or verifying code references are still valid. Use when you say "add a citation", "verify this memory's code refs", "check memory health".… - 100memory-enhancement
Manage memory citations, verify code references, and track confidence scores. Use when adding citations to memories, checking memory health, or verifying code references are still valid. Use when you say "add a citation", "verify this memory's code refs", "check memory health".… - 100memory-evidence
Use when saving or updating a Claude Code memory note that states something about code, configuration, commands or system behavior, and when freshlint reports that a memory needs re-checking. Covers Evidence lines, citation forms, and how to re-check a stale memory. - 90agent-memory
Use when implementing or managing persistent, hierarchical memory systems for AI agents. Covers cross-session state, fact supersession, and self-managed memory tools to enable long-term recall and adaptive agent behavior. - 90conversation-memory
Persistent memory systems for LLM conversations including short-term, long-term, and entity-based memory Use when: conversation memory, remember, memory persistence, long-term memory, chat history. - 100setup-project
When setting up agentskel on a new project that does not yet have .memory/ or .agents/. Use when the user says "set up agentskel", "install agentskel", or "add agent memory to this project".