| name | audit-logger |
| description | Automatically log all skill invocations to a local append-only audit file. This skill hooks into the session lifecycle and is not invoked directly by the user. |
| version | 1.0.0 |
| metadata | {"openclaw":{"requires":{"env":[],"bins":[]}},"tribe-security":{"network-egress":"none","file-access":"append-only to ~/openclaw-audit/audit.jsonl","review-status":"tribe-verified","scanner-result":"0 critical, 0 high, 0 medium","reviewed-by":"tribe-ai","reviewed-at":"2026-02-22"}} |
Audit Logger
A meta-skill that wraps other skill invocations and appends a structured log entry to a local append-only log file. This skill is not invoked directly — it hooks into the session lifecycle.
Behavior
On each skill invocation within the session, append a JSON line to ~/openclaw-audit/audit.jsonl with the following structure:
{
"timestamp": "2026-02-22T10:00:00Z",
"skill": "jira-task-creation",
"trigger": "create a Jira ticket for the auth bug",
"inputs": {},
"outputs": {},
"duration_ms": 1200
}
Each log entry must include:
- timestamp: ISO 8601 timestamp of when the skill was invoked
- skill: Name of the skill that was invoked
- trigger: The user input that triggered the skill
- inputs: Summary of inputs passed to the skill (redact sensitive values)
- outputs: Summary of outputs returned by the skill
- duration_ms: How long the skill execution took in milliseconds
Constraints
- The log file is append-only. Never modify or delete existing entries.
- Create the
~/openclaw-audit/ directory if it does not exist.
- Do NOT make any network calls. All logging is local.
- Do NOT read from the audit log — only append to it.
- For sensitive inputs (such as API keys or tokens), write only the key names to the log — redact all values.
- Each line must be valid JSON (JSON Lines format) for compatibility with log aggregation tools.
