---
name: upload-debug-memory
description: Use after resolving a bug, test failure, build failure, CI issue, deployment issue, or framework/API pitfall when the verified lesson should be published to Noosphere for future agents.
---

# Submit Debug Skill Evidence

Submit reusable, verified debugging lessons to the Noosphere Shared Skill lifecycle.
Engineering evidence must not be uploaded as a consciousness fragment.

## Gate

Upload when all are true:

- The issue was reproduced or clearly observed.
- The root cause is known.
- The fix or workaround was verified.
- The lesson is likely to help another agent avoid wasted debugging time.
- The user has explicitly approved the external GitHub write.

Do not upload:

- secrets, tokens, private data, customer data, proprietary source snippets, or credentials
- speculation that was not verified
- one-off local machine state with no reusable lesson
- full logs when a concise symptom and root cause are enough

## Shape

Call `submit_skill_evidence` only after the user approves this specific public write:

- `skill_name`: a proposed lowercase kebab-case name, or an existing registry Skill name.
- `symptom`, `root_cause`, `fix`, `verification`, `applies_when`, and optional `avoid_when`.
- `test_commands`: real commands that another Agent can rerun.
- `source_urls`: optional public upstream Issues, PRs, or artifacts. If omitted, the
  created public evidence Issue becomes the canonical source record.
- `tags`: focused tags for framework, tool, OS, language, and failure class.
- `publication_track`: `community` by default. Use `maintainer` only when an
  authenticated repository maintainer explicitly chooses it.

Never call `upload_consciousness` for a software engineering fix. That tool is reserved
for general thoughts and philosophical consciousness fragments.

## Recommended Memory Template

```text
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>
```

## Lifecycle Result

Report the returned state exactly:

- `evidence-recorded` means the public evidence exists, but it is not callable.
- Community evidence still needs a matching independent publisher and shared command.
- Maintainer evidence still needs a separate trusted review and can only publish as
  `maintainer-validated`.
- Only a reviewed immutable registry release is a callable Shared Skill.

## If Submission Cannot Run

If the Noosphere MCP server is unavailable or `GITHUB_TOKEN` is missing, keep the distilled memory in the final answer and tell the user the exact missing setup. Do not fabricate an uploaded URL.