clerk-observability
Implement monitoring, logging, and observability for Clerk authentication. Use when setting up monitoring, debugging auth issues in production, or implementing audit logging. Trigger with phrases like "clerk monitoring", "clerk logging", "clerk observability", "clerk metrics", "clerk audit log".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/clerk-pack/skills/clerk-observability/SKILL.mdQuality
Discovery
89%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 is a solid skill description with excellent completeness and trigger term coverage. Its main weakness is that the capabilities listed are somewhat high-level categories (monitoring, logging, observability) rather than specific concrete actions. The explicit 'Use when' and 'Trigger with' clauses are well-structured and make it easy for Claude to select appropriately.
Suggestions
Add more specific concrete actions, e.g., 'Track authentication failures, configure webhook event logging, set up session monitoring dashboards, implement rate-limit alerting' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk authentication) and some actions (monitoring, logging, observability), but doesn't list specific concrete actions like 'track failed login attempts', 'set up webhook event logging', or 'configure error alerting'. The actions listed are broad categories rather than specific capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement monitoring, logging, and observability for Clerk authentication) and 'when' (setting up monitoring, debugging auth issues in production, implementing audit logging) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms: 'clerk monitoring', 'clerk logging', 'clerk observability', 'clerk metrics', 'clerk audit log'. Also includes contextual triggers like 'debugging auth issues in production'. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining Clerk authentication with monitoring/observability. The 'clerk' prefix on all trigger terms and the specific focus on auth monitoring makes it very unlikely to conflict with general monitoring skills or general Clerk skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable TypeScript code covering a comprehensive set of Clerk observability patterns. Its main weaknesses are the monolithic structure (all code inline rather than split across referenced files) and the lack of explicit validation/verification steps between stages of the setup process. The content could be tightened by removing the redundant Output section and adding verification checkpoints.
Suggestions
Add verification checkpoints after each step (e.g., 'Test: curl localhost:3000/api/health and confirm Clerk status is healthy') to improve workflow clarity.
Split detailed implementations (Sentry config, health check, metrics dashboard) into separate referenced files, keeping SKILL.md as a concise overview with links.
Remove the Output section which restates what the steps already describe, or convert it into a verification checklist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with substantial code blocks. Some code is reasonable as executable examples, but there's redundancy (e.g., the middleware step has issues with response handling that won't actually work in Next.js middleware, and some patterns could be more condensed). The Output section largely restates what the steps already cover. | 2 / 3 |
Actionability | Every step provides fully executable TypeScript code with specific file paths, imports, and concrete implementations. The code is copy-paste ready with real library APIs (Pino, Sentry, Clerk) and covers complete patterns from logging to health checks to metrics dashboards. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no validation checkpoints between steps. For a monitoring setup involving production infrastructure, there should be verification steps (e.g., 'verify logs appear', 'test health endpoint', 'confirm Sentry receives events'). The error handling table is helpful but doesn't constitute in-workflow validation. | 2 / 3 |
Progressive Disclosure | The content is largely monolithic with ~200 lines of inline code. The health check, metrics endpoint, and Sentry integration could reasonably be split into separate reference files. The 'Next Steps' reference to clerk-incident-runbook is good, but the main body would benefit from being an overview with links to detailed implementations. | 2 / 3 |
Total | 9 / 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
3e83543
- 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.