How do I install the RAG Remember skill?

Run npx skillmds@latest add zhaixin244-wq/rag-remember in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is RAG Remember safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with RAG Remember?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is RAG Remember free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published RAG Remember?

zhaixin244-wq (@zhaixin244-wq) published this skill. Their other Agent Skills are listed on their SkillMD profile.

RAG Remember by zhaixin244-wq — Agent Skill

Name: RAG Remember
Author: zhaixin244-wq

File contents

RAG Remember — Store to Personal Knowledge Graph

Store a specific fact, decision, or observation into your personal LightRAG knowledge graph. Use mid-session when something worth remembering comes up.

Formatting rules

Format each entry as:

[TYPE] Title — YYYY-MM-DD

What: Brief description of the fact or decision
Why: The reasoning or context behind it
Files: Relevant file paths (if applicable)

Entry types

Type	Use for
`DECISION`	Architecture choices, tool selections, approach decisions
`FEEDBACK`	User corrections, preferences, "do this / don't do that"
`CONFIG`	Server settings, env vars, ports, credentials (NO actual secrets)
`PROJECT`	Project status, goals, deadlines, stakeholders
`PERSON`	People, roles, contact preferences, working styles
`REFERENCE`	URLs, docs, external resources, where to find things
`INSIGHT`	Debugging lessons, performance findings, non-obvious learnings

How to store

node -e "
const BASE = process.env.LIGHTRAG_SERVER_URL || 'http://YOUR_LIGHTRAG_HOST:YOUR_PERSONAL_PORT';
(async () => {
  const auth = await fetch(BASE + '/auth-status').then(r => r.json());
  const token = auth.access_token;
  const res = await fetch(BASE + '/documents/text', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'Authorization': 'Bearer ' + token
    },
    body: JSON.stringify({
      file_source: '[TYPE] Title — YYYY-MM-DD',
      text: 'Full content here with What/Why/Files structure'
    })
  });
  const data = await res.json();
  console.log('Status:', res.status);
})();
"

After inserting

Confirm to the user: "Stored: [TYPE] Title"
Do NOT dump the raw API response
If the insert fails, tell the user and suggest trying again

What NOT to store

Ephemeral task details — current conversation context, in-progress work steps
Code from the codebase — it's already in the repo; store the decision, not the code
Duplicates — query first if unsure whether something is already stored
Credentials or secrets — never store API keys, passwords, tokens
Git history — use git log / git blame instead

Infrastructure

Server: YOUR_LIGHTRAG_HOST:YOUR_PERSONAL_PORT
Auth: Bearer token from /auth-status (guest/disabled mode)
Env var: LIGHTRAG_SERVER_URL

---name: rag-rememberdescription: Store a fact, decision, or observation into the personal LightRAG knowledge graph immediately---# RAG Remember — Store to Personal Knowledge GraphStore a specific fact, decision, or observation into your personal LightRAG knowledge graph. Use mid-session when something worth remembering comes up.## Formatting rulesFormat each entry as:```[TYPE] Title — YYYY-MM-DDWhat: Brief description of the fact or decisionWhy: The reasoning or context behind itFiles: Relevant file paths (if applicable)```### Entry types| Type | Use for ||------|---------|| `DECISION` | Architecture choices, tool selections, approach decisions || `FEEDBACK` | User corrections, preferences, "do this / don't do that" || `CONFIG` | Server settings, env vars, ports, credentials (NO actual secrets) || `PROJECT` | Project status, goals, deadlines, stakeholders || `PERSON` | People, roles, contact preferences, working styles || `REFERENCE` | URLs, docs, external resources, where to find things || `INSIGHT` | Debugging lessons, performance findings, non-obvious learnings |## How to store```bashnode -e "const BASE = process.env.LIGHTRAG_SERVER_URL || 'http://YOUR_LIGHTRAG_HOST:YOUR_PERSONAL_PORT';(async () => { const auth = await fetch(BASE + '/auth-status').then(r => r.json()); const token = auth.access_token; const res = await fetch(BASE + '/documents/text', { method: 'POST', headers: { 'Content-Type': 'application/json', 'Authorization': 'Bearer ' + token }, body: JSON.stringify({ file_source: '[TYPE] Title — YYYY-MM-DD', text: 'Full content here with What/Why/Files structure' }) }); const data = await res.json(); console.log('Status:', res.status);})();"```## After inserting- Confirm to the user: "Stored: [TYPE] Title"- Do NOT dump the raw API response- If the insert fails, tell the user and suggest trying again## What NOT to store- **Ephemeral task details** — current conversation context, in-progress work steps- **Code from the codebase** — it's already in the repo; store the *decision*, not the code- **Duplicates** — query first if unsure whether something is already stored- **Credentials or secrets** — never store API keys, passwords, tokens- **Git history** — use `git log` / `git blame` instead## Infrastructure- **Server**: `YOUR_LIGHTRAG_HOST:YOUR_PERSONAL_PORT`- **Auth**: Bearer token from `/auth-status` (guest/disabled mode)- **Env var**: `LIGHTRAG_SERVER_URL`

Frequently asked questions

RAG Remember