ns-config

Display active Neuralscape plugin configuration without exposing sensitive credentials.

5|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/ehfazrezwan/neuralscape --skill ns-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ns-config
Source: https://github.com/ehfazrezwan/neuralscape/tree/main/neuralscape-plugin/skills/ns-config
Command: npx skills add https://github.com/ehfazrezwan/neuralscape --skill ns-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users often cannot quickly verify their Neuralscape plugin configuration, leading to misconfigured service URLs, collided user identities from OS username fallbacks, and hard-to-troubleshoot memory operation failures.

Core Features & Use Cases

  • Read-Only Config Display: Shows your active Neuralscape service URL, user ID, and API key status without exposing the actual sensitive API key value to prevent secret leaks.
  • Cross-Platform Identity Explanation: Clarifies how your user identity is resolved, whether via local plugin config, environment variables, OS username fallback in Claude Code, or OAuth connector authentication in Claude Cowork.
  • Misconfiguration Alerts: Warns you if your user ID is falling back to your machine's OS username, which can cause memory collisions across different devices. Use this skill when you are getting unexpected memory results, cannot connect to your Neuralscape service, or want to confirm your plugin is properly authenticated.

Quick Start

Ask the AI to display your current Neuralscape plugin configuration to verify all your settings are correct.

Frequently Asked Questions about ns-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my Neuralscape plugin configuration and connection status?

To check your Neuralscape plugin configuration, use a read-only inspection tool that displays your active service URL, user ID, and API key status to verify your connection without exposing sensitive credentials.

Why does my Neuralscape memory operation fail due to cross-device identity collisions?

Neuralscape memory operations fail when your user identity falls back to your machine's OS username, causing cross-device memory collisions. You need to verify your identity resolution to prevent this misconfiguration.

Can I verify my Neuralscape connection in both Claude Code and Claude Cowork environments?

Yes, you can verify your Neuralscape connection across both Claude Code local plugin environments and Claude Cowork connector modes using read-only configuration inspection that works without triggering memory writes.

How is my Neuralscape user identity resolved across different platforms?

Your Neuralscape user identity is resolved via local plugin config, environment variables, OS username fallback in Claude Code, or OAuth connector authentication in Claude Cowork, depending on your active environment.

Does checking Neuralscape API key status expose my actual sensitive credentials?

No, checking your Neuralscape API key status does not expose your actual sensitive credentials. The read-only configuration display shows the key status safely to prevent secret leaks.

What should I do if my Neuralscape service URL is misconfigured?

If your Neuralscape service URL is misconfigured, you should inspect your active plugin settings to verify the URL, confirm your user ID is not falling back to your OS username, and troubleshoot any memory operation failures.