clerk-incident-runbook

Manage incident response for Clerk authentication issues. Use when handling auth outages, security incidents, or production authentication problems. Trigger with phrases like "clerk incident", "clerk outage", "clerk down", "auth not working", "clerk emergency".

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

80%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 runbook is actionable and token-efficient with strong executable examples, but its multi-step destructive workflows lack explicit validation checkpoints and it fails to route to the existing implementation-guide.md reference, leaving content inline that should be split out.

Suggestions

Add explicit validation/verification checkpoints to destructive steps — e.g., after enabling emergency bypass, verify auth is restored before disabling it; after key rotation, run a health check before declaring resolution.

Link references/implementation-guide.md from the body (e.g., a '## Advanced procedures' section pointing to it) and move the duplicated bypass/session-revoke code out of SKILL.md into that reference.

Make Step 3 key rotation executable instead of commented-out vercel commands, or clearly justify why it is left as manual steps.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-dense — triage scripts, middleware, and endpoint code with tables — and assumes Claude's competence without explaining concepts Claude already knows.	3 / 3
Actionability	Most steps ship copy-paste-ready executable code (triage bash script, middleware bypass, session-revocation route), with specific commands; only Step 3 key rotation leans on commented-out vercel commands, which keeps it just at 3 rather than clearly above.	3 / 3
Workflow Clarity	Steps 1–6 are clearly sequenced, but destructive/batch operations (emergency bypass, mass session revocation, key rotation) lack explicit validate→fix→retry checkpoints, which per the rubric caps workflow clarity at 2.	2 / 3
Progressive Disclosure	A references/implementation-guide.md bundle exists but is never linked or signaled from the body, and substantial inline content (bypass middleware, session revoke) overlaps with what that file already covers — structure is present but references are not clearly signaled.	2 / 3
	Total	10 / 12 Passed

Description

90%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 well-formed: it states the capability, gives an explicit Use-when clause, and lists natural trigger phrases in third person. Its only weakness is that the named actions are scenario categories rather than concrete operations, keeping specificity at 2.

Dimension	Reasoning	Score
Specificity	Names the domain ("Clerk authentication issues") and several actions ("Manage incident response", "handling auth outages, security incidents"), but the verbs are abstract scenario categories rather than the concrete operations a level-3 example would list.	2 / 3
Completeness	Explicitly answers both what ("Manage incident response for Clerk authentication issues") and when ("Use when handling auth outages, security incidents, or production authentication problems") with explicit trigger guidance.	3 / 3
Trigger Term Quality	Provides natural phrases a user would actually say ("clerk incident", "clerk outage", "clerk down", "auth not working", "clerk emergency") with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Clerk-authentication niche with Clerk-specific trigger phrases is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 13 / 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
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/clerk-pack/skills/clerk-incident-runbook/SKILL.md
Commit: 4c47e33

Reviewed: 3 days 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.