$npx -y skills add sickn33/agentic-awesome-skills --skill agent-memoryA hybrid memory system that provides persistent, searchable knowledge management for AI agents.
| 1 | # agentMemory Skill |
| 2 | ## When to Use |
| 3 | |
| 4 | Use this skill when you need a hybrid memory system that provides persistent, searchable knowledge management for AI agents. |
| 5 | |
| 6 | |
| 7 | This skill extends your capabilities by providing a persistent, searchable memory bank that automatically syncs with project documentation. |
| 8 | |
| 9 | ## Prerequisites |
| 10 | |
| 11 | - Node.js installed |
| 12 | - Check if `agentMemory` is already installed in the project: |
| 13 | ```bash |
| 14 | ls -la .agentMemory |
| 15 | ``` |
| 16 | |
| 17 | ## Setup |
| 18 | |
| 19 | 1. **Install Dependencies**: |
| 20 | ```bash |
| 21 | npm install |
| 22 | ``` |
| 23 | |
| 24 | 2. **Build the Project**: |
| 25 | ```bash |
| 26 | npm run compile |
| 27 | ``` |
| 28 | |
| 29 | 3. **Start the Memory Server**: |
| 30 | You need to run the MCP server to interact with the memory bank. |
| 31 | ```bash |
| 32 | npm run start-server <project_id> <absolute_path_to_workspace> |
| 33 | ``` |
| 34 | *Note: This skill typically runs as a background process or via an mcp-server configuration. ensuring it is running is key.* |
| 35 | |
| 36 | ## Capabilities (MCP Tools) |
| 37 | |
| 38 | Once the server is running, you can use these tools: |
| 39 | |
| 40 | ### `memory_search` |
| 41 | Search for memories by query, type, or tags. |
| 42 | - **Args**: `query` (string), `type?` (string), `tags?` (string[]) |
| 43 | - **Usage**: "Find all authentication patterns" -> `memory_search({ query: "authentication", type: "pattern" })` |
| 44 | |
| 45 | ### `memory_write` |
| 46 | Record new knowledge or decisions. |
| 47 | - **Args**: `key` (string), `type` (string), `content` (string), `tags?` (string[]) |
| 48 | - **Usage**: "Save this architecture decision" -> `memory_write({ key: "auth-v1", type: "decision", content: "..." })` |
| 49 | |
| 50 | ### `memory_read` |
| 51 | Retrieve specific memory content by key. |
| 52 | - **Args**: `key` (string) |
| 53 | - **Usage**: "Get the auth design" -> `memory_read({ key: "auth-v1" })` |
| 54 | |
| 55 | ### `memory_stats` |
| 56 | View analytics on memory usage. |
| 57 | - **Usage**: "Show memory statistics" -> `memory_stats({})` |
| 58 | |
| 59 | ## Workflow |
| 60 | |
| 61 | 1. **Initialization**: The first time you run this in a project, it may attempt to import existing markdown memory banks from `.kilocode/`, `.clinerules/`, or `.roo/`. |
| 62 | 2. **Development Loop**: |
| 63 | - **Before Task**: Search memory for relevant context. |
| 64 | - **During Task**: Use read/search to answer questions. |
| 65 | - **After Task**: Write new findings to memory. |
| 66 | 3. **Sync**: Your writes are automatically synced to standard markdown files in the project. |
| 67 | |
| 68 | ## Limitations |
| 69 | |
| 70 | - Use this skill only when the task clearly matches its upstream source and local project context. |
| 71 | - Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes. |
| 72 | - Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions. |