Skip to main content

← All sources

Claude-Mem skills

Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex,.... 20 skills. skills-hub.ai mirrors 35 skills from Claude-Mem daily, every skill links back to its upstream GitHub source. Install with one command across Claude Code, Cursor, Codex, Windsurf, and any MCP-compatible tool.

Upstream: github.com/thedotmack/claude-mem

Installing a Claude-Mem skill

Pick a skill below, then run the install command for your AI coding tool. The skills-hub CLI writes the SKILL.md to the right directory and tracks the install in .skills.json so your team gets reproducible installs.

# Install a Claude-Mem skill
npx @skills-hub-ai/cli install <skill-slug>

# Browse all Claude-Mem skills via API
curl https://skills-hub.ai/api/v1/skills?source=claude-mem

# Browse all sources
open https://skills-hub.ai/sources

Top Claude-Mem skills

See all →

The most-installed skills from Claude-Mem, ranked by adoption.

  1. 01handoff

    13 installs

    Generate a HANDOFF.md that captures goal, current state, files touched, failed attempts, and next steps — so a fresh Claude session can continue exactly where this one left off. Use when sessions are getting long, Claude keeps retrying the same broken solution, or the user wants to step away and resume later.

    Buildfrom Claude-Mem
  2. 02learn-codebase

    7 installs

    Prime a codebase by reading every source file in full. Use when starting work on a new or unfamiliar project, or when the user asks to "learn the codebase", "read the codebase", "prime", or "get up to speed".

    Buildfrom Claude-Mem
  3. 03cloud-sync

    2 installs

    Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.

    Buildfrom Claude-Mem
  4. 04claude-mem-install

    2 installs

    Use this when setting up claude-mem on Grok Bot: local worker plus CMEM Pro observer (default), optional host-login observer, or remote cmem.ai. No Cursor required.

    Buildfrom Claude-Mem
  5. 05mode-creator

    2 installs

    Interactively create, install, activate, and verify custom claude-mem modes, including domain-specific observation types, concept tags, optional Telegram alerts, bot setup, worker restart, and startup-context verification. Use this whenever someone asks to customize what claude-mem remembers, create or change a mode, track domain-specific notes, add observation types or tags, or send Telegram notifications for particular memories—even if they do not use the word "mode."

    Buildfrom Claude-Mem
  6. 06version-bump

    1 installs

    Maintainer release workflow for the thedotmack/claude-mem repository only. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. npm publishing is done by the tag-triggered GitHub Actions workflow through npm trusted publishing. Does not apply to any other repository or npm package.

    Buildfrom Claude-Mem
  7. 07mem-search

    1 installs

    Smart search (default). Search claude-mem's persistent cross-session memory database in three steps: search, timeline, then selected get_observations. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.

    Buildfrom Claude-Mem
  8. 08pathfinder

    1 installs

    Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture. Use when asked to "find the ideal path," unify duplicated systems, or audit architecture before a refactor. Emits a proposed unified flowchart plus per-system /make-plan prompts.

    Buildfrom Claude-Mem
  9. 09Claude-Mem OpenClaw Plugin — Setup Guide

    1 installs

    This guide walks through setting up the claude-mem plugin on an OpenClaw gateway. By the end, your agents will have persistent memory across sessions via system prompt context injection, and optionally a real-time observation feed streaming to a messaging channel.

    Buildfrom Claude-Mem
  10. 10screenpipe

    Search screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.

    Buildfrom Claude-Mem
  11. 11request-progress

    Group recent conversations into overall requests, review each one's progress from memory, sort each into one of the owner's focus areas, and write the build story, so My Work shows progress meters, shipping velocity and learned working preferences. Use when asked to "group requests", "group by overall request", "review request progress", "refresh progress", "build story", "shipping velocity", or "how do I like to work with agents".

    Buildfrom Claude-Mem
  12. 12release

    Fully automate a release with version-bump and childhood.

    Buildfrom Claude-Mem
  13. 13build

    Fully automate a coding task with make-plan, do, and babysit.

    Buildfrom Claude-Mem
  14. 14host-observer

    Use this when fulfilling claude-mem observer jobs on Grok Bot: reply only skip_summary or one full observation XML, never prose.

    Buildfrom Claude-Mem
  15. 15make-plan

    Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.

    Buildfrom Claude-Mem
  16. 16weekly-digests

    Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests", "week-by-week story", "serial timeline", or "narrative chapters" of a project's history.

    Buildfrom Claude-Mem
  17. 17do

    Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.

    Buildfrom Claude-Mem
  18. 18oh-my-issues

    Cluster a GitHub issue backlog by root cause into a small set of plan-master issues, redirect children with a standardized comment, and bundle architectural-fix PRs that close clusters atomically. Use when an issue tracker has accumulated dozens of reports that share underlying defects, when asked to triage / consolidate / cluster / dedupe issues, when asked to build a plan series or roadmap from open issues, or when routing a new incoming bug into an existing plan.

    Buildfrom Claude-Mem
  19. 19what-the

    What the? Use when the user wants a plain-English breakdown of something technical — the who, what, where, why, and when.

    Buildfrom Claude-Mem
  20. 20standup

    Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.

    Buildfrom Claude-Mem
  21. 21knowledge-agent

    Build and query AI-powered knowledge bases from claude-mem observations. Use when users want to create focused "brains" from their observation history, ask questions about past work patterns, or compile expertise on specific topics.

    Buildfrom Claude-Mem
  22. 22babysit

    Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.

    Buildfrom Claude-Mem
  23. 23timeline-report

    Generate a "Journey Into [Project]" narrative report analyzing a project's entire development history from claude-mem's timeline. Use when asked for a timeline report, project history analysis, development journey, or full project report.

    Buildfrom Claude-Mem
  24. 24Agent Cost Report

    Believable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.

    Buildfrom Claude-Mem

About this source

skills-hub.ai mirrors skills from 300+ official GitHub repositories every day. Each imported skill is parsed from a SKILL.md file in the source repo, gets a security scan and quality score on import, and links back to its upstream source of truth.

Last sync: Nov 17, 2026, 6:37 PM (success).

Claude-Mem skills, frequently asked

What are Claude-Mem skills?

Claude-Mem skills are AI coding skills published by Claude-Mem (Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex,.... 20 skills.) and mirrored daily on skills-hub.ai. They are SKILL.md files that follow the open Agent Skills standard, so they work in Claude Code, Cursor, Codex CLI, Windsurf, Copilot, and any MCP-compatible tool.

How many Claude-Mem skills are available?

skills-hub.ai indexes 35 skills from Claude-Mem, synced daily from the upstream GitHub repository (https://github.com/thedotmack/claude-mem).

How do I install a Claude-Mem skill?

Run `npx @skills-hub-ai/cli install <skill-slug>` in your project. The CLI writes the SKILL.md to the right directory for your AI tool and adds it to your `.skills.json` lockfile so your team gets the same skills at the same versions.

Are these official Claude-Mem skills?

Yes. Every skill from this source is mirrored from Claude-Mem's own GitHub repository (https://github.com/thedotmack/claude-mem). Each skill page links back to the upstream source of truth, so you can verify the original.