audit-trail-helper
Audit Trail Helper - Auto-activating skill for Enterprise Workflows. Triggers on: audit trail helper, audit trail helper Part of the Enterprise Workflows skill category.
34
0%
Does it follow best practices?
Impact
100%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/audit-trail-helper/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no substantive content. It fails on every dimension: it names no concrete actions, includes no natural trigger terms beyond its own repeated name, provides no 'Use when...' guidance, and is too generic to be distinguishable from other skills. It would be nearly impossible for Claude to correctly select this skill from a pool of available options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates audit trail logs, tracks entity changes, records user actions with timestamps, and produces compliance reports for enterprise systems.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about audit logs, change tracking, compliance reporting, activity history, or needs to trace who modified what and when.'
Remove the duplicate trigger term ('audit trail helper' is listed twice) and replace with varied natural language terms users would actually say, such as 'audit log', 'change history', 'compliance trail', 'activity tracking'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Audit Trail Helper' is a name, not a description of capabilities. There is no indication of what this skill actually does—no verbs describing specific actions like logging, tracking, generating reports, etc. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause, and the description only states the skill's name and category without explaining functionality or trigger conditions. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'audit trail helper' repeated twice, which is the skill's own name rather than natural keywords a user would say. Missing natural terms like 'audit log', 'compliance', 'change history', 'tracking changes', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's impossible to distinguish this skill from any other enterprise or audit-related skill. 'Enterprise Workflows' is extremely broad and provides no clear niche. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty placeholder that provides no actual value. It contains no actionable content, no code examples, no workflow steps, and no domain-specific knowledge about audit trails. Every section is generic boilerplate that could apply to any skill by swapping the name.
Suggestions
Add concrete, executable code examples showing how to implement audit trail logging (e.g., database schema for audit events, middleware for capturing changes, structured log formats).
Define a clear workflow for setting up audit trails: e.g., 1) identify auditable events, 2) implement capture mechanism, 3) validate trail completeness, 4) set up retention policies—with specific commands or configurations at each step.
Remove all generic filler sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual domain knowledge about audit trail patterns, compliance requirements (SOX, HIPAA, GDPR), and concrete implementation guidance.
Add references to detailed sub-files for specific audit trail topics (e.g., COMPLIANCE_STANDARDS.md, DATABASE_SCHEMA.md, INTEGRATION_PATTERNS.md) to provide progressive disclosure of complex enterprise workflow content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'audit trail helper' excessively, and provides zero substantive information about what an audit trail helper actually does or how to implement one. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no specific steps, no examples of audit trail structures or implementations. Every section is vague and abstract, describing capabilities without demonstrating any. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no sequences, no validation checkpoints, and no process to follow. | 1 / 3 |
Progressive Disclosure | The content is a flat, shallow placeholder with no meaningful structure. There are no references to detailed files, no layered content, and the sections that exist contain only generic filler text. | 1 / 3 |
Total | 4 / 12 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- 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.