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
{
"context": "scenario-5",
"type": "weighted_checklist",
"checklist": [
{
"name": "C01",
"description": "The score quality gate block (the 'if [[ \"$AVG_SCORE\" -lt 80 ]]' conditional and its body) has been removed from the workflow.",
"max_score": 16
},
{
"name": "C02",
"description": "The PR comment footer has been changed from enforcement text ('skills scoring below 80% will fail the check') to informational text ('Review score is informational' or similar).",
"max_score": 16
},
{
"name": "C03",
"description": "The enforcement footer text ('scoring below 80%') is no longer present in the workflow file.",
"max_score": 12
},
{
"name": "C04",
"description": "The workflow YAML file still exists at ~/project/.github/workflows/tessl-skill-review.yml and is valid YAML (not broken by the edits).",
"max_score": 10
},
{
"name": "C05",
"description": "The workflow retains its original triggers (pull_request on main, push on main, workflow_dispatch).",
"max_score": 10
},
{
"name": "C06",
"description": "The workflow retains its original permissions (contents: write, pull-requests: write).",
"max_score": 8
},
{
"name": "C07",
"description": "The validation failure logic still works: the pipeline can still fail when PASSED is 'false' (validation failure), just not on low scores alone.",
"max_score": 12
},
{
"name": "C08",
"description": "The PR comment body still includes the '<!-- tessl-skill-review -->' HTML marker.",
"max_score": 8
},
{
"name": "C09",
"description": "The cache file at ~/project/.github/.tessl/skill-review-cache.json is unchanged — still contains the existing 'skills/onboarding' entry and 'last_updated' timestamp.",
"max_score": 8
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6