使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/gentleman-programming/engram --skill engram-memory-protocol開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
When to Use
Use this skill when:
- Making architecture or implementation decisions
- Fixing bugs with non-obvious root causes
- Discovering patterns, gotchas, or user preferences
- Closing a session or after compaction
Save Rules
Call mem_save immediately after:
- decision
- bugfix
- pattern/discovery
- config/preference changes
Use structured content:
- What
- Why
- Where
- Learned
Use stable topic_key for evolving topics.
Search Rules
- On recall requests:
mem_contextfirst, thenmem_search. - Before similar work: run proactive
mem_search. - On first message: if user references the project, a feature, or a problem, call
mem_searchwith their keywords before responding.
Session Close Rules
Before saying done/listo:
- Call
mem_session_summary. - Include goal, discoveries, accomplished, next steps, relevant files.
After compaction:
- Save summary first.
- Recover context.
- Continue work.
Delivery Guarantee
Memory operations are internal bookkeeping, never the user-facing answer. Complete required memory work before composing the completed-task reply; send the complete answer as the final message of the turn with no later tool calls. If memory work fails or needs follow-up, still send the answer.


