← Back to Skills Marketplace
lethehades

Agent Audit Log

by lethehades · GitHub ↗ · v0.1.0 · MIT-0
cross-platform ✓ Security Clean
535
Downloads
0
Stars
2
Active Installs
1
Versions
Install in OpenClaw
/install agent-audit-log
Description
Lightweight operational audit logging for AI assistants, agent workspaces, and personal automation systems. Use when you need a structured way to record high...
README (SKILL.md)

Agent Audit Log

Create and maintain a lightweight audit trail for high-value actions.

Core rule

Log only actions that matter for safety, traceability, or later review. Do not turn the audit log into noise.

Default layers

  1. Raw fact log (YYYY-MM-DD.jsonl)
  2. Date summary (index.json)
  3. Target/project index (by-target.json)
  4. Risk index (by-risk.json)
  5. Human-readable summary (latest.md)
  6. Export-safety events (export_safety_check)
  7. Open items (open-items.json)
  8. Status transition history (open-items-history.json)

Read references as needed

  • Read references/schema.md for the log schema and event fields.
  • Read references/risk-model.md for how to classify low / medium / high risk.
  • Read references/export-safety.md before logging publish/export actions.
  • Read references/open-items.md when tracking unresolved risks or follow-up work.
  • Read references/examples.md when you need concrete event, export-safety, or open-item examples.

Use scripts as needed

  • Use scripts/init_audit.sh to create the basic audit directory and starter files.

Operating rules

  • Do not store plaintext secrets in audit logs.
  • Prefer concise, human-readable summaries.
  • Record target, result, and non-sensitive references.
  • Use warn when something needs attention but did not fail.
  • Use open items for follow-up risk, not for routine noise.
Usage Guidance
This skill appears safe and does what it claims: initializes a local audit directory and provides a schema and examples. Before use: (1) run scripts/init_audit.sh in a test directory to verify behavior; (2) ensure the audit directory is stored with appropriate file permissions and retention policies (logs can be sensitive); (3) never log plaintext secrets — follow the README guidance and redact or reference secrets rather than storing them; (4) be aware that other skills or workflows could later read or transmit these logs, so control which agents or services have access to the logs. If you need remote centralized logging, implement secure, explicit export steps rather than relying on this skill alone.
Capability Analysis
Type: OpenClaw Skill Name: agent-audit-log Version: 0.1.0 The agent-audit-log skill is a legitimate utility designed to help AI agents maintain a structured audit trail of their actions. It includes a simple shell script (scripts/init_audit.sh) for directory initialization and comprehensive documentation (references/) for risk modeling and export safety, which actually encourages the exclusion of sensitive data like credentials and local logs from public exports.
Capability Assessment
Purpose & Capability
Name/description (lightweight audit log) match the files and runtime instructions. All referenced files (schema, examples, risk model) are present and relevant; nothing in the manifest suggests unrelated capabilities or external services are required.
Instruction Scope
SKILL.md stays on-topic: it instructs how to structure logs, which local reference files to read, and to use the included init script. It explicitly warns not to store plaintext secrets. It does not instruct reading unrelated system files, environment variables, or sending data to external endpoints.
Install Mechanism
There is no install spec (instruction-only) and a single small bash script that only creates local directories/files. No downloads, package installs, or archive extraction are present.
Credentials
The skill requests no environment variables, no credentials, and no config paths. The schema includes event kinds such as 'config_secret_injection' but the documentation explicitly advises not to store plaintext secrets; this is a legitimate logging schema choice rather than credential access.
Persistence & Privilege
The skill is not forced always-on (always:false) and does not request elevated or cross-skill configuration changes. Its only persistence is creating local audit files in a logs/audit directory under a provided root — standard and scoped behavior.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install agent-audit-log
  3. After installation, invoke the skill by name or use /agent-audit-log
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
First public draft of a lightweight operational audit logging skill for AI assistants, agent workspaces, and personal automation systems.
Metadata
Slug agent-audit-log
Version 0.1.0
License MIT-0
All-time Installs 2
Active Installs 2
Total Versions 1
Frequently Asked Questions

What is Agent Audit Log?

Lightweight operational audit logging for AI assistants, agent workspaces, and personal automation systems. Use when you need a structured way to record high... It is an AI Agent Skill for Claude Code / OpenClaw, with 535 downloads so far.

How do I install Agent Audit Log?

Run "/install agent-audit-log" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Agent Audit Log free?

Yes, Agent Audit Log is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Agent Audit Log support?

Agent Audit Log is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Agent Audit Log?

It is built and maintained by lethehades (@lethehades); the current version is v0.1.0.

💬 Comments