Writes, audits, and continuously evolves project memory across the whole Claude Code memory system — CLAUDE.md (project ./CLAUDE.md, personal /.claude/CLAUDE.md, local ./CLAUDE.local.md), AGENTS.md, .claude/rules, and Auto Memory. Use when the user wants to create, generate, review, audit, slim down, or evolve a…
Analyzes development sessions to extract learnings from corrections, successful patterns, and revealed preferences. Use when the user wants to reflect on a coding session, extract lessons learned, or update project knowledge. Triggered by /reflect command or phrases like "reflect on this session", "what did we learn…
Deep-mines the last 50 sessions of a project to find recurring corrections, repeated instructions, and reverted changes. Writes proposed CLAUDE.md rules to CLAUDE.md.undrift — review and merge manually. Run when patterns keep repeating or after /undrift-check flags a project as needing attention.
End-of-session self-improvement. Review the session for user corrections, steering, and reusable discoveries, then route them into global or project CLAUDE.md, auto-memory, GSD planning docs, or (rarely) a skill, with a compact preview and per-item approval before anything is written. Use when the user invokes…
A project-tracking system that connects multiple Git repositories to an Obsidian vault through Markdown notes and commands. It keeps architecture, progress, current focus, and recent changes in one place.
Initialize Obsidian second brain vault structure by creating comprehensive CLAUDE.md context maps across PARA modules (Projects, Areas, Resources, Archives). Use when working with Obsidian vaults to establish AI-readable context, when user requests vault initialization, knowledge base mapping, or says "/init-vault".…
Explore, organize, and extract knowledge using WKSM MCP tools. Use for filesystem exploration, file organization, document extraction, vault generation, and knowledge base management.
Use this skill whenever the user wants to design, build, set up, scaffold, structure, or improve the agentic framework of a Claude project — meaning the architecture of memory (CLAUDE.md, MEMORY.md), subagents, skills, hooks, and MCP connections. Triggers include phrases like "montar el framework del proyecto"…
Personal conversation distillation system. Records, analyzes, and distills your AI conversations to automatically discover and generate personalized skills from your real behavior patterns. Contains three sub-commands: - /self-distill record: Script directly parses JSONL to archive the current conversation — zero…
Use when user says "wrap up", "close session", "end session", "wrap things up", "close out this task", or invokes /wrap-up — runs end-of-session checklist for shipping, memory, and self-improvement.
Migrate a bloated monolithic memory.md (or any large knowledge file) into a slim INDEX + per-topic files pattern. Cuts session-start token cost by 93% by lazy-loading topic content only when relevant. Use when an agent's memory.md has grown above 10KB, when a CLAUDE.md is bloating session context, when a multi-agent…
Imports an existing Claude.ai project folder, Cowork project, or any folder of past Claude work into the user's Obsidian vault as structured PARA notes. Use this skill when the user runs /migrate-claude-project [path], says "import my Claude project", "migrate this folder into my vault", "seed my vault from old Claude…
Operate an LLM-maintained personal knowledge base (an "LLM Wiki") — a persistent, interlinked markdown wiki that the LLM builds and maintains from raw sources, used for study, research, and reading notes. Use this whenever the user wants to ingest sources into their knowledge base — one at a time or in a batch via…
A persistent memory service for AI coding assistants, storing project rules, architecture decisions, bug fixes, and other knowledge across sessions. It uses a database to search stored information by meaning.
Bootstrap a repository-level "super harness" for long-running agent and human collaboration, so durable team knowledge, experiment progress, and verification evidence live in the repo rather than individual chat history. Use when initializing or normalizing the harness structure in a new or messy repository…
Persistent continuity management for AI agents. Ensures continuity across sessions, prevents data loss from compaction, and maintains reliable audit trails. Logs all human interactions and agent responses for complete conversational continuity. Works with base OpenClaw — no external dependencies. Continuity data stays…
Use the ASIMOV CLI to join the user's personal knowledge (such as mail, messages, documents) and public data (such as from social media) into a unified intelligence layer and knowledge base. Use this skill when the user mentions ASIMOV, wants their own data in the task, or needs a data source an ASIMOV module handles.
Set up, maintain, or operate a personal wiki vault (second brain). Three branches: Setup, Maintain, Operate. Trigger for: "set up my second brain", "lint my wiki", "schedule my vault operator", "check wiki health", "operate my second brain", or any vault bootstrap, maintenance, or operator task — even phrased casually.
A handoff and return workflow for continuing work with an AI agent after hours or days away. It records task status, decisions, next steps, unanswered questions, and gaps in understanding.
Preserve the minimum sufficient working state required for another coding agent to continue a task without repeating repository discovery, reconstructing prior decisions, or losing task-specific constraints.
Initialize, plan, run, inspect, and review resumable Ralph-style autonomous implementation loops with sequential chunks, persistent scratchpad memory, manifests, and idempotent post-sprint hooks. Use for .ralph orchestration or similar long-running coding-agent sprint systems.
Use when deciding where knowledge goes or reading/writing durable docs: AGENTS.md, .context/, KB, docs/, and work directories.
★not rated 2
changed todayA32 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: