CtrlK
BlogDocsLog inGet started
Tessl Logo

clerk-core-workflow-a

Implement user sign-up and sign-in flows with Clerk. Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login. Trigger with phrases like "clerk sign-in", "clerk sign-up", "clerk login flow", "clerk OAuth", "clerk social login".

71

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

Highly actionable with complete, executable code and a clear step sequence, but the body is a token-heavy monolith that inlines full components while a bundle file sits unreferenced. Tightening the inline code and actually linking the implementation guide would lift both conciseness and progressive disclosure.

Suggestions

Trim the inline full React components to minimal, representative snippets and move the complete versions into references/implementation-guide.md, then link to it (e.g., 'See [implementation-guide.md](references/implementation-guide.md) for full component source').

Replace some inline component blocks with concise patterns/anchors (sign-in status handling, OAuth redirect flow) to reduce the ~330-line body while preserving actionability.

Add a one-line navigation pointer near the top pointing to the implementation guide and external Clerk docs so the SKILL.md reads as an overview rather than a self-contained dump.

DimensionReasoningScore

Conciseness

The body is mostly efficient and free of concept-explanation fluff, but it inlines five full React/TypeScript components (~330 lines) that could be tightened; a duplicate implementation-guide.md bundle exists yet is never referenced, leaving the body heavier than needed.

2 / 3

Actionability

Every step provides complete, copy-paste-ready executable code with real imports, state handling, and a concrete error-handling table — no pseudocode or vague direction.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Step 1 through Step 5) with cross-references such as 'MFA required — handled in Step 5' and status branching (complete/needs_second_factor/needs_identifier) acting as feedback paths; these are read-only UI flows so destructive-op validation checkpoints are not required.

3 / 3

Progressive Disclosure

Sections are well-organized, but a references/implementation-guide.md bundle file exists and is never linked from the body, while content that could be split out remains inline as a monolithic component dump — references are present but not clearly signaled or used.

2 / 3

Total

10

/

12

Passed

Description

100%

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

A strong, third-person description that names concrete capabilities, gives an explicit 'Use when' clause, and lists natural trigger phrases scoped to Clerk. It is concise without fluff and clearly distinct from other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Implement user sign-up and sign-in flows with Clerk', 'building authentication UI', 'customizing sign-in experience', 'implementing OAuth social login' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what it does (implement sign-up/sign-in flows with Clerk) and when to use it via an explicit 'Use when building authentication UI...' clause plus trigger phrases.

3 / 3

Trigger Term Quality

Provides natural phrases a user would actually say: 'clerk sign-in', 'clerk sign-up', 'clerk login flow', 'clerk OAuth', 'clerk social login', covering common variations.

3 / 3

Distinctiveness Conflict Risk

Clerk-scoped triggers and a clear auth-UI niche make it unlikely to fire for unrelated skills; no overlap risk with generic skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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