Ijfw Memory Audit
Audit and clean project memory files. Trigger: 'memory audit', 'clean memory', 'memory health', /memory-audit
Install
npx skills add FerroxLabs/wayland-core --skill ijfw-memory-auditgit clone --depth 1 https://github.com/FerroxLabs/wayland-core.git /tmp/wayland-core
mkdir -p ~/.claude/skills
cp -r /tmp/wayland-core/crates/wayland-ijfw/snapshots/ijfw-source/claude/skills/ijfw-memory-audit ~/.claude/skills/ijfw-memory-auditPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
## Execution 1. Call `ijfw_memory_status` to get counts and last-update timestamps for all tiers. 2. Scan `.ijfw/memory/` for all `.md` files. For each, note: - File name, size (lines), last modified date. - Days since last referenced (use file mtime as proxy). 3. Categorize entries: ``` ACTIVE -- referenced within 30 days STALE -- not referenced in 30-90 days ARCHIVE -- not referenced in 90+ days, or flagged as superseded ``` 4. Report: ``` MEMORY HEALTH REPORT Total entries: <N> | Total size: ~<X> lines Active: <N> | Stale: <N> | Archive candidates: <N> STALE ENTRIES (>30 days unreferenced) - <filename>: <one-line summary> [last seen: <date>] ARCHIVE CANDIDATES (>90 days or superseded) - <filename>: <one-line summary> [last seen: <date>] RECOMMENDATION Archive <N> entries to .ijfw/memory/archive/. No data is deleted. ``` 5. **Pruning question:** for each entry flagged STALE or ARCHIVE, ask "Would removing this rule cause the agent to make a mistake?" If no, archive. If yes, keep and tighten. Memory that doesn't change behavior is bloat that crowds out memory that does. 6. Ask before acting: > `Archive <N> stale entries? (y/n -- files move to .ijfw/memory/archive/, not deleted)` 6. On confirmation, move flagged files. Store audit result: > `ijfw_memory_store: memory audit on <date> -- archived <N> entries`
Details
- Skill name
ijfw-memory-audit- Repository
- FerroxLabs/wayland-core
- Path
crates/wayland-ijfw/snapshots/ijfw-source/claude/skills/ijfw-memory-audit/SKILL.md- License
- Apache-2.0
- Repo updated
- 3 November 2026
FAQ
What does the Ijfw Memory Audit skill do?
Audit and clean project memory files. Trigger: 'memory audit', 'clean memory', 'memory health', /memory-audit
How do I install the Ijfw Memory Audit skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add FerroxLabs/wayland-core --skill ijfw-memory-audit. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Ijfw Memory Audit popular?
It lives in FerroxLabs/wayland-core, which has 43 GitHub stars and 17 forks.
Related skills
Ijfw Agents Md
43FerroxLabs/wayland-core
Maintain canonical AGENTS.md (open spec). Trigger: 'agents.md', 'update AGENTS.md', or auto-fired by ijfw-team after agent generation.
Ijfw Auto Memorize
43FerroxLabs/wayland-core
Session-end auto-extraction of lessons, errors, fixes, and user feedback into structured memory. Fires at session end. Requires consent on first run.
Ijfw Commit
43FerroxLabs/wayland-core
Terse conventional commits. Trigger: commit, git commit, /ijfw-commit
Ijfw Recall
43FerroxLabs/wayland-core
Surface relevant project memory at session start or on demand. Trigger: session start, 'recall', 'remember', 'what do you know', 'context', /recall
Ijfw Team
43FerroxLabs/wayland-core
Generate project-specific agent teams during workflow Discovery. Trigger: 'set up a team', 'create agents for', or auto-triggered by ijfw-workflow deep mode after Discovery.
Client Email Coach
48harvard-lil/lawskills-hub
Triggers when a practicing attorney wants feedback on a draft email to a client, needs help improving client communication, or wants coaching on tone, clarity, or risk management in written client communications.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.