skills.rest
gist-kol-copy-trade-agent
gist-kol-copy-trade-agentOFFICIAL
Explore all skills by this author →
GitHub

okx-audit-log

Export Onchain OS audit logs in JSON Lines format for offline troubleshooting.

1|Updated Apr 13, 2026
Search Tags:#debugging#troubleshooting#logs#audit#json-lines#onchain-os#audit-path
One-click install
npx skills add https://github.com/gist-kol-copy-trade-agent/agent-system --skill okx-audit-log-gist-kol-copy-trade-agent
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okx-audit-log
Source: https://github.com/gist-kol-copy-trade-agent/agent-system/tree/main/okx-onchainos-skills/okx-audit-log
Command: npx skills add https://github.com/gist-kol-copy-trade-agent/agent-system --skill okx-audit-log-gist-kol-copy-trade-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide access to the Onchain OS audit logs for offline troubleshooting, enabling developers to locate log files, inspect history, and analyze audit trails without exposing live system details.

Core Features & Use Cases

  • Locate the default audit log path (e.g., ~/.onchainos/audit.jsonl) for debugging and incident analysis.
  • Review per-entry fields such as ts, source, command, ok, duration_ms, args, and error to understand system activity.
  • Use for offline triage, performance debugging, and compliance reviews across Onchain OS deployments.

Quick Start

Export the audit log to the default path and review the most recent entries.

Frequently Asked Questions about okx-audit-log

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

FAQPage Schema
How do I locate the default audit log path on Onchain OS for offline troubleshooting?▼

The default audit log path is ~/.onchainos/audit.jsonl. Locating this JSON Lines file allows you to inspect command history and review audit trails for offline triage and performance debugging.

What fields are included in the Onchain OS audit log entries?▼

Audit log entries include fields such as ts, source, command, ok, duration_ms, args, and error. Reviewing these fields helps you understand system activity and analyze failures during incident analysis.

How does the JSON Lines format work for Onchain OS audit logs?▼

The JSON Lines format stores each audit log entry as a separate JSON object. This structure enables sequential reading of command history and audit trails while specifying device headers and rotation rules.

Can I use these audit logs for compliance reviews across multiple Onchain OS deployments?▼

Yes, you can export and review audit logs for compliance reviews across Onchain OS deployments. Inspecting the exported JSON Lines files provides an offline record of system activity without exposing live details.

What is the best way to export Onchain OS audit logs for incident analysis?▼

The best way to export audit logs for incident analysis is to retrieve the default JSON Lines file. This offline export captures command history, duration, and errors to support performance debugging and triage.

Do I need live system access to review Onchain OS audit trails?▼

No, you do not need live system access to review audit trails. Exporting the JSON Lines audit log allows you to perform offline troubleshooting and compliance reviews safely without exposing live system details.

Related Skills

Explore More Software Engineering Skills→
Dargon789Dargon789
3

okx-audit-log

Generate and export JSON Lines audit logs from Onchain OS.

Community
Basic
OkheerOkheer

okx-audit-log

Exports Onchain OS audit logs to JSON Lines for offline troubleshooting.

Community
Basic
aram-devdocsaram-devdocs
6

goudengine-debugging

Attach to live GoudEngine game processes and retrieve subsystem diagnostics.

Community
Advanced
Sarnav07Sarnav07

okx-audit-log

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

Community
Basic