audit-log

Parse WrongStack session JSONL logs and generate structured markdown audit reports.

224|27|Updated May 12, 2026
One-click install
npx skills add https://github.com/WrongStack/WrongStack --skill audit-log-wrongstack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-log
Source: https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/audit-log
Command: npx skills add https://github.com/WrongStack/WrongStack --skill audit-log-wrongstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify patterns, anomalies, and operational insights from WrongStack session logs, event streams, and system traces.

Core Features & Use Cases

  • Analyze session-level and cross-session logs to surface usage patterns, recurring errors, and cost trends.
  • Generate structured audit reports that prioritize issues and enable rapid remediation.
  • Use cases include investigating spikes in tool usage, identifying failing workflows, and tracking cost per iteration.

Quick Start

Run audit on a session JSONL file to generate an actionable report.

Frequently Asked Questions about audit-log

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

FAQPage Schema
How do I analyze JSONL session logs to find usage patterns and errors?

You can analyze session logs by parsing JSONL files to extract iterations, tool calls, errors, and costs. This produces a structured markdown audit report that surfaces recurring failures and usage patterns across one or more sessions.

What is the best way to track cost trends and anomalies in session logs?

Tracking cost trends in session logs involves analyzing cross-session event streams to extract cost per iteration data. Generating a structured audit report flags anomalies and operational insights, enabling rapid remediation of cost spikes.

Can I use this to investigate spikes in tool usage across multiple sessions?

Yes, you can investigate spikes in tool usage by running cross-session analysis on JSONL log streams and system traces. The analysis extracts tool call data to identify anomalies and generate a structured markdown audit report.

How do I generate a structured audit report from system traces?

Generating a structured audit report from system traces requires parsing log streams to extract iterations and errors. The process identifies recurring failures and outputting an actionable markdown document that prioritizes issues for rapid remediation.

Does this work with JSONL log files from WrongStack sessions?

Yes, it works directly with WrongStack session JSONL log files. The tool parses the logs to extract tool usage, errors, and cost trends, producing a structured markdown audit report that flags recurring failures and operational anomalies.