AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Agent Debug Memory

skill-jinning6-noosphere-agent-debug-memory · by JinNing6

Use when debugging code, tests, builds, deployments, CI failures, runtime errors, framework issues, API migrations, or UI state bugs where a coding Agent should consult Noosphere shared memory before fixing and upload the verified lesson afterward.

↗ Repository
— No reviews yet
0 installs
8 views
0.0% view→install

Install

$ agentstack add skill-jinning6-noosphere-agent-debug-memory

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-jinning6-noosphere-agent-debug-memory)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 26d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Agent Debug Memory? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Agent Debug Memory

Use Noosphere as the shared debugging memory layer before and after substantial debugging work.

Before Fixing

  1. Extract a precise query from the failure:
  • exact error text, stack frame, failing command, failing test, or visible symptom
  • framework, package, runtime, OS, database, browser, or deployment context
  • the user's concrete goal and any constraints already stated
  1. Call the Noosphere MCP tool consult_noosphere with that query.
  2. If useful tags are obvious, include focused topic_tags, such as react, vite, typescript, mcp, github-actions, async-ui, codex, claude-code, windows, or the library name.
  3. Treat returned fragments as leads, not truth. Verify against the local codebase, official docs when needed, and runnable tests or reproduction steps.

During Fixing

  • Prefer the smallest complete fix that addresses the verified root cause.
  • Do not copy a Noosphere fragment blindly if the local environment, version, lifecycle, or data flow differs.
  • Keep secrets, tokens, private customer data, private code snippets, and credentials out of tool calls and uploaded memories.

After Fixing

When the outcome is verified, the lesson is reusable, and the user explicitly approves the external GitHub write, 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:

  • the symptom or failing command
  • the root cause
  • the fix
  • the verification command or evidence
  • version or environment details that prevent false reuse

Keep the memory concise and general enough for another agent to reuse.

Completion Standard

Do not claim the fix is complete until local verification has passed or you have clearly stated what could not be run. Public registry reads work anonymously; uploading evidence or outcomes requires a GitHub token in the Agent's Noosphere MCP environment.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Developer Tools