Write and file a GitHub issue for the Tessl factory to turn into a pull request, with the person's own GitHub account. Use when someone wants Tessl to work on something in a repository whose factory takes GitHub issues, wants a task split into issues the factory builds in order, or asks how to write an issue for Tessl.
94%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
The canonical home for this skill is tessl/factory-setup
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.boranfurkan/discordlancer
a41c33b
Canonical home
since Nov 3, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.