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".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 well-structured skill description with explicit trigger guidance and clear 'when' clauses that make it easy for Claude to select appropriately. Its main weakness is that the capability list could be more comprehensive—it mentions sign-up, sign-in, and OAuth but doesn't detail other specific actions like component customization, session management, or middleware setup. The Clerk-specific trigger terms make it highly distinctive.
Suggestions
Expand the capability list with more specific actions, e.g., 'configure Clerk middleware, customize sign-in/sign-up components, handle session tokens, set up multi-factor authentication'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk authentication) and some actions (sign-up, sign-in flows, OAuth social login), but doesn't list comprehensive concrete actions like session management, redirect handling, or specific component usage. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement sign-up/sign-in flows with Clerk) and 'when' (explicit 'Use when' clause for authentication UI, customizing sign-in, implementing OAuth, plus a 'Trigger with' clause listing specific phrases). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'clerk sign-in', 'clerk sign-up', 'clerk login flow', 'clerk OAuth', 'clerk social login', plus broader terms like 'authentication UI' and 'customizing sign-in experience'. These cover common variations users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific 'Clerk' branding throughout. The trigger terms are all Clerk-prefixed, making it very unlikely to conflict with generic auth skills or other auth provider skills (e.g., Auth0, Firebase Auth). | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent executable code examples covering the full spectrum of Clerk authentication flows. The workflow progression from pre-built to custom components is logical and well-structured. The main weakness is length — at 250+ lines with full component code including styling classes, it could benefit from trimming non-essential details or splitting advanced flows into separate files.
Suggestions
Trim CSS className details from code examples (e.g., 'flex min-h-screen items-center justify-center') — Claude can generate appropriate styling without being told specific Tailwind classes.
Consider moving Steps 4-5 (email verification, MFA) into a separate referenced file to reduce the main skill's token footprint while keeping Steps 1-3 as the core quick-start content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides substantial executable code which is valuable, but is quite long (~250+ lines). Some sections like the full JSX with className styling details are verbose and could be trimmed. The Enterprise Considerations section adds useful but somewhat padded bullet points. Overall mostly efficient but could be tightened. | 2 / 3 |
Actionability | Excellent actionability — every step includes fully executable TypeScript code with proper imports, file paths, error handling, and state management. The code is copy-paste ready for Next.js + Clerk projects, covering pre-built components, custom forms, OAuth, email verification, and MFA. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from quick start (pre-built components) through progressively more complex flows (custom forms, OAuth, email verification, MFA). Each step builds logically on the previous one, with Step 2's MFA branch explicitly referencing Step 5. The error handling table provides clear recovery guidance. The verification flow in Step 4 has an explicit two-phase process (form → verify). | 3 / 3 |
Progressive Disclosure | The skill has good structure with clear sections and a reference to the next workflow skill. However, the content is quite long and monolithic — the custom sign-in form, OAuth, sign-up with verification, and MFA could potentially be split into separate referenced files. The Resources section provides external links, but the inline content is heavy for a single SKILL.md. | 2 / 3 |
Total | 10 / 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
70e9fa4
- 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.