maludb-ed

Memory To Skill — Development skill for Claude Code

Development community

Claude Code plugin: turn marked sections of successful session history into repeatable skills and slash commands (/mark + /distill).

How to install Memory To Skill

This entry records only its repository, not the path inside it, so there is no exact command to give. Open maludb-ed/memory-to-skill and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Memory To Skill does

Claude Code plugin: turn marked sections of successful session history into repeatable skills and slash commands (/mark + /distill).

Alternatives in Development

  • Claude Supermemory — Persistent memory across sessions and projects using Supermemory 2.3k ★
  • /remember — Save a finding or successful pattern to persistent hunt memory 1.2k ★
  • Claude Usage — A local dashboard for tracking your Claude Code token usage, costs, and session history 864 ★

README

memory-to-skill

A Claude Code plugin that turns the sections of your sessions that actually *worked* into repeatable skills and slash commands — mark an attempt, and when it succeeds, distill it.

[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE) ![Version](https://img.shields.io/badge/version-0.1.0-blue.svg) ![Platform](https://img.shields.io/badge/platform-macOS%20%7C%20Linux%20%7C%20Windows-lightgrey.svg)


The idea

Some sessions produce a result you'll want again: a migration recipe, a debugging procedure, a deploy sequence that finally worked. Rather than hoping you remember the prompts, you delimit the good part with markers and run `/distill`. Claude re-reads that section as *evidence* — extracting the goal, keeping the working path, converting dead ends into "gotchas", generalizing project-specific details — and writes a proper skill or slash command from it.

Highlights

  • Two markdown commands, zero runtime. No hooks, no scripts, no Node.js, no dependencies. Works identically on macOS, Linux, and Windows.
  • Mark live or after the fact. /mark drops a marker into the session as you work; the identical [SKILL-START: ] string can be pasted into a saved transcript later when you realize yesterday's session had the good stuff.
  • Skill or command output. Procedures become auto-triggering skills (SKILL.md); replayable prompts become parameterized slash commands. Claude picks the right form, or you force one.
  • Project scope by default. Output lands in your project's .claude/ directory, so committing it shares the skill with your whole team. A personal flag targets ~/.claude/ instead.
  • Distills, never copies. The output is instructions for a fresh Claude — dead ends become warnings, specifics become placeholders, and the verification step that proved success comes along.

Prerequisites

| Requirement | Why | How to check