tessl-labs/tessl-skill-review-ci
Implements Tessl skill review CI/CD pipelines through an interactive, configuration-first wizard. Supports GitHub Actions, Jenkins, and Azure DevOps.
70
90%
Does it follow best practices?
Impact
50%
0.67xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
tessl-skill-review-ci-review.md
tessl-skill-review-ci
Average Score: 88% | Validation: PASSED
Validation Checks
| Check | Status | Detail |
|---|---|---|
| skill_md_line_count | PASSED | SKILL.md line count is 313 (<= 500) |
| frontmatter_valid | PASSED | YAML frontmatter is valid |
| name_field | PASSED | 'name' field is valid: 'tessl-skill-review-ci' |
| description_field | PASSED | 'description' field is valid (222 chars) |
| body_present | PASSED | SKILL.md body is present |
Description -- 90%
| Criterion | Score | Detail |
|---|---|---|
| specificity | 2/3 | Names the domain (automated skill review pipelines, CI/CD) and mentions some actions (setting up, configuring, adding PR checks, migrating), but lacks concrete specific actions like 'create workflow files', 'configure scoring thresholds', or 'set up webhook triggers'. |
| trigger_term_quality | 3/3 | Good coverage of natural terms users would say: 'CI/CD', 'PR checks', 'GitHub Actions', 'Jenkins', 'Azure DevOps', 'skill review', 'pipelines', 'workflow'. |
| completeness | 3/3 | Clearly answers both what (setting up pipelines, configuring CI/CD, adding PR checks, migrating workflows) and when ('Use when setting up...') with explicit trigger scenarios. |
| distinctiveness_conflict_risk | 3/3 | Very specific niche combining 'Tessl skill scoring' with CI/CD platforms. Unlikely to conflict with general CI/CD or general skill-related skills. |
Assessment: Well-structured description that leads with explicit 'Use when' triggers and covers multiple specific scenarios. The platform support adds valuable specificity. The main weakness is that capabilities could be more concrete -- it describes contexts rather than specific actions.
Content -- 85%
| Criterion | Score | Detail |
|---|---|---|
| conciseness | 2/3 | Reasonably efficient but includes unnecessary verbosity, such as explaining what each CI platform is (GitHub-hosted runners, Jenkinsfile declarative pipeline) which Claude already knows. |
| actionability | 3/3 | Concrete, executable commands throughout (git commands, file paths, JSON structures). Step-by-step actions are specific and copy-paste ready. |
| workflow_clarity | 3/3 | Excellent multi-step workflow with clear phases, explicit validation checkpoints, confirmation gates before execution, and safety notes for git operations. |
| progressive_disclosure | 3/3 | Well-structured with clear overview pointing to one-level-deep references (github-actions.md, jenkins.md, azure-devops.md, TESTING.md). |
Assessment: Well-structured skill with excellent workflow clarity and progressive disclosure. The multi-phase wizard approach with explicit validation steps and confirmation gates is exemplary. Minor verbosity in explaining CI platform basics could be trimmed.
Suggestions
- Add more concrete action verbs describing what the skill does, e.g., 'Creates workflow YAML files, configures scoring thresholds, sets up webhook integrations'
- Remove explanatory text about CI platforms since Claude already knows these details
- Condense the 'When to Use This Skill' section into the overview or remove it entirely
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6