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".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

65%Weight 40%Scale 1-3

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

The body is highly actionable with complete, executable code and a clear six-step sequence, but it is verbose for the context window, lacks explicit validation feedback loops, and fails to surface its own bundle file. Tightening inline code and linking the implementation guide would lift the weaker dimensions.

Suggestions

Move the secondary Sentry config and the admin metrics endpoint into references/implementation-guide.md and link them from SKILL.md to improve progressive disclosure and reduce inline length.

Add explicit validation checkpoints to the webhook and database steps (e.g. verify the webhook signature before processing; confirm db writes succeeded before returning) to establish a validate→fix→retry feedback loop.

Trim inline comments and consolidate Steps 4's two code blocks to tighten conciseness without losing actionability.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient—executable TypeScript with no concept-explanation fluff—but runs ~295 lines across six full code blocks (two separate Sentry configs, a full metrics endpoint), some of which could be trimmed or moved to the bundle; it is longer than the lean 'every token earns its place' anchor warrants.	2 / 3
Actionability	Every step ships complete, executable TypeScript with file paths and real imports (e.g. lib/auth-logger.ts, clerkMiddleware, Sentry.init with a beforeSend scrubber), matching the 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	The six Steps are clearly sequenced and an Error Handling table exists, but there are no explicit validate→fix→retry checkpoints for the webhook and DB-write operations; the error handling is reactive rather than a feedback loop, which matches the 'sequence present but checkpoints missing or implicit' anchor.	2 / 3
Progressive Disclosure	Content is well-sectioned but largely monolithic—all six steps and full code live inline—while the existing references/implementation-guide.md bundle file is never linked from the body; per the guideline of scoring against actual bundle structure, content that should be split is inline and references are not signaled.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

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

The description is specific, complete, and well-triggered: it states concrete actions, an explicit 'Use when' clause, and a set of natural trigger phrases scoped to a clear Clerk-auth niche. It is concise without padding and uses third person throughout.

Dimension	Reasoning	Score
Specificity	It lists multiple concrete actions—"monitoring, logging, and observability" and "audit logging"—against the specific Clerk-authentication domain, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It explicitly answers both what ("Implement monitoring, logging, and observability for Clerk authentication") and when ("Use when setting up monitoring, debugging auth issues in production, or implementing audit logging") with explicit triggers.	3 / 3
Trigger Term Quality	It provides a dedicated trigger set—"clerk monitoring", "clerk logging", "clerk observability", "clerk metrics", "clerk audit log"—covering natural terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The Clerk-specific niche plus distinct Clerk-prefixed triggers make it unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/clerk-pack/skills/clerk-observability/SKILL.md
Commit: 0540a62

Reviewed: about 6 hours ago

Table of Contents

Discovery Implementation Validation

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.