memory-management-working-memory-format-claudemd
Sub-skill of memory-management: Working Memory Format (AGENTS.md).
Best use case
memory-management-working-memory-format-claudemd is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of memory-management: Working Memory Format (AGENTS.md).
Teams using memory-management-working-memory-format-claudemd should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/working-memory-format-claudemd/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How memory-management-working-memory-format-claudemd Compares
| Feature / Agent | memory-management-working-memory-format-claudemd | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of memory-management: Working Memory Format (AGENTS.md).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Working Memory Format (AGENTS.md) ## Working Memory Format (AGENTS.md) Use tables for compactness. Target ~50-80 lines total. ```markdown # Memory
Related Skills
memory-bridge-operations
Operate and recover the Hermes-to-repo memory bridge: drift checks, quality gate, bridge commits, push verification, and stash recovery when pre-bridge scripts fail after generating outputs.
hermes-memory-bridge
Architecture and scripts for syncing Hermes memory into git-tracked .claude/memory/ so all machines get context via git pull. Covers quality gate, drift detection, topic mirroring, and cron automation.
verify-Codex-run-commit-vs-working-tree-before-closing
After a Codex implementation run, verify the claimed file set against the actual commit and working tree before treating the issue as fully complete.
multi-format-transaction-parser
Parse and consolidate financial transaction data across multiple CSV formats and years
multi-format-csv-parser-with-deduplication
Parse brokerage CSV exports that exist in multiple formats with overlapping data across files
multi-format-csv-detection-and-deduplication
Detect and handle multiple CSV format versions from the same data source; deduplicate records across format variants
cron-job-management
Patterns for creating, testing, debugging, and maintaining cron-driven automation in workspace-hub, including log strategy, failure analysis, and safe git-aware job design.
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
data-management
Comprehensive DataFrame loading, filtering, transformation, and data pipeline management from Excel, CSV, and multiple sources with YAML-driven configuration.
memory-bridge-operation
Manage the Hermes ↔ repo memory sync system — bridge, quality gate, compaction, health checks, and cron
memory-bridge-commit-fallbacks
Fallback procedures when the Hermes ↔ Codex memory bridge writes .Codex/memory outputs but the internal git commit/push path fails because of dirty, stale, or broken submodule state.
agent-memory-bridge
Bidirectional sync between Hermes memory and Codex auto-memory, with licensed machine bootstrap. Use when context parity across agents is needed.