mcpField
G
groove-utilities-memory-graduate

groove-utilities-memory-graduate

github.com/andreadellacorteAgent workflows6510 installsUpdated 14w ago
Repository

About groove-utilities-memory-graduate

A skill for promoting stable workflow insights from Groove memory files into `AGENTS.md` for future sessions. It is intended for agents maintaining project guidance and requires confirmation of the exact text before writing.

Key features

  1. 01Append insights to Graduated Learnings
  2. 02Create the section when needed
  3. 03Confirm exact text before writing
  4. 04Mark the source entry as graduated
  5. 05Skip exact duplicates

Use cases

  1. 01Preserve recurring workflow lessons
  2. 02Select an entry from learned files
  3. 03Avoid adding an insight twice

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/andreadellacorte/groove --skill groove-utilities-memory-graduate

After installing, type/groove-utilities-memory-graduatein Claude Code to confirm it loaded.

Details

From the project README

groove-utilities-memory-graduate

Promote a stable workflow insight from .groove/memory/learned/ into AGENTS.md as a permanent constraint — visible to every agent session without needing to run prime.

Use $ARGUMENTS as the topic or insight text if provided.

Outcome

The lesson is appended to a <!-- groove:learned:start --> / <!-- groove:learned:end --> section in AGENTS.md, making it permanently visible to all future sessions.

Acceptance Criteria

  • Insight is appended to the ## Graduated Learnings section in AGENTS.md
  • Section is created if it does not exist
  • User confirms the exact text before writing
  • Source learned/<topic>.md entry is marked as graduated (not deleted)

Steps

  1. Memory path is always .groove/memory/
  2. If $ARGUMENTS names a topic, read .groove/memory/learned/<topic>.md and show its entries. Otherwise, list all *.md files in .groove/memory/learned/ and ask which topic to graduate from.
  3. Show the file contents; ask: "Which entry should be graduated? (paste or describe it)"
  4. Show the exact text that will be written to AGENTS.md; ask: "Confirm? (yes / edit / skip)"
  5. If confirmed: write to AGENTS.md (see section management below)
  6. Mark the entry in the learned file by appending [graduated YYYY-MM-DD] inline after the bullet
  7. Report: "Lesson graduated to AGENTS.md → ## Graduated Learnings"

Section management in AGENTS.md

Look for a <!-- groove:learned:start --> / <!-- groove:learned:end --> block:

  • If the block exists: append the new insight as a bullet under ## Graduated Learnings inside the block
  • If the block does not exist: append the following to the end of AGENTS.md:
<!-- groove:learned:start -->
## Graduated Learnings

Stable workflow insights promoted from `.groove/memory/learned/`. These apply to every session.

- <insight text>
<!-- groove:learned:end -->

Each entry is a single bullet: - <insight text> *(from learned/<topic>.md, graduated YYYY-MM-DD)*

Constraints

  • Never graduate without explicit user confirmation of the exact text
  • Never delete the source entry from learned/<topic>.md — mark it as graduated with [graduated YYYY-MM-DD] inline; the full context stays in the file
  • The <!-- groove:learned:* --> section is user-owned — groove update will not overwrite it
  • Keep graduated lessons concise — one actionable sentence per bullet; ask user to trim if longer
  • If AGENTS.md does not exist: create it with just the graduated learnings section
  • If the same insight is already present in the block (exact match): skip and report "Already graduated."

Comments

Markdown supported