CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

factory-setup

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.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

The canonical home for this skill is tessl/factory-setup

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary orchestration skill: a situation-driven loop with explicit done-state, copy-paste-ready commands with exact fields and expected responses, and disciplined gating of every risky action. The weaknesses are minor: a few over-stuffed sentences that trade clarity for density, and a bundle with one orphaned file and some second-level reference chains.

Suggestions

Link references/progress.md from somewhere (or remove it) — it is currently unreachable from SKILL.md and every other reference file.

Flatten the second-level reference chains: surface triggers.md, building-blocks.md, and customize.md directly from SKILL.md (e.g. from the 'Suggested next steps' or a 'What else you can ask for' section) rather than only via starters.md.

Split the longest sentences for readability — invariant 10 (Commands) and invariant 1 pack several rules into single 80–100 word sentences; separate sentences or bullets would preserve the same rules at lower reading cost.

DimensionReasoningScore

Conciseness

Nearly every line carries Tessl-specific, non-inferable knowledge (CLI quirks, API fields, timing behavior like 'keeps answering `missing` for up to five minutes'), with no padding about concepts Claude already knows. Not 5: a few passages are over-stuffed and would be clearer split up — e.g. the ~100-word invariant 10 sentence and the long parenthetical in invariant 1 — which is density rather than leanness.

4 / 5

Actionability

Fully executable throughout: exact commands ('tessl code repo update <owner/repo> --org <org id> --review-enabled --review-trigger every-push', 'gh api -X PATCH repos/<owner>/<repo> -F has_issues=true'), exact JSON bodies ('{"workspaceId": ..., "sourceType": "git", "sourceUri": ...}'), exact response fields to read ('usage.credits.state', 'meta.issuesEnabled', 'data.attributes.status') and expected values for each. Common cases, including error and refusal paths, are covered with the exact command to run.

5 / 5

Workflow Clarity

The situation loop is explicit — 'Read where things stand, take the first situation that applies, do its next action, and look again' — with a clear done-state, ordered situations 1–13, and validation checkpoints at each turn ('Confirm the Loops setup reported ... are listed and active', 'confirm with tessl code repo view ... --json'). Error-recovery feedback loops are present ('When it refuses, say the access can take a few minutes to show, and try again'; 'When either check gives no clear answer ... say you could not check it and go on'), and resume behavior is specified ('when starting and when resuming'). Risky operations (push, merge, turning on Issues) are gated on the person's explicit yes, so no validation cap applies.

5 / 5

Progressive Disclosure

SKILL.md is a genuine overview with well-signaled, purpose-stated one-level references, and every anchor link verified against the bundle (all four headings in set-up-in-tessl.md exist). Not 5: the actual bundle structure has gaps — references/progress.md is orphaned (linked from neither the body nor any reference file), and triggers.md, building-blocks.md, customize.md, and confirm-loops.md are only reachable via second-level links through starters.md and testing.md, so some content sits two levels deep.

4 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete capability list, explicit 'Use when' triggers, and clear routing to sibling skills for adjacent intents. Written in imperative/third-person voice with no fluff. Only minor room to broaden natural trigger phrasings.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'turn tickets into pull requests, answer reviews and fix checks on them, and review every pull request' — which comprehensively cover the factory's capabilities, and the routing line ('To explain or change a factory that exists, use the understand-factory and change-factory skills') explicitly handles the adjacent intents rather than leaving coverage gaps. Not 4: coverage gaps are addressed by explicit delegation, not merely minor.

5 / 5

Completeness

Explicitly answers both questions: what ('Set up a Tessl factory on a repository: ... turn tickets into pull requests, answer reviews and fix checks on them, and review every pull request') and when ('Use when someone wants Tessl agents to do work in their repo, or asks what a factory is'). This matches the anchor with concrete trigger phrases; nothing is left implicit.

5 / 5

Trigger Term Quality

Good natural-term coverage: 'Use when someone wants Tessl agents to do work in their repo, or asks what a factory is' captures the phrases an owner would naturally say ('Tessl agents', 'factory', 'repo'). Not 5: a few natural variations users might say are absent, e.g. 'automate my repository', 'set up automations', or 'review my pull requests' as a trigger phrasing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Tessl factory setup) with distinct triggers, and the description actively disambiguates the two nearest sibling skills ('To explain or change a factory that exists, use the understand-factory and change-factory skills'), minimizing wrong-skill triggering. Not 4: overlap risk is addressed explicitly, not just minor.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 suspicious

Warning

Total

15

/

16

Passed

Repository

boranfurkan/discordlancer

Path

.tessl/plugins/tessl/factory-setup/skills/factory-setup/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.