القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use automatically before diagnosing or fixing a concrete software engineering failure, including bugs, exceptions, failing tests, build or CI failures, deployment and runtime faults, package installation failures, API or framework traps, performance regressions, and repeated incident patterns. Retrieve applicable reviewed Noosphere Live Skills through MCP, verify the exact artifact digest, apply only after checking local evidence, run real verification, and report an outcome only with explicit user consent. Do not use for unrelated feature work, general questions, or speculative discussion.
Use automatically before diagnosing or fixing a concrete software engineering failure, including bugs, exceptions, failing tests, build or CI failures, deployment and runtime faults, package installation failures, API or framework traps, performance regressions, and repeated incident patterns. Retrieve applicable reviewed Noosphere Live Skills through MCP, verify the exact artifact digest, apply only after checking local evidence, run real verification, and report an outcome only with explicit user consent. Do not use for unrelated feature work, general questions, or speculative discussion.
Verify Python packages, CLIs, MCP servers, and Agent plugins through the exact installed artifact and real runtime contract. Use when source tests pass but a published release may omit modules, expose broken entry points, depend on local paths, fail without optional credentials, or behave differently after public installation.
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.
Audit and repair readers for fixed-length binary credentials and their text encodings without mutating raw bytes. Use when code loads Ed25519/X25519 keys, nonces, digests, MAC keys, signatures, tokens, or other opaque bytes from files or environment values; when `.strip()`, decoding, newline handling, or format auto-detection occurs before length/type validation; or when cryptographic tests fail intermittently for otherwise valid generated material.
Diagnose browser UI tests or real browser checks where an element appears visible but cannot be clicked, copied, hovered, or focused. Use for Playwright/Chrome/browser automation failures involving overlays, splash screens, opacity transitions, pointer-events, elementFromPoint mismatches, clipboard assertions, or differences between "visible" and actually actionable UI.
| 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. |
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.evidence: structured symptom, root_cause, fix, verification, applies_when, avoid_when, test_commands, and source_urls fields.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 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.