Set up a Tessl factory on a repository: Tessl agents that turn tickets into pull requests, answer reviews and fix checks on them, and review every pull request. Use when someone wants Tessl agents to do work in their repo, or asks what a factory is. To explain or change a factory that exists, use the understand-factory and change-factory skills.
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
The canonical home for this skill is tessl/factory-setup
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
The skill sets up Tessl automated cloud factories, creating projects and configuring automations via API (`tessl api -X POST /v1/projects`) and CLI commands, which consume Tessl service usage credits and manage repository workflows. It describes setting up cloud environments and triggering tasks that utilize credits, but does not handle direct financial transactions, charges, or transfers of funds. Therefore, it constitutes an indirect financial/usage metering scope without direct payment execution, resulting in an indirect classification.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The factory setup agent reads repository contents, open issues, and pull request history from GitHub during runtime to configure and test Tessl automations.
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.