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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clerk-core-workflow-a81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 that clearly identifies its niche (Clerk authentication) and provides explicit trigger guidance. The main weakness is that the capability list could be more comprehensive with specific actions like 'configure redirect URLs', 'customize Clerk components', or 'handle session tokens'. The explicit trigger terms section is a strong feature that aids skill selection.
Suggestions
Expand specificity by listing more concrete actions such as 'configure Clerk components', 'handle user sessions', 'set up webhooks', or 'manage redirect URLs'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk authentication) and some actions ('sign-up and sign-in flows', 'customizing sign-in experience', 'OAuth social login'), but doesn't list comprehensive concrete actions like specific UI components, session management, or redirect handling. | 2 / 3 |
Completeness | Clearly answers both what ('Implement user sign-up and sign-in flows with Clerk') and when ('Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'clerk sign-in', 'clerk sign-up', 'clerk login flow', 'clerk OAuth', 'clerk social login', plus implicit terms like 'authentication UI'. These are realistic phrases developers would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by specifying 'Clerk' as the authentication provider throughout. The explicit Clerk-prefixed trigger terms ('clerk sign-in', 'clerk OAuth') clearly distinguish this from generic auth skills or other auth providers like Auth0 or Firebase Auth. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent code examples covering multiple authentication patterns. The main weaknesses are minor verbosity (the Output section, generic overview) and missing validation checkpoints between steps. The error handling table is a good addition but could be integrated into the workflow steps themselves.
Suggestions
Remove the 'Output' section - the outcomes are self-evident from the code examples
Add validation checkpoints between steps (e.g., 'Test sign-in works before implementing OAuth', 'Verify OAuth callback URL is configured in dashboard before testing')
Trim the Overview section or remove it entirely - the Prerequisites section already provides necessary context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary elements like the 'Output' section listing obvious outcomes and could be tighter in places (e.g., the overview adds little value). | 2 / 3 |
Actionability | Provides fully executable TypeScript code for all authentication scenarios - pre-built components, custom forms, OAuth, and email verification. All examples are copy-paste ready with proper imports and complete implementations. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints. For authentication flows that can fail in multiple ways, there's no guidance on testing/verifying each step works before proceeding to the next. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate external resource links, and a clear pointer to the next skill for session management. Content is appropriately scoped without unnecessary nesting. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.