CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

change-factory

Change or extend a Tessl factory that is already set up on this repository, and suggest what to add next. Use when someone wants to let a teammate start runs, change the model an automation uses, change what an automation does, change how Code Review behaves, stop or remove an automation, update the setup hook, change what the cloud environment can access, add another automation, set up Learn from past work so the factory learns from its mistakes, act on its findings, or asks what they should add to their factory.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

A well-crafted operational skill: concrete commands throughout, a clearly sequenced workflow with validation and recovery paths, and disciplined externalization of detail to reference files. The residual issues are minor — a few long inline passages that could be tightened or split out, and reliance on a sibling skill's bundle for most reference material.

DimensionReasoningScore

Conciseness

The prose is dense and operational — commands, conditions, and edge cases with essentially no explanation of concepts Claude already knows — but passages like the ~26-line "Let someone else start runs" bullet and invariant 7 on error handling could be tightened, matching 'efficient; minor instances that could be trimmed' rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with sensible placeholders cover every common case: `gh api users/<login> --jq .id`, `tessl schedule pause <loop id>`, `tessl code repo update <owner/repo> --org <org> --review-trigger every-push|open-and-command`, `gh api repos/<owner>/<repo>/branches/<default branch>/protection` — matching the top anchor rather than 'minor gaps'.

5 / 5

Workflow Clarity

A clear three-step sequence (Read the factory → Make the change → Check and publish) with explicit validation checkpoints — `tessl doctor --automations` before push, the cloud check before merge, post-merge Loops verification with a 10-minute timeout recovery path — plus a "What done looks like" checklist; risky writes are gated by ask-before-each-write, so no validation cap applies.

5 / 5

Progressive Disclosure

References are well signaled ("The factory-setup skill's references hold the starters, trigger entries, setup-hook guidance, cloud check, Loops check…") and the 232-line feature catalogue is properly externalized to the bundled references/features.md, but step-2 bullets carry heavy inline detail (notably the access-control bullet) and most referenced material lives in a sibling skill's bundle — good structure with minor organization gaps rather than the ideal split.

4 / 5

Total

18

/

20

Passed

Description

96%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: third-person voice, explicit what-and-when structure, and a comprehensive catalogue of concrete change types phrased as natural user requests. Its only weakness is mild trigger overlap with a sibling factory-setup skill around setup-flavoured requests.

DimensionReasoningScore

Specificity

Enumerates concrete actions across the skill's full scope: "let a teammate start runs, change the model an automation uses, change what an automation does, change how Code Review behaves, stop or remove an automation, update the setup hook, change what the cloud environment can access, add another automation" — comprehensive and concrete with no generic filler, matching the top anchor rather than the 'minor gaps' anchor below it.

5 / 5

Completeness

Explicitly answers both halves: the "what" ("Change or extend a Tessl factory that is already set up on this repository, and suggest what to add next") is followed by an explicit "Use when someone wants to…" clause with concrete trigger scenarios, exactly matching the top anchor.

5 / 5

Trigger Term Quality

The "Use when" clause lists natural phrasings a user would actually say — "stop or remove an automation", "update the setup hook", "let a teammate start runs", "asks what they should add to their factory" — covering synonyms and variations for every entry point, which fits the comprehensive-coverage anchor rather than 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

The scoping phrase "already set up on this repository" clearly separates it from a factory-setup skill, but triggers like "set up Learn from past work" and "add another automation" overlap with a closely related setup skill's territory — mostly distinct with minor overlap risk, not the minimal-conflict top anchor.

4 / 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: 15 suspicious

Warning

Total

15

/

16

Passed

Repository

boranfurkan/discordlancer

Path

.tessl/plugins/tessl/factory-setup/skills/change-factory/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.