clerk-ci-integration
Configure Clerk CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Clerk tests into your build process. Trigger with phrases like "clerk CI", "clerk GitHub Actions", "clerk automated tests", "CI clerk", "clerk pipeline".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clerk-ci-integration88
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 with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is that the capabilities could be more specific about what concrete actions the skill enables (e.g., specific workflow configurations, test setup steps). The explicit trigger phrases section is a strong pattern that aids skill selection.
Suggestions
Add more specific concrete actions like 'create GitHub Actions workflow files', 'configure Clerk test environment variables', or 'set up mock authentication for tests' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk CI/CD, GitHub Actions, testing) and some actions (configure, setting up, integrating), but lacks specific concrete actions like 'create workflow files', 'configure test runners', or 'set up environment variables'. | 2 / 3 |
Completeness | Clearly answers both what (configure Clerk CI/CD integration with GitHub Actions and testing) and when (setting up automated testing, configuring CI pipelines, integrating tests). Includes explicit 'Use when' clause and 'Trigger with phrases' section. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'clerk CI', 'clerk GitHub Actions', 'clerk automated tests', 'CI clerk', 'clerk pipeline'. Good coverage of variations users might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Clerk + CI/CD + GitHub Actions. The explicit Clerk-specific triggers ('clerk CI', 'clerk GitHub Actions') make it unlikely to conflict with generic CI/CD skills or other authentication provider skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%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, actionable skill with complete, executable code examples for setting up Clerk CI/CD integration. The content is well-organized and token-efficient. The main weakness is the lack of explicit validation steps - there's no guidance on how to verify the CI pipeline works correctly or troubleshoot common setup issues before committing.
Suggestions
Add a validation step after Step 1 explaining how to verify the workflow runs successfully (e.g., 'Push a test commit and check the Actions tab for green status')
Include a troubleshooting workflow: 'If tests fail in CI but pass locally, check: 1) All secrets are set, 2) Test user exists, 3) Environment variables match'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary configuration and code without explaining what GitHub Actions, Playwright, or CI/CD concepts are. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | All code examples are complete and copy-paste ready - full YAML workflow files, TypeScript configurations, and test helpers. No pseudocode or vague instructions. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints. No guidance on verifying the workflow works before proceeding, or what to do if tests fail in CI. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate use of tables for error handling, and external resource links. Content is appropriately scoped for a single skill file with clear navigation to next steps. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
68%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_voice | 'description' should use third person voice; found second person: 'your ' | Warning |
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 | 11 / 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.