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".
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-ci-integration/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 solid skill description that clearly defines its niche at the intersection of Clerk and CI/CD. It provides explicit trigger phrases and clear 'when to use' guidance. The main weakness is that the specific capabilities could be more concrete—listing actual actions like 'generate GitHub Actions workflow files' or 'configure test environment variables' would strengthen it. Note: the description uses second person ('your build process') which is a minor style issue.
Suggestions
Replace 'your build process' with third-person phrasing like 'the build process' to follow the recommended voice guidelines.
Add more concrete actions such as 'generate GitHub Actions workflow YAML files, configure Clerk test environment variables, set up test authentication tokens' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk CI/CD with GitHub Actions and testing) and some actions (setting up automated testing, configuring CI pipelines, integrating tests into build process), but the actions are somewhat generic and not highly concrete—no specific steps like 'create workflow files' or 'configure test runners' are mentioned. | 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 Clerk tests into build process) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'clerk CI', 'clerk GitHub Actions', 'clerk automated tests', 'CI clerk', 'clerk pipeline' which are natural terms users would say. Also includes broader terms like 'automated testing', 'CI pipelines', and 'build process'. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Clerk' + 'CI/CD' + 'GitHub Actions' creates a very specific niche that is unlikely to conflict with generic CI/CD skills or generic Clerk skills. The trigger terms are well-scoped to this particular intersection. | 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 solid, highly actionable skill with complete, executable code for every step of Clerk CI integration. Its main weaknesses are the lack of explicit validation checkpoints in the workflow (important for CI/secrets configuration) and the monolithic structure that could benefit from splitting detailed examples into referenced files. Minor verbosity in the Output section and some structural choices prevent top scores.
Suggestions
Add explicit validation checkpoints after key steps, e.g., 'Run `gh secret list` to verify secrets are configured' after Step 2, and 'Run `npx playwright test auth.setup.ts` locally to verify auth state saves correctly' after Step 3.
Split the E2E test examples (Step 5), seed script (Step 6), and Vitest mock example into separate referenced files to improve progressive disclosure and reduce the main file length.
Remove the 'Output' bullet list section as it merely restates what the steps already demonstrate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary sections like the 'Output' bullet list which just restates what the steps already cover, and the 'Next Steps' section adds little value. The content could be tightened by removing redundant summaries. | 2 / 3 |
Actionability | Every step provides fully executable, copy-paste ready code: complete GitHub Actions YAML, Playwright config, auth setup, E2E test examples, seed script, and even a Vitest mock example. Secrets are clearly enumerated in a table with expected value formats. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-6) and logically ordered, but there are no explicit validation checkpoints or feedback loops. For a CI pipeline setup involving secrets and auth state, there should be verification steps (e.g., 'verify secrets are accessible by running a test workflow' or 'validate auth state was saved correctly before proceeding'). | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headings and sections, but it's quite long (~180 lines of substantive content) and could benefit from splitting detailed examples (E2E tests, seed script, Vitest mock) into separate referenced files. The error handling table and resources section are well-placed, but the monolithic structure could be improved. | 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
3e83543
- 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.