Niplex Skills Helper

Niplex Skills Helper is a separately distributed, mobile-compatible Obsidian companion for the Niplex ecosystem. It looks up instruction-only skills from the public-for-preview Aj-Niplex/Niplex-Obsidian-skills catalogue, lets the user preview and verify a package, and writes an explicitly approved skill into NIPLEX-OBSIDIAN/Skills/<code>/.

The repository, manifest, release history, and Community entry remain independent from Niplex Research AI. When a compatible Niplex ecosystem host is present, the helper registers a read-only action that opens the marketplace inside the host’s Actions surface. Marketplace lookup, preview, digest verification, and installation remain explicit user actions; the helper never silently downloads, enables, or executes another plugin.

Ecosystem boundary

The helper uses the versioned niplex-ecosystem protocol only for capability discovery and a user-invoked marketplace action. It does not contribute vault context by default, does not receive provider keys, and cannot modify the Research AI protected prompt, write approvals, or safety limits. If the host is missing, disabled, incompatible, or slow, the marketplace remains usable on its own.

Installed skills are read by Niplex Research AI as untrusted additive guidance. They cannot replace the protected prompt, run code, access secrets, or bypass approvals. The host may later request selected skill guidance only after the user chooses a specific skill and grants that capability.

Marketplace and privacy

This helper never reuses Gemini or Agnes keys. The public catalogue works without a PAT. If you point the helper at a private fork or private endpoint later, enter a read-only GitHub token in the marketplace modal; it is stored in Obsidian SecretStorage. The package is written only after digest and safety validation.

Local validation

Run npm install, npm run validate, npm run build, and npm run package:release to verify the source locally. The normal delivery is the independent GitHub source repository; no GitHub Actions workflow or paid runner is required.