dev
claudecodexreddb.io dev plugin — engineering skills for code agents (autonomous /afk loop, triage, tdd, diagnose, graph-aware codebase understanding, wiki, …)
54 skills · 3 agents · 1 MCP server
reddb.io memory plugin — governed operational memory for code agents on top of dev: markdown notes, RedDB graph memory, governed recall, context packs, claim checks, readiness, lifecycle hooks, MCP/HTTP surfaces, Workbench diagnostics, and Skill telemetry.
Plugin memory from marketplace red-skills in reddb-io/red-skills. Commands read from the repo's manifest — 6 days ago.
This plugin runs code on your machine — it starts local MCP servers. The exact commands are listed below; read them before installing.
context-statusReport the project context stack posture without mutating anything. Use when checking whether agent rules, domain docs, ADRs, Memory graph/telemetry, and LLM Wiki are ready before a large task or self-improvement loop.
doctorInspect and maintain the memory graph — list stale nodes (long-unaccessed and never recalled) and, only after explicit confirmation, prune them. Use when the user says "memory doctor", "clean up memory", "what's stale in memory", "prune old memory", or wants a health check of the graph. Graph mode o
exportExport the memory graph to a self-contained, navigable bundle — graph.json (data), graph.html (an interactive node-link view that opens straight from disk), and audit.md (a health summary). Use when the user says "export memory", "visualize the memory graph", "show me the graph", "dump the memory gr
extractExtract durable facts from a transcript into the Memory graph through the configured AI provider. Use when the user wants to preserve decisions, gotchas, root causes, or reasoning traces from a conversation or log. Graph mode only; requires `provider` in the `plugins.memory` block of `.red/config.ya
healthReport Memory plugin operational health. Use before memory self-improvement, CI checks, or large agent runs to verify initialization, graph mode, freshness, Skill telemetry, ranked proposal candidates, and pending proposal files without mutating anything.
improve-skillsGenerate approval-gated Skill improvement proposals from Memory Skill telemetry. Use when repeated failures suggest a skill should be patched, but direct self-modification would be unsafe.
ingestWalk a repo (or a subtree) and populate the memory graph from its code and markdown — symbols, files, headings, concepts, and the edges between them. Use when the user says "index this repo", "ingest the codebase into memory", "/memory:ingest …", or when you want recall to know about the project's s
initOne-time setup wizard for the memory plugin. Asks what storage to use and writes the per-project memory config. Two modes ship today — markdown-only (plain notes, no engine) and graph (governed operational memory over a per-project RedDB store). Hooks are optional in graph mode; MCP/read surfaces co
recallSearch the project's configured memory surface and return governed context ranked by relevance. Use when the user asks "what do we know about …", "did we decide …", "have we seen this before", "/memory:recall …", or when you want past decisions/gotchas before acting. Requires `memory init` to have r
skills-statusDiagnose Skill telemetry status and recent Skill usage events. Use when checking whether self-improvement telemetry is enabled, whether skills are being observed, or before running the report-only Skill curator. Graph mode with `--skill-telemetry` provides full output; all other states explain what
storeSave one durable work fact to the project's configured memory surface. Use when the user says "remember this", "store that …", "/memory:store …", or when you want a scoped decision, gotcha, validation, or why-note to survive across sessions. Requires `memory init` to have run.
viewOpen the project Memory graph in red-ui (the visual cluster/query/collections workspace) by pointing the red-ui MCP App at the local RedDB store, falling back to the browser Workbench in terminal hosts. Use when the user wants to SEE the memory graph, clusters, or collections visually rather than re
wiki-initBootstrap the LLM Wiki pattern in a repo — create `.red/wiki/` layout, write `.red/agents/wiki.md` schema, gitignore wiki artifacts, register a `### Wiki` entry under `## Agent skills` in CLAUDE.md/AGENTS.md. Run once per repo before using `/wiki`. Re-run only to reset.
wikiOperate the LLM Wiki — ingest a source (URL or file), query the wiki and optionally file the answer back as a page, or lint for contradictions/orphans/stale claims. Requires `/wiki-init` to have run. Use when ingesting a doc, asking a question against the knowledge base, or checking the wiki for con
rs_memoryruns: red-skills-memory mcp
reddb.io dev plugin — engineering skills for code agents (autonomous /afk loop, triage, tdd, diagnose, graph-aware codebase understanding, wiki, …)
54 skills · 3 agents · 1 MCP server
reddb.io brain plugin — project-local RedDB knowledge repository for freeform captures, typed artifacts, graph connections, and human-facing recall.
5 skills · 1 MCP server
reddb.io internal plugin — maintainer-only skills for operating the red-skills repository.
2 skills
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Scaffold, validate, and publish new Claude Code plugins with proper structure
3 skills · 1 command · 1 agent
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Use Alibaba Open Code Review from local Codex.
2 skills
Claude Code skill for creating and presenting Slidev slidedecks
1 skill
Code intelligence powered by a knowledge graph. Provides execution flow tracing, blast radius analysis, and augmented search across your codebase.
12 skills · 1 MCP server · hooks
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.