Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

nio-doctor

Étoiles19

Forks0

Mis à jour22 juin 2026 à 07:35

Nio config validator + connectivity check. Use when the user wants to validate their Nio setup — e.g. "run nio doctor", "is my nio config valid / working", "test my OAuth / external endpoint / LLM connectivity", "why isn't my scorer firing". Focused single-purpose skill; for other Nio operations use /nio.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

core0-io

core0-io/nio

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Autres occupations informatiquesProfessions informatiques et mathématiques·SOC 15-1299

SKILL.md

readonly

name	nio-doctor
description	Nio config validator + connectivity check. Use when the user wants to validate their Nio setup — e.g. "run nio doctor", "is my nio config valid / working", "test my OAuth / external endpoint / LLM connectivity", "why isn't my scorer firing". Focused single-purpose skill; for other Nio operations use /nio.
compatibility	Requires Node.js 18+.
metadata	{"author":"core0-io","version":"2.5.1"}
user-invocable	true
command-arg-mode	raw
argument-hint

Nio — Doctor

Validate the current configuration end-to-end. Doctor catches issues before they cause silent failures during real tool calls. This is the focused doctor capability of the Nio framework.

Passive invocation. If the user asks whether their Nio setup/config is valid or working, to test OAuth/LLM/external-endpoint connectivity, or why a scorer isn't firing, you MUST run the CLI below rather than reasoning about it from memory.

Resolving the Script Path

The CLI for this skill lives in the sibling nio skill, not in this skill's own directory:

This SKILL.md's parent directory is THIS skill's directory (e.g. <plugins>/skills/nio-doctor/).
The script is the sibling nio skill's scripts/doctor-cli.js — i.e. ../nio/scripts/doctor-cli.js relative to this directory. Derive the absolute path; do not hard-code ~/.claude/....
Invoke with a single node command — no cd, no ;/&&/|/$(...)/backticks.

Example (substitute the real absolute path):

node /absolute/path/to/skills/nio/scripts/doctor-cli.js

Print its stdout verbatim — it is already formatted markdown.

What Doctor Checks

Configuration — re-runs schema validation against the live ~/.nio/config.yaml, flagging any field with a path + message.
External analysers — fires each enabled guard.external_analyser endpoint (OAuth entries do a real client_credentials grant) and reports ✓ with the returned score or ✗ with the underlying error + a hint: line.
LLM analyser — flags guard.llm_analyser.enabled=true paired with an empty api_key.

Collector reachability is intentionally not probed (OTLP gateways often need routing headers a bare probe wouldn't send). Doctor never writes to the audit log — its probes use a scoped collector discarded after the command returns.

Output Format

A markdown checklist with ✓ / ✗ per check and inline hint: lines, e.g.:

## Nio Doctor

### Configuration
- ✓ ~/.nio/config.yaml loaded successfully

### External Analysers (1 configured)
- ✓ guardrail (https://score.example.com) — score 0.42 [oauth]

Plus depuis ce dépôt

même dépôt

nio-action

core0-io/nio

Nio runtime action safety evaluator. Use when the user asks whether a specific runtime action is safe — e.g. "is it safe to run `<command>`", "should I allow this curl/POST", "evaluate this file write / secret access", "check this action with nio". Returns allow/deny/confirm. Focused single-purpose skill; for other Nio operations use /nio.

2026-06-2219

nio-config

core0-io/nio

Nio configuration viewer/editor. Use when the user wants to view or change Nio settings — e.g. "show my nio config", "set nio to strict/balanced/permissive", "what protection level am I on", "reset nio config". Focused single-purpose skill; for other Nio operations use /nio.

2026-06-2219

nio-external-score

core0-io/nio

Nio external scoring-endpoint snapshot. Use when the user asks about their current Nio/risk scores from configured external scoring endpoints — e.g. "what's my Nio score", "tell me the nio score", "check my external/guardrail endpoint scores", "what do my scoring services return right now", "list the current risk scores from my external analysers". Focused single-purpose skill; for other Nio operations use /nio.

2026-06-2219

nio-report

core0-io/nio

Nio execution audit report. Use when the user wants to review recent agent execution activity — e.g. "show my nio report", "what did nio block recently", "show the audit log / recent activity", "any diagnostics / errors in nio". Read-only. Focused single-purpose skill; for other Nio operations use /nio.

2026-06-2219

nio-scan

core0-io/nio

Nio code/skill execution-risk scanner. Use when the user wants to scan a file, repo, directory, or skill for execution risks — e.g. "scan this code for risks", "is this file/plugin dangerous", "check this repo for malicious code", "run nio scan on <path>". Focused single-purpose skill; for other Nio operations use /nio.

2026-06-2219

nio

core0-io/nio

Nio — AI agent execution assurance. Use for evaluating action safety before execution, scanning code for execution risks, reviewing the agent execution audit log, and querying the current risk scores returned by configured external scoring endpoints (e.g. "what's my Nio score", "check my external/guardrail endpoint scores", "show the current risk scores from my scoring services").

2026-06-2219

name	nio-doctor
description	Nio config validator + connectivity check. Use when the user wants to validate their Nio setup — e.g. "run nio doctor", "is my nio config valid / working", "test my OAuth / external endpoint / LLM connectivity", "why isn't my scorer firing". Focused single-purpose skill; for other Nio operations use /nio.
compatibility	Requires Node.js 18+.
metadata	{"author":"core0-io","version":"2.5.1"}
user-invocable	true
command-arg-mode	raw
argument-hint

Nio — Doctor

Validate the current configuration end-to-end. Doctor catches issues before they cause silent failures during real tool calls. This is the focused doctor capability of the Nio framework.

Passive invocation. If the user asks whether their Nio setup/config is valid or working, to test OAuth/LLM/external-endpoint connectivity, or why a scorer isn't firing, you MUST run the CLI below rather than reasoning about it from memory.

Resolving the Script Path

The CLI for this skill lives in the sibling nio skill, not in this skill's own directory:

This SKILL.md's parent directory is THIS skill's directory (e.g. <plugins>/skills/nio-doctor/).
The script is the sibling nio skill's scripts/doctor-cli.js — i.e. ../nio/scripts/doctor-cli.js relative to this directory. Derive the absolute path; do not hard-code ~/.claude/....
Invoke with a single node command — no cd, no ;/&&/|/$(...)/backticks.

Example (substitute the real absolute path):

node /absolute/path/to/skills/nio/scripts/doctor-cli.js

Print its stdout verbatim — it is already formatted markdown.

What Doctor Checks

Configuration — re-runs schema validation against the live ~/.nio/config.yaml, flagging any field with a path + message.
External analysers — fires each enabled guard.external_analyser endpoint (OAuth entries do a real client_credentials grant) and reports ✓ with the returned score or ✗ with the underlying error + a hint: line.
LLM analyser — flags guard.llm_analyser.enabled=true paired with an empty api_key.

Output Format

A markdown checklist with ✓ / ✗ per check and inline hint: lines, e.g.:

## Nio Doctor

### Configuration
- ✓ ~/.nio/config.yaml loaded successfully

### External Analysers (1 configured)
- ✓ guardrail (https://score.example.com) — score 0.42 [oauth]