okx-audit-log

Export Onchain OS audit logs to JSON Lines files for troubleshooting.

Updated Apr 8, 2026

Search Tags:#troubleshooting #logs #audit #jsonl #onchain-os #audit-log-export

Ready to run

npx skills add https://github.com/Sarnav07/Nexus.AI --skill okx-audit-log-sarnav07

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: okx-audit-log
Source: https://github.com/Sarnav07/Nexus.AI/tree/main/.agents/skills/okx-audit-log
Command: npx skills add https://github.com/Sarnav07/Nexus.AI --skill okx-audit-log-sarnav07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a simple way to export and locate on-chain audit logs, view command history, and access operation records without exposing wallet balances or performing on-chain transactions.

Core Features & Use Cases

Export audit logs to a machine-readable file for offline troubleshooting.
Locate audit log files and review historical command activity across devices.
Safe and scoped: does not perform wallet or token operations; this skill is solely for audit log access and inspection.

Quick Start

Ask the AI to export the audit logs to the default path at ~/.onchainos/audit.jsonl and review the resulting file.

Frequently Asked Questions about okx-audit-log

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

FAQPage Schema

How do I export on-chain audit logs to a machine-readable format for troubleshooting?▼

Export on-chain audit logs to a machine-readable JSON Lines file at ~/.onchainos/audit.jsonl for offline troubleshooting. This structures command history and wallet actions across multiple devices without exposing balances or performing transactions.

What is the JSONL format used for on-chain audit log tracing?▼

The JSONL format structures on-chain audit logs into individual JSON entries, meeting requirements for device headers, entry fields, and rotation constraints. It enables structured tracing of command history and wallet actions across devices.

How do I locate historical command activity across multiple on-chain devices?▼

Locate historical command activity by exporting audit logs from Onchain OS to a default file path. The exported file contains structured operation records and command history across multiple devices and environments for offline review.

Does the audit log export process perform any wallet or token operations?▼

The audit log export process does not perform wallet or token operations. It is scoped solely to log access and inspection, meaning it safely retrieves operation records and command history without exposing wallet balances.

What are the limitations of troubleshooting on-chain operations using exported logs?▼

Troubleshooting is limited to reviewing historical command activity and operation records. The approach does not support real-time debugging, perform on-chain transactions, or expose wallet balances, focusing strictly on offline log inspection.