logging-best-practices
Logging best practices focused on wide events (canonical log lines) for powerful debugging and analytics
Install with Tessl CLI
npx tessl i github:boristane/agent-skills --skill logging-best-practicesOverall
score
71%
Validation for skill structure
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid logging skill with an excellent, actionable code example demonstrating the wide events pattern. The core principles are well-organized and the anti-patterns provide useful guardrails. However, there's redundancy between sections (anti-patterns restating principles), and the referenced rule files are mentioned without clear indication of their added value over the main content.
Suggestions
Remove the anti-patterns section or consolidate it into the core principles to reduce redundancy
Add a brief validation step showing how to verify logging is working (e.g., 'Test by checking your log aggregator for the expected fields')
Clarify what additional content exists in the referenced rules/*.md files to help readers decide whether to consult them
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation (e.g., 'also called canonical log lines', explaining what high cardinality means). The anti-patterns section largely restates what was already covered in core principles. | 2 / 3 |
Actionability | Provides a complete, executable TypeScript example demonstrating the wide events pattern with proper try/catch/finally structure. The code is copy-paste ready and shows exactly how to implement the pattern. | 3 / 3 |
Workflow Clarity | The 'When to Apply' section provides clear triggers, and the code example shows the workflow, but there are no explicit validation steps or checkpoints for verifying logging is working correctly. For a logging skill, some guidance on testing/validating log output would strengthen this. | 2 / 3 |
Progressive Disclosure | References to rules files (wide-events.md, context.md, etc.) suggest good structure, but these are mentioned at the end without clear signaling of what additional value they provide. The main content could be tighter with more detail pushed to referenced files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
93%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 15 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
Total | 15 / 16 Passed | |
- 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.