Nm Leyline Usage Logging
v1.0.0Consult this skill when implementing usage logging and audit trails
⭐ 0· 33·1 current·1 all-time
by@athola
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (usage logging, audit trails) align with the provided SKILL.md and module content. The skill documents session management, log schemas, read/write patterns, and query helpers — all coherent with a logging/audit helper.
Instruction Scope
Instructions and example code stay within logging concerns: creating/updating a session.json, appending/reading JSONL log files at ~/.claude/leyline/usage/{service}.jsonl, and query helpers. There are no instructions to call external endpoints, request unrelated system state, or exfiltrate data.
Install Mechanism
No install spec and no code files to execute beyond the included examples. As an instruction-only skill, it does not download or install external artifacts.
Credentials
The skill declares no required environment variables, credentials, or config paths. Its filesystem usage (per-user home directory logs) is proportional to the described function.
Persistence & Privilege
The skill is not always-enabled and does not request elevated or cross-skill configuration. Its persistent footprint (per-user log files under ~/.claude/leyline/usage/) is appropriate for a logging tool.
Assessment
This skill appears coherent and local-only, but note it writes and reads log files under your home directory. Before using: (1) ensure logs won't contain secrets or sensitive data, (2) set appropriate file permissions on ~/.claude/leyline/usage/ to limit access, (3) implement log rotation or retention to avoid unbounded growth, and (4) if you need centralized/secure storage, adapt the examples to send logs to a secure service rather than leaving them in plaintext. If you need further assurance, ask for the actual implementation (the UsageLogger class) to review exact IO and error handling behavior.Like a lobster shell, security has layers — review code before you run it.
latestvk97fvbav4gjfwrrjym4bhzzdgx84tv9y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🦞 Clawdis