Adoption

Agent Skills are supported by leading AI development tools.

VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory

andreadellacorte/groove-utilities-memory-mistakes

Name: groove-utilities-memory-mistakes
Author: andreadellacorte

skills/groove-utilities-memory-mistakes/SKILL.md

npx skillsauth add andreadellacorte/groove groove-utilities-memory-mistakes

Clean

TrivyContainer and dependency vulnerability scanner

Clean

SemgrepStatic code analysis for vulnerabilities

Clean

mcp-scan (Snyk)Model Context Protocol security validation

Skipped

Snyk (dep)Open source security scanning

Skipped

Socket.devSupply chain security analysis

Skipped

VirusTotalMulti-engine malware detection

Skipped

CrowdStrikeAdvanced threat intelligence

Skipped

OSV-ScannerOpen Source Vulnerability database check

Skipped

OWASP Dep-Check

groove-utilities-memory-mistakes

Use $ARGUMENTS as the mistake description if provided (e.g. --list to show open incidents only).

Outcome

The workflow mistake is logged, its root cause is fixed in the relevant memory or learned file, and the lesson is graduated to .groove/memory/learned/<topic>.md. The incident is closed.

Acceptance Criteria

Incident is recorded with root cause and fix
Permanent fix applied to .groove/memory/learned/<topic>.md
Incident marked resolved

Task backend

Read tasks.backend from .groove/index.md. Incidents are tracked as tasks in the configured backend. If no task backend is configured (tasks.backend: none), tell the user to run /groove-utilities-task-install first.

Incidents are stored as bugs under a shared "Groove Memory" milestone → "Mistakes" epic.

Ensure parent hierarchy

Before any operation, resolve or create the parent epic:

Find or create the Groove Memory milestone:
- beans list -t milestone --search "Groove Memory" -q — if non-empty, use first ID; otherwise beans create "Groove Memory" -t milestone
Find or create the Mistakes epic under that milestone:
- beans list -t epic --parent <milestone-id> --search "Mistakes" -q — if non-empty, use first ID; otherwise beans create "Mistakes" -t epic --parent <milestone-id>

`--list`

Resolve <parent-id>
beans list --parent <parent-id> -t bug -s in-progress
Display as numbered list: 1. [<id>] <title>
If empty: print "No open incidents."

Log and resolve an incident

Resolve <parent-id>
Get description from $ARGUMENTS or ask: "What mistake did I make?"
Ask: "Root cause — why did it happen?" (propose from context; user confirms)
Ask: "What fix should be applied?" (propose; user confirms)
beans create "<description>" -t bug --parent <parent-id> -s in-progress
Apply the fix immediately (edit the relevant file)
Ask: "Which learned topic? (e.g. anti-patterns, tools)" — suggest based on root cause
Append lesson to .groove/memory/learned/<topic>.md under ## YYYY-MM-DD heading
beans update <id> -s completed
Report: "Incident resolved → learned/<topic>.md"

Constraints

Read tasks.backend from .groove/index.md; memory path is always .groove/memory/
Requires a configured task backend — if tasks.backend: none, prompt user to install one
Never auto-create incidents without user confirmation
Root cause is required before resolving — do not skip the audit step
Parent hierarchy is idempotent — always check before creating
If the fix targets a skills/ file: note that skills/ is managed by groove:update; redirect fix to learned/anti-patterns.md

andreadellacorte/groove-utilities-memory-mistakes

skills/groove-utilities-memory-mistakes/SKILL.md

Log a workflow mistake, fix its root cause, and graduate the lesson to learned memory. Use when the agent makes an error you want to prevent recurring.

4 stars

data-ai

Updated Apr 24, 2026

$ install --global

skillsauth

npx skillsauth add andreadellacorte/groove groove-utilities-memory-mistakes

Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.

Security Scan Results

3 of 9 scanners reported clean

Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.

Scanners Passed

Scanners in report

Clean

TrivyContainer and dependency vulnerability scanner

95%

Clean

SemgrepStatic code analysis for vulnerabilities

95%

Clean

mcp-scan (Snyk)Model Context Protocol security validation

95%

Skipped

Snyk (dep)Open source security scanning

50%

Skipped

Socket.devSupply chain security analysis

50%

Skipped

VirusTotalMulti-engine malware detection

50%

Skipped

CrowdStrikeAdvanced threat intelligence

50%

Skipped

OSV-ScannerOpen Source Vulnerability database check

50%

Skipped

OWASP Dep-Check

50%

Last scanned: Apr 24, 2026, 8:33 PM0.4s1 file scanned

SKILL.md

name:: groove-utilities-memory-mistakes
description:: Log a workflow mistake, fix its root cause, and graduate the lesson to learned memory. Use when the agent makes an error you want to prevent recurring.
license:: MIT
allowed-tools:: Read Write Edit Glob Grep Bash(git:*) Bash(beans:*) AskUserQuestion
author:: andreadellacorte

groove-utilities-memory-mistakes

Use $ARGUMENTS as the mistake description if provided (e.g. --list to show open incidents only).

Outcome

The workflow mistake is logged, its root cause is fixed in the relevant memory or learned file, and the lesson is graduated to .groove/memory/learned/<topic>.md. The incident is closed.

Acceptance Criteria

Incident is recorded with root cause and fix
Permanent fix applied to .groove/memory/learned/<topic>.md
Incident marked resolved

Task backend

Incidents are stored as bugs under a shared "Groove Memory" milestone → "Mistakes" epic.

Ensure parent hierarchy

Before any operation, resolve or create the parent epic:

Find or create the Groove Memory milestone:
- beans list -t milestone --search "Groove Memory" -q — if non-empty, use first ID; otherwise beans create "Groove Memory" -t milestone
Find or create the Mistakes epic under that milestone:
- beans list -t epic --parent <milestone-id> --search "Mistakes" -q — if non-empty, use first ID; otherwise beans create "Mistakes" -t epic --parent <milestone-id>

`--list`

Resolve <parent-id>
beans list --parent <parent-id> -t bug -s in-progress
Display as numbered list: 1. [<id>] <title>
If empty: print "No open incidents."

Log and resolve an incident

Resolve <parent-id>
Get description from $ARGUMENTS or ask: "What mistake did I make?"
Ask: "Root cause — why did it happen?" (propose from context; user confirms)
Ask: "What fix should be applied?" (propose; user confirms)
beans create "<description>" -t bug --parent <parent-id> -s in-progress
Apply the fix immediately (edit the relevant file)
Ask: "Which learned topic? (e.g. anti-patterns, tools)" — suggest based on root cause
Append lesson to .groove/memory/learned/<topic>.md under ## YYYY-MM-DD heading
beans update <id> -s completed
Report: "Incident resolved → learned/<topic>.md"

Constraints

Read tasks.backend from .groove/index.md; memory path is always .groove/memory/
Requires a configured task backend — if tasks.backend: none, prompt user to install one
Never auto-create incidents without user confirmation
Root cause is required before resolving — do not skip the audit step
Parent hierarchy is idempotent — always check before creating
If the fix targets a skills/ file: note that skills/ is managed by groove:update; redirect fix to learned/anti-patterns.md

Related Skills

andreadellacorte/groove-utilities-stats

testing

VerifiedTrustedCommunity

Quantified compound-loop dashboard: lessons captured vs graduated, adherence streaks, and task velocity. Use to see whether the workflow is actually compounding.

5SKILL.mdUpdated Jun 5, 2026

andreadellacorte/groove-utilities-stats