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

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

nio-report

Étoiles19

Forks0

Mis à jour22 juin 2026 à 07:35

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.

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-report
description	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.
compatibility	Requires Node.js 18+.
metadata	{"author":"core0-io","version":"2.5.1"}
user-invocable	true
command-arg-mode	raw
argument-hint

Nio — Execution Report

Display recent agent execution events from the Nio audit log. This is the focused report capability of the Nio framework.

Passive invocation. If the user asks what Nio blocked/confirmed recently, to see the audit log / recent activity, or for a diagnostics summary, you MUST read and format the audit log as below.

This skill uses the Read tool only — there is no script to run. Do not attempt to invoke any report.js / report-cli.js — none exist. The only action is: read ~/.nio/audit.jsonl with the Read tool, parse each line as JSON, and format the output as shown below.

Log Location

The audit log is stored at ~/.nio/audit.jsonl (or $NIO_HOME/audit.jsonl). Each line is a JSON object with an event discriminator field: guard (one per tool-call evaluation), session_scan, lifecycle, diagnostic.

A diagnostic entry carries source (one of config, oauth, llm, external_analyser, collector, scanner, hook), kind, severity, component, message, optional hint. Aggregate diagnostics by (source, kind, component, config_path) into a Diagnostics summary section. Old-format lines (no event field) are guard entries with event_type: "pre".

How to Display

Read ~/.nio/audit.jsonl using the Read tool
Parse each line as JSON
Filter by event type — guard entries in the main table, scan entries in a separate section
Show recent events (last 50 by default)
If any events have initiating_skill, add a "Skill Activity" section grouping events by skill

Output Format

## Nio Execution Report

**Events**: <total count>
**Blocked**: <deny count>
**Confirmed**: <confirm count>

### Recent Events

| Time | Tool | Type | Decision | Risk | Score | Phase | Top Finding | Skill |
|------|------|------|----------|------|-------|-------|-------------|-------|
| 14:30 | Bash | exec | DENY | critical | 0.95 | 2 | DANGEROUS_COMMAND | some-skill |

### Diagnostics

| Count | Source | Kind | Component |
|-------|--------|------|-----------|
| 2 | oauth | token_failed | scorer_primary |

### Summary
<Brief analysis of agent execution behaviour and any patterns of concern>

If the log file doesn't exist, inform the user that no execution events have been recorded yet, and suggest enabling hooks via ./setup.sh or by adding the plugin.

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-doctor

core0-io/nio

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.

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-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-report
description	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.
compatibility	Requires Node.js 18+.
metadata	{"author":"core0-io","version":"2.5.1"}
user-invocable	true
command-arg-mode	raw
argument-hint

Nio — Execution Report

Display recent agent execution events from the Nio audit log. This is the focused report capability of the Nio framework.

Passive invocation. If the user asks what Nio blocked/confirmed recently, to see the audit log / recent activity, or for a diagnostics summary, you MUST read and format the audit log as below.

Log Location

How to Display

Read ~/.nio/audit.jsonl using the Read tool
Parse each line as JSON
Filter by event type — guard entries in the main table, scan entries in a separate section
Show recent events (last 50 by default)
If any events have initiating_skill, add a "Skill Activity" section grouping events by skill

Output Format

## Nio Execution Report

**Events**: <total count>
**Blocked**: <deny count>
**Confirmed**: <confirm count>

### Recent Events

| Time | Tool | Type | Decision | Risk | Score | Phase | Top Finding | Skill |
|------|------|------|----------|------|-------|-------|-------------|-------|
| 14:30 | Bash | exec | DENY | critical | 0.95 | 2 | DANGEROUS_COMMAND | some-skill |

### Diagnostics

| Count | Source | Kind | Component |
|-------|--------|------|-----------|
| 2 | oauth | token_failed | scorer_primary |

### Summary
<Brief analysis of agent execution behaviour and any patterns of concern>

If the log file doesn't exist, inform the user that no execution events have been recorded yet, and suggest enabling hooks via ./setup.sh or by adding the plugin.