Set up, understand, and change a Tessl factory on a repository: pick automations that fit how you work, such as shipping tickets as pull requests, answering reviews and fixing checks on those pull requests, code review, and scheduled jobs; prepare the repository for agents; write issues for the factory to build; then see what the factory has done, find out why a run failed or never started, and change or extend it.
91%
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
The factory actions run skills from tessl/factory. The user has two ways
to change what a skill does.
For a small change, keep the published skill and add instructions to the
action in tessl.json, for example "Run bun run lint before you push." The
user keeps getting fixes when tessl/factory is updated.
For a larger change, copy the skill into the repository and point the action
at the copy. The user owns the copy and no longer gets fixes from
tessl/factory. Tell the user this before you copy.
git init, write
{"name": "factory-copy", "dependencies": {}} to tessl.json, and run
tessl install tessl/factory --yes..tessl/plugins/tessl/factory/skills/<skill> from that directory
to tessl-factory/skills/<skill> in the repository.tessl-factory/.tessl-plugin/plugin.json with name set to
<workspace>/<repo>-factory, version 0.1.0, a one-line
description, private true, and a skills entry for each copied
skill. If the file exists, add the new skill
to its skills list.tessl.json, change the action's skill to
file:tessl-factory#<skill>.tessl doctor --automations.SKILL.md with the
write-factory-skill skill. Keep its "Invariants" section.The change takes effect after it merges to the default branch.