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
Quality
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 critically deficient across all dimensions. It provides only a skill name and category without explaining what the skill does, what actions it performs, or when it should be selected. The redundant trigger term ('audit trail helper' listed twice) suggests a template was not properly filled out.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Generates audit logs, tracks user actions, records data changes, creates compliance reports').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when tracking changes, logging activity, compliance reporting, or reviewing action history').
Remove the redundant trigger term and add varied natural keywords like 'audit log', 'activity tracking', 'compliance', 'change history', 'user actions'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Audit Trail Helper' is just a name, and 'Enterprise Workflows' is an abstract category with no explanation of what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 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 users would say. No domain-specific terms like 'logging', 'compliance', 'track changes', or 'history' are included. | 1 / 3 |
Distinctiveness Conflict Risk | 'Enterprise Workflows' is extremely generic and could overlap with countless other business-related skills. Without specific capabilities or triggers, there's no way to distinguish this from other enterprise or audit-related tools. | 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 essentially a placeholder with no substantive content. It describes what an audit trail helper skill might do but provides absolutely no actionable guidance, code examples, or concrete implementation details. The entire content could be replaced with actual audit trail patterns, logging code, compliance checklists, or database schema examples.
Suggestions
Add concrete code examples showing how to implement audit trail logging (e.g., database triggers, middleware patterns, or event sourcing examples)
Define a clear workflow for setting up audit trails: what to log, where to store it, how to query it, and how to validate completeness
Include specific audit trail schemas or data structures with field definitions (timestamp, actor, action, resource, before/after states)
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about audit trails. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual audit trail implementation. The content only describes what the skill claims to do without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The skill mentions 'step-by-step guidance' but provides none. There are no sequences, validation steps, or any actual process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples, and no structured navigation to actual implementation details. | 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
0c08951
- 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.