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
A timeline tells the person what is done and what is left, one line per stage, each starting with its status mark:
✓ done: what you did and what the person decided, in one short sentence,
naming the real things you created or found. Link pull requests and issues.● now: the stage you are on.◐ waiting on you: the person has to do something outside this session.
Say what.○ to do: what the stage does.⊘ skipped: say why in a few words.Use these marks, not emoji, as a list under the timeline's heading. Keep it short, do not repeat details the person has just seen, and never put a token or other secret in it.