memory-view
Skill2 starsChanged 19 days agoApache-2.0View on GitHub
View and manage persistent memory - active issues, open MRs, follow-ups, environment health, recent sessions. Use when user says "view memory", "what's in memory?", or "show current work".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Mark-Life/agent-skillstheir own version, first seen Nov 6, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Mark-Life/agent-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository124 other files it gives its agents.
- add-projectSkill
- ansible-configure-vmSkill
- api-smoke-testSkill
- appinterface-checkSkill
- attach-session-to-jiraSkill
- aws-rds-debugSkill
- beerSkill
- bootstrap-all-knowledgeSkill
- bootstrap-knowledgeSkill
- build-persona-styleSkill
- cancel-pipelineSkill
- cert-checkSkill
- check-ci-healthSkill
- check-integration-testsSkill
- check-mr-feedbackSkill
- check-my-prsSkill
- check-secretsSkill
- ci-retrySkill
- cleanup-branchesSkill
- cleanup-stale-executionsSkill
- clone-jira-issueSkill
- close-issueSkill
- close-mrSkill
- cloud-inventorySkill
- coffeeSkill
- compare-optionsSkill
- create-jira-issueSkill
- create-mrSkill
- create-slide-deckSkill
- data-migration-verifySkill
- debug-local-dbSkill
- debug-prodSkill
- deploy-to-ephemeralSkill
- dev-workflow-orchestratorSkill
- discovered-work-summarySkill
- edit-slide-deckSkill
- email-digestSkill
- environment-overviewSkill
- explain-codeSkill
- export-presentationSkill
- extend-ephemeralSkill
- find-similar-codeSkill
- gather-contextSkill
- gdrive-researchSkill
- gke-cluster-opsSkill
- hello-worldSkill
- hotfixSkill
- inscope-researchSkill
- investigate-alertSkill
- investigate-service-issuesSkill
- investigate-slack-alertSkill
- jira-hygiene-allSkill
- jira-hygieneSkill
- knowledge-refreshSkill
- konflux-statusSkill
- learn-architectureSkill
- learn-patternSkill
- list-presentationsSkill
- local-build-testSkill
- local-dev-environmentSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
clear_old_sessions: Delete session files older than 7 days from memory/sessions/.
- Very specific: line 75
Use memory_ask("What am I working on?") for quick context
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Memory View - Inspect and Manage Memory
Shows current work state, learned patterns, follow-ups, and environment status. Supports optional actions.
Inputs
| Input | Type | Default | Purpose |
section | string | "all" | all, work, followups, environments, patterns, sessions |
action | string | - | clear_completed, add_followup, clear_old_sessions |
followup_text | string | - | For add_followup action |
followup_priority | string | "normal" | high, medium, normal |
slack_format | bool | false | Use <url|text> links |
Workflow
1. Load Memory via MCP
memory_read("state/current_work")- active issues, open MRs, follow_upsmemory_read("state/environments")- environment healthmemory_read("learned/patterns")- error patternsmemory_read("learned/runbooks")- runbooks- List
memory/sessions/*.yaml- recent session logs (last 5 files)
2. Perform Action (if requested)
- clear_completed: Filter
active_issues(remove Done/Closed/Resolved), filteropen_mrs(remove merged). Usememory_updateor write back. - add_followup: Append to
follow_upswith task, priority, created. Usememory_append("state/current_work", "follow_ups", item). - clear_old_sessions: Delete session files older than 7 days from
memory/sessions/.
3. Format Output by Section
work: Active issues (key, summary, status, branch), Open MRs (id, title, url, needs_review, is_draft)
followups: List with priority emoji (🔴 high, 🟡 medium, ⚪ normal)
environments: Per-env status (healthy/issues/unknown), last_check, alerts, ephemeral namespaces
patterns: Error patterns with pattern + meaning/fix
sessions: Recent dates with last 5 actions each
4. Output Format
# 🧠 Memory View
## 📋 Current Work
### Active Issues (N)
- **AAP-XXXXX** - summary | Status: X | Branch: `branch`
### Open MRs (N)
- !1234 - title 👀📝
## 📌 Follow-ups
- 🔴/🟡/⚪ task
## 🌐 Environment Status
### ✅/⚠️/❓ stage/production/konflux
## 💡 Learned Patterns
## 📜 Recent Sessions
---
### Available Actions
- Clear completed: skill_run("memory_view", '{"action": "clear_completed"}')
- Add follow-up: skill_run("memory_view", '{"action": "add_followup", "followup_text": "..."}')Key Details
- Chains to:
memory_edit,memory_cleanup - Use
memory_ask("What am I working on?")for quick context - Linkify Jira keys and MR IDs in output
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

