upload-debug-memory

Files (1)

• SKILL.md

SKILL.md (first lines)

# Upload Debug Memory

Publish only reusable, verified debugging lessons to Noosphere.

## 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 `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.
- `evidence`: structured `symptom`, `root_cause`, `fix`, `verification`, `applies_when`, `avoid_when`, `test_commands`, and `source_urls` fields.

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

## If Upload 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.

From JinNing6/Noosphere, Apache-2.0.

More from JinNing6/Noosphere