CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

audit-log

Durable, access-scoped, append-only record of who changed what app data, when, and whether it was the agent or a human. Use when adding an activity feed or change history, declaring what a mutating action targets, auditing sensitive reads, or answering "what did the agent change / who edited this".

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable and dense with framework specifics, and each task path is unambiguous, but the skill is a monolithic single file: the internal attribution/frame mechanics inflate the token budget and belong in a reference file. Splitting the deep implementation rules out of SKILL.md would fix both the conciseness and progressive-disclosure weaknesses at once.

Suggestions

Move the 'Approval and an audit override belong to one invocation', 'Attribution comes from one helper', and 'Client and approval' internals into a references/attribution.md file, keeping only the one-line rule ('call auditAttribution at write time; never hand-build attribution') in SKILL.md.

Add an explicit end-to-end sequence for the headline task (e.g., 'Build an activity feed': call list-audit-events via useActionQuery → page with nextOffset/hasMore → open a row with get-audit-event) so the primary workflow is a numbered path, not scattered facts.

Trim the 'Probes' and 'Outside agents' default bullets to one line each in SKILL.md, or fold them into a defaults reference table with the visibility table.

DimensionReasoningScore

Conciseness

Most sections are dense and high-value (defaults list, visibility table, 'Never' rules), but a few bullets are seriously bloated — the 'Approval and an audit override belong to one invocation' bullet runs ~40 lines of internal mechanics (execution frames, ACTION_EXECUTION_KEY, action-frame.ts, async-local storage) that reads as maintainer documentation. It matches 'mostly efficient but could be tightened' rather than 'noticeably verbose with several padded sections', since it never explains concepts Claude already knows.

3 / 5

Actionability

Guidance is fully executable: two near copy-paste code blocks (defineAction with audit.target, orgAdminAudit/recordOrgAdminAuditEvent with imports), exact action names and filter parameters (list-audit-events, sinceMs/beforeMs, scope: 'organization'), specific env vars (AGENT_NATIVE_AUDIT_RETENTION_DAYS, AGENT_NATIVE_AUDIT_ENABLED), and concrete file paths. The common cases (declare a target, opt reads in/out, read the log, export) are each covered with specifics.

5 / 5

Workflow Clarity

Every task path is unambiguous — shared change → declare target; sensitive read → onRead: true; org change → orgAdminAudit helpers; reading → list-audit-events with named filters; OCSF export has explicit cursor/checkpoint handling ('store every returned nextCursor, including on empty pages'). It sits just below the top anchor because there is no explicit end-to-end sequence for the headline 'build an activity feed' task, though this is a config/reference skill rather than a destructive multi-step workflow, so no validation cap applies.

4 / 5

Progressive Disclosure

Section headers are clear, but there are no bundle reference files at all — everything, including deep attribution/execution-frame internals that clearly belong in a separate reference document, is inlined in a ~250-line SKILL.md. This matches 'some structure but content that should be separate is inline'; it cannot reach the 'references mostly clear' anchor because no references exist.

3 / 5

Total

15

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete, third-person, with an explicit 'Use when' clause containing natural trigger phrases including quoted user questions. The only weakness is slight overlap risk with generic logging/telemetry skills, which the skill body itself disambiguates.

DimensionReasoningScore

Specificity

The description states concrete properties ('Durable, access-scoped, append-only record of who changed what app data, when, and whether it was the agent or a human') and lists multiple specific capabilities (declare what a mutating action targets, audit sensitive reads, add an activity feed or change history), matching the comprehensive-coverage anchor. It stays in third person and never falls back to generic language.

5 / 5

Completeness

It explicitly answers both questions: the 'what' is the durable, access-scoped, append-only record with agent-vs-human attribution, and an explicit 'Use when...' clause gives concrete trigger scenarios including quoted user questions. This matches the top anchor exactly.

5 / 5

Trigger Term Quality

Natural user phrasings appear verbatim — 'activity feed', 'change history', 'who edited this', 'what did the agent change', 'auditing sensitive reads' — covering the synonym space a user would actually say when needing this skill. No common variation of the domain's vocabulary is missing.

5 / 5

Distinctiveness Conflict Risk

The audit-trail niche (who changed what app data, agent vs human) is distinct with specific triggers, but the broad 'record/audit' vocabulary leaves minor overlap risk with general logging, observability, or analytics skills. It is well above the 'could still overlap with similar skills' midpoint anchor.

4 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

BuilderIO/agent-native

Path

.agents/skills/audit-log/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.