Batch knowledge ingestion from external sources (a folder, a codebase, a docs tree, a set of files). Plans the ingestion as a list of well-shaped nodes with reconciled keywords, shows the user the plan for approval, then executes idempotently. Triggered by /learn, "ingest this folder into memory", "porta questo codice…
Connect the user's Akashi second brain (local, private, verifiable) over MCP and answer from cited vault passages with signed provenance. Query it BEFORE answering anything about the user's knowledge, projects, decisions, or conventions. Triggers - akashi, vault, my notes, second brain, remember this, what did I…
Document a codebase into a Memory Crystal knowledge base with re-runnable, self-updating architecture notes. Use when asked to "document this repo", "architect notes", or to refresh existing architecture documentation in memory.
Use Dory wake once at the start of a new agent session, after context compaction, or at a real task switch to load bounded hot context with the right profile before substantive work.
Build a custom source → raw-intake adapter for Athenaeum. Use when someone wants to feed an external source (an API, an export file, a message feed, a scraper, another tool's output) into an Athenaeum knowledge base, asks "how do I write an adapter / integration for athenaeum", or wants to turn some data source into…
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.
A project-context tool for recording important lessons about bugs and failure-prone code in nearby AGENTS.md documents. These documents give coding agents repository-specific guidance.
Use this skill when Pioneer should proactively use durable memory or recalled context: decide whether memory can improve a turn, answer from remembered user/project facts, request memory tools, search/list/get stored memories, save durable preferences or project decisions, forget memories, audit or clean up memory, or…
Activate at the start of any session where memoryweb MCP tools are available. Covers filing, connecting, and retrieving knowledge through the memoryweb graph — any coding, architecture, backlog, or general work an agent is tracking for this user.
Search, inspect, and export Claude Code, Cursor, and Codex conversation history. Use when the user asks about past conversations, wants to find a previous session, needs to search chat history, wants a summary of what they worked on, or asks to resume a session. Also use when the user says "what did I work on", "find…
ALWAYS use this skill when working with agents, memory, context, persistence, or AI agent state. Use when the user mentions: 'the agent forgot', 'save this', 'remember that', 'context is lost', 'memory', 'MCP server', 'agent memory', 'persistent memory', 'session context', 'project context', 'recall', 'remember'…
Build and maintain personal knowledge bases as LLM-compiled markdown wikis, inspired by Andrej Karpathy's LLM Wiki pattern. The LLM incrementally ingests raw sources (articles, papers, repos, images) into a structured, interlinked wiki of .md files — with summaries, entity pages, concept pages, cross-references, and a…
Use Grape MCP for Codex context continuity in coding repositories. Use when a task needs repeated-turn context, omitted context restore, stale-context checks, invalidation checks, or safe continuity across branch and dirty-worktree changes.
Persistent four-layer agent memory (episodic + continuity + Hebbian + affective) plus a prospective spore layer and an on-demand crystallized-pattern tier, via anneal-memory. Use in any project wired for anneal-memory — an ANNEALMEMORYDB env var, an anneal://continuity MCP resource, or memory instructions referencing…
Ingest meetings, articles, docs, and conversations into the brain. Updates existing pages with new info, creates pages for new entities, maintains cross-references.
Compile personal data (journals, notes, messages, whatever) into a personal knowledge wiki. Ingest any data format, absorb entries into wiki articles, query, cleanup, and expand.
Use when a repository needs one lightweight repository memory profile that evolves with the codebase to reduce drift, prevent structural mistakes, and keep current repository truth plus durable working context explicit. Trigger for requests to refresh current-state or architecture docs from live code, classify or…
Extract personal facts and build a "Who Am I?" profile from your ChatGPT conversation history using local LLM processing. All data stays on your machine.
Persist and retrieve Claude Code work logs and reusable experiences under the current project's .worklog directory by default. Use when the user wants to record a coding session, source-reading session, debug session, or mixed session; when a task mixes development, reading, and debugging; when adding, deprecating, or…
Build and reason about projects using Interpretable Context Methodology (ICM) — a filesystem-based way to structure AI work using numbered folders and markdown files (CLAUDE.md, CONTEXT.md) instead of code-heavy agent frameworks. Use this skill whenever the user wants to scaffold a new ICM workspace, set up a…
★not rated 11 2mo agoA164 tokens
originalMIT
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: