Claude
Skill
audit-logger
Keep a clear audit trail of actions, tools used, actors, outcomes, and errors for sensitive work. Use for compliance-sensitive tasks, incidents, or when the user asks what changed.
Virus-scanned
Reviewed automatically before listing.
Download
navinspire-ia-navin-navin_skills_audit-logger-e9c73a3.zip · 0 KB
Install
skills CLI
npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/audit-logger
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart
Git
git clone https://github.com/Navinspire-ia/navin.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Audit Logger
Overview
For sensitive operations, produce a concise audit record the user can keep.
Record fields
| Field | Content |
|---|---|
| When | ISO timestamp |
| Who | user / channel / session |
| Action | what was attempted |
| Tools | tools + key args (redact secrets) |
| Target | systems / paths / tickets |
| Result | success / failure / partial |
| Error | message if any |
Workflow
- Before the work: note the intent.
- During: prefer tools that leave artifacts (PRs, tickets, log files).
- After: write an Audit summary in the reply (and optionally a file the user chooses, e.g.
audit/YYYY-MM-DD.mdin the workspace). - Never log raw secrets or full credential headers.
Template
## Audit
- time: ...
- action: ...
- tools: ...
- result: ...
- notes: ...
Files (navin)
-
SKILL.md 1.1 KB
--- name: audit-logger description: Keep a clear audit trail of actions, tools used, actors, outcomes, and errors for sensitive work. Use for compliance-sensitive tasks, incidents, or when the user asks what changed. metadata: {"navin":{"emoji":"📒","category":"security"}} --- # Audit Logger ## Overview For sensitive operations, produce a concise audit record the user can keep. ## Record fields | Field | Content | |-------|---------| | When | ISO timestamp | | Who | user / channel / session | | Action | what was attempted | | Tools | tools + key args (redact secrets) | | Target | systems / paths / tickets | | Result | success / failure / partial | | Error | message if any | ## Workflow 1. Before the work: note the intent. 2. During: prefer tools that leave artifacts (PRs, tickets, log files). 3. After: write an **Audit summary** in the reply (and optionally a file the user chooses, e.g. `audit/YYYY-MM-DD.md` in the workspace). 4. Never log raw secrets or full credential headers. ## Template ```markdown ## Audit - time: ... - action: ... - tools: ... - result: ... - notes: ... ```
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.