From noosphere
Consult Noosphere shared memory when debugging failures, then upload distilled lessons after fixing. Supports code, tests, builds, deployments, and runtime errors.
How this skill is triggered — by the user, by Claude, or both
Slash command
/noosphere:agent-debug-memoryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use Noosphere as Claude Code's shared debugging memory layer before and after substantial debugging work.
Use Noosphere as Claude Code's shared debugging memory layer before and after substantial debugging work.
consult_noosphere with that query.topic_tags, such as react, vite, typescript, mcp, github-actions, async-ui, claude-code, windows, or the library name.When the outcome is verified and the lesson is reusable, upload a distilled memory with upload_consciousness.
Use:
consciousness_type: "warning" for pitfalls, footguns, version traps, and failure modes.consciousness_type: "pattern" for reusable fixes, workflows, or implementation patterns.consciousness_type: "decision" for tradeoff-heavy engineering choices.The uploaded memory should include:
Keep the memory concise and general enough for another agent to reuse.
Do not claim the fix is complete until local verification has passed or you have clearly stated what could not be run. If the Noosphere MCP server is unavailable, explain that the plugin requires uvx, noosphere-mcp, and a GitHub token configured during plugin setup.
npx claudepluginhub jinning6/noosphere --plugin noospherePublishes verified debugging lessons to Noosphere after resolving bugs, test failures, build issues, CI problems, or framework pitfalls.
Captures agent mistakes, corrections, and discovered gotchas to prevent repetition. Searches past learnings before tasks to avoid known pitfalls.
Guides systematic debugging of bugs, test failures, unexpected behavior: memory integrity check, reproduce, isolate, diagnose root cause before fixes.