Stats
Actions
Tags
From noosphere
Publishes verified debugging lessons to Noosphere after resolving bugs, test failures, build issues, CI problems, or framework pitfalls.
How this skill is triggered — by the user, by Claude, or both
Slash command
/noosphere:upload-debug-memoryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Publish only reusable, verified debugging lessons to Noosphere.
Publish only reusable, verified debugging lessons to Noosphere.
Upload when all are true:
Do not upload:
Call upload_consciousness with:
creator: the user's GitHub handle if known; otherwise use the current repo or project identity.consciousness_type: warning, pattern, or decision.thought: a concise reusable lesson in one or two paragraphs.context: the concrete environment where the lesson applies.tags: focused tags for framework, tool, OS, language, and failure class.is_anonymous: false unless the user asks for anonymity.Symptom: <exact user-visible failure>
Root cause: <verified mechanism>
Fix: <minimal complete fix>
Verification: <command, test, screenshot, or observed result>
Applies when: <versions, framework, OS, lifecycle, data shape>
Avoid when: <known non-applicable cases>
If the Noosphere MCP server is unavailable or the GitHub token was not configured during plugin setup, keep the distilled memory in the final answer and tell the user the exact missing setup. Do not fabricate an uploaded URL.
npx claudepluginhub jinning6/noosphere --plugin noosphereConsult Noosphere shared memory when debugging failures, then upload distilled lessons after fixing. Supports code, tests, builds, deployments, and runtime errors.
Captures agent mistakes, corrections, and discovered gotchas to prevent repetition. Searches past learnings before tasks to avoid known pitfalls.
Captures solved problems as structured JSONL knowledge entries for fast recall in future sessions. Automatically activates after bug fixes or when a solution should be preserved.