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".
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-core-workflow-a/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 well-structured skill description with explicit trigger guidance and clear 'when' clauses that make it easy for Claude to select appropriately. The Clerk-specific focus provides strong distinctiveness. The main weakness is that the capability list could be more comprehensive—mentioning specific components, session management, or middleware configuration would strengthen specificity.
Suggestions
Expand the concrete actions to include more specific capabilities like 'configure Clerk middleware, embed <SignIn/> and <SignUp/> components, manage user sessions, set up redirect URLs' to improve specificity.
| 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 plus a 'Trigger with phrases' section listing specific triggers). | 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 natural user phrasing well. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the Clerk-specific focus. The trigger terms are all prefixed with 'clerk', making it very unlikely to conflict with generic auth skills or other authentication provider 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 is a highly actionable skill with complete, executable code examples covering the full spectrum of Clerk authentication flows. Its main weaknesses are length (could be more concise or better split across files) and the lack of explicit validation/testing checkpoints between steps. The error handling table and enterprise considerations add value but contribute to a somewhat monolithic document.
Suggestions
Add validation checkpoints after each step (e.g., 'Verify: navigate to /sign-in and confirm the component renders correctly before proceeding to Step 2')
Consider splitting Steps 2-5 into separate referenced files, keeping SKILL.md focused on the quick-start pre-built components with links to detailed custom implementation guides
Trim the Enterprise Considerations section — items like 'phone_code strategy instead of email_code' and 'magic link uses email_link' are one-liners that could be a brief reference table or moved to a separate file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with extensive code examples that are mostly necessary, but includes some unnecessary filler like the 'Enterprise Considerations' bullet list with vague mentions of features not fully explained, and the appearance styling details in Step 1 add bulk. The error handling table is useful but some entries are obvious to Claude. | 2 / 3 |
Actionability | All code examples are fully executable, copy-paste ready TypeScript/React components with proper imports, file paths, error handling, and state management. Each step provides complete, working implementations including the SSO callback page and environment variables. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from pre-built components through custom forms, OAuth, email verification, and MFA, with cross-references between steps (e.g., Step 2 references Step 5 for MFA). However, there are no explicit validation checkpoints — no guidance on how to verify each step works before proceeding, no testing instructions, and no feedback loops for debugging failed configurations. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headings and a logical progression, and references external docs and a next skill. However, the file is quite long (~200+ lines of code) and could benefit from splitting detailed implementations (custom sign-in, OAuth, MFA) into separate referenced files, keeping SKILL.md as a concise overview with the quick-start pre-built component approach. | 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
3a2d27d
- 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.