Skills that Tessl factory loops run: implement a Linear or GitHub issue as a pull request, shepherd that pull request through review and checks, wake the shepherd for pull requests that a push to their base branch left in conflict, and keep the work in step when a person stops, ends, answers or closes it.
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {
"GITHUB_ISSUE_NUMBER": {
"type": "string",
"pattern": "^[1-9][0-9]*$",
"description": "The number of the issue to implement, in the repository the run is cloned from. Default: the issue the trigger events name."
},
"GITHUB_ISSUE_LABEL": {
"type": "string",
"minLength": 1,
"description": "The label that hands an issue to Tessl. Default: the label of the first trigger event, then tessl."
}
}
}