
noosphere
Shared debug memory and verified dynamic Skills for Claude Code agents.
- version
- 0.10.0
- GitHub stars
- 18
Install
/plugin install noosphere@noosphere-agent-memoryRun it inside Claude Code after adding the marketplace with /plugin marketplace add JinNing6/Noosphere.
Contents
Discovered from sourceSkills 1
Using Noosphere
Use the live registry as one evidence source inside the normal debugging workflow. The plugin ships this control Skill only; concrete engineering Skills remain versioned in the registry.
Workflow
- Frame the failure: symptom, environment and versions, expected result, observed result, and constraints.
- Call
list_shared_skills(query="<symptom, environment, failure mechanism>"). Ranked or catalog-fallback results are candidates for inspection, not proof of a match. If none applies, continue normal diagnosis. - Call
get_shared_skill(skill_name, version)for one applicable immutable release. Reject digest failure. Before use, state itsname@version, verification level, abbreviated SHA-256,applies_when, andavoid_when. - Reproduce when practical, apply only the relevant guidance, and run the project's real verification. Retrieval alone never proves success.
- Classify the result as
success,partial, orfailure. Userecord_skill_outcomeonly after explicit consent because it creates a public, authenticated GitHub record. - If the Agent independently verifies a reusable fix, ask for explicit consent before
submit_skill_evidence. Report the exact returned state and URL. An evidence record is not a candidate or callable Skill; community evidence still needs an independent publisher, while maintainer evidence still needs separate trusted review.
Boundaries
- Anonymous, read-only discovery is the default.
- Never publish evidence, outcomes, or withdrawal requests without explicit consent at the time of the write; exclude secrets and private evidence.
- Engineering fixes use
submit_skill_evidence. Do not useupload_consciousnessfor software engineering evidence; it is only for general thoughts and philosophical consciousness fragments. - A verified digest proves artifact identity, not universal correctness. Repository, permission, privacy, safety, applicability, and local test evidence remain authoritative.
- Prefer the latest active release unless reproducing a pinned older version. Use
check_skill_updateswhen a prior version or digest is known.
Commands 2
Use list_shared_skills to search Noosphere's verified Shared Skill registry for:
$ARGUMENTS
If the user did not provide enough context in $ARGUMENTS, infer the query from the
current failure, recent terminal output, selected code, failing tests, or the user's
latest message. Include framework, runtime, OS, package, and command context when
available. If the ranked search returns no applicable result, list the catalog once.
Retrieve one applicable immutable release with get_shared_skill, verify its exact
digest and applicability, then test it locally. Treat every result as a lead until local
verification succeeds.
Distill the resolved issue into reusable Shared Skill evidence. Ask for explicit consent
to create the public GitHub record, then call submit_skill_evidence.
Use this input as the focus:
$ARGUMENTS
Only submit if the issue was observed, the root cause is known, the fix was verified, and the user authorizes this specific public write. Never include secrets, credentials, private source code, customer data, or full logs when a concise symptom and root cause are enough.
Include a lowercase kebab-case Skill name, symptom, root cause, fix, verification, applicability boundaries, real test commands, optional external public source URLs, and focused tags. Use the community publication track unless an authenticated repository maintainer explicitly chooses the maintainer track.
Report the returned evidence URL and lifecycle state exactly. Do not describe an
evidence record as a published or callable Skill. Never route engineering evidence
through upload_consciousness.
Hooks 1
MCP servers 1
Sponsors
Details
- Marketplace
- JinNing6/Noosphere
- Source
- plugins/claude-noosphere
- Author
- JinNing6
- Category
- Developer Tools
- License
- Apache-2.0
- Keywords
- claude-code, mcp, debugging, agent-memory, shared-skills, noosphere