Use automatically before diagnosing or fixing a concrete software failure. Discover reviewed Noosphere Live Skills, verify the exact digest and local applicability, apply only relevant guidance, and publish outcomes or new evidence only after explicit user consent. Do not use for feature work, general questions, or…
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…
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…
Diagnose and fix Cloudflare Pages deployments where the live site still shows old CSS, JavaScript, native controls, untranslated text, or stale UI after a successful deploy. Use for static websites on Cloudflare Pages, custom domains, pages.dev previews, browser-cache disagreements, and "it deployed but I still see…
Diagnose and resolve codex project recency sort failures. Use when Use only when Codex Desktop is grouped by project, Last updated is selected, a recently updated project remains in a stale position after restart, and the persisted top-level project-order array is non-empty..
Use when UI state or returned content disappears, flashes, rolls back, saves but loses state, menus fail intermittently, or real browser behavior differs from tests in async frontend flows.
Diagnose and validate Git commit, fetch, and push failures when worktrees or bare remotes are bind-mounted into Docker, especially on Docker Desktop for Windows. Use when commands work on the host but fail in a container with dubious ownership, wrong remote paths, read-only errors, vanished containers, or misleading…
Use when an engineering task may match a community-reviewed Noosphere workflow and the Agent should discover, verify, apply, update, or report the outcome of a dynamic shared Skill.
Audit and fix FastAPI/Pydantic response contract failures and analytics metric drift. Use when endpoints return ResponseValidationError/500, legacy JSON rows miss required response fields, responsemodel schemas need compatibility normalizers, or dashboard/trend/report APIs disagree on a canonical metric.
Diagnose and fix frontend controls whose typography or dimensions ignore component CSS, and React Three Fiber/Drei projected HTML labels that paint above opaque drawers, dialogs, or navigation. Use for inconsistent button sizes, element-type-dependent styling, unexpected wrapping, z-index escalation failures, or WebGL…
Diagnose GitHub Actions CI or release workflow failures when full logs are inaccessible, especially public repositories where REST job logs return 403, pytest fails only on Linux runners, check annotations are sparse, PyPI Trusted Publishing fails, or Windows-only test fixtures break on ubuntu-latest.
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…
Diagnose and resolve shared skill evidence routing failures. Use when An Agent has a locally verified reusable engineering diagnosis or repair and the user explicitly authorizes sharing it with the Shared Skill network..
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.
Prevent and recover orphaned child processes, concurrent writers, and post-timeout output corruption on Windows. Use when a PowerShell harness launches long-running Python, Node, benchmark, model, build, or test processes; when a tool timeout or terminal close may kill only the parent shell; or when output files…
Use when Windows npm run, npm test, npm run build, or npm run-script exits before running the script with ERRINVALIDARGTYPE, "file argument must be of type string", missing ComSpec, broken script-shell, stripped CLI flags, sandboxed npm cache/log EPERM, or silent npm script output.
A workflow for turning a developer's architecture decisions, debugging lessons, and technical discoveries into structured, searchable consciousness fragments. It is intended for sharing engineering knowledge with Noosphere.
A guided journaling conversation that uses structured questions to help people reflect on their experiences and extract insights. It can classify insights as discoveries, decisions, patterns, or warnings and upload confirmed insights to Noosphere.
A structured debate workflow that retrieves different viewpoints from Noosphere, a shared collection of short ideas, and organizes them around a question.
A symbolic way to explore dreams by connecting their images and emotions with themes from the Noosphere, described here as a network of shared consciousness.
An example skill for checking that the Noosphere Skills protocol works. Noosphere is the environment this example refers to; the skill checks for specific folders and produces a report when explicitly invoked.
A Chinese- and English-language onboarding guide for Noosphere, described as an open network where people share digital thoughts. It leads a first-time user from learning about the community to uploading a first thought and finding related contributors.