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
Write issues the factory can build without asking, and file them in Linear as the person. Writing a ticket for the factory says how to find the state and delegate the factory starts on, what an issue says, and how to size and order a batch. Read it first.
LINEAR_API_KEY. With neither, ask the person to
connect a Linear MCP server or set a key, and wait.tessl api /v1/orgs/<org id>/integrations/linear/routes
lists which Linear team runs in which project: take the team whose
projectId is this project. A linearTeamId of * routes every team
without a route of its own. When more than one team fits, ask which.unstarted. When the team has more than one, use its first by
position. Its name is often Todo but need not be, and a state named Todo
of another type is not it.
blocked by relations, then make one update that sets Tessl as delegate
and moves it to the start state.