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-value actions such as installs, config changes, updates, repository operations, external publishing, secret injection, deletions, export-safety checks, and follow-up risks. Also use when designing or improving an audit trail with JSONL logs, risk levels, target indexes, human summaries, and open-item tracking.

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "agent-audit-log" with this command: npx skills add lethehades/agent-audit-log

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.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Security

Agent Causal

Helps decide to ship, continue, or roll back changes from A/B test and DiD data by providing statistical analysis, decisions, and audit trails.

Registry SourceRecently Updated
Security

Code Review Inspector

Automated code review checking for bugs, security issues, best practices, performance problems, and code style

Registry SourceRecently Updated
250Profile unavailable
Security

Docker Optimizer

Optimize Dockerfiles with multi-stage builds, layer caching, security best practices, and size reduction techniques

Registry SourceRecently Updated
260Profile unavailable
Security

Skill Auditor

Audit core: a classification taxonomy and a severity scoring function, kept orthogonal. Operates on the whole skill bundle (SKILL.md plus any referenced scri...

Registry SourceRecently Updated
1250Profile unavailable