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.
92%
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 with gh as
the person. Writing a ticket for the factory
says how to find the factory's label, what an issue says, and how to size and
order a batch. Read it first.
gh auth status and gh repo view --json nameWithOwner. When gh
is missing or not logged in, ask the person to install it or run
gh auth login, and wait.Blocked by #<n> line to the body. File blockers first so their numbers
exist.gh issue create --title <title> --body-file <file> --assignee @me --label <label>. Write the body to a file outside the
repository. An issue with a Blocked by line gets the label too: Tessl
waits for its blockers and starts it when they close. To park an issue
until the person decides, leave the label off; adding it later with
gh issue edit <n> --add-label <label> starts the work.