CtrlK
BlogDocsLog inGet started
Tessl Logo

autonomous-coding-workflow

Governs safe, incremental, repository-wide development workflow with continuous validation gates

53

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/autonomous-coding-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

The body is a well-structured, actionable instruction skill with strong validation gates, feedback loops, and a completion checklist. Its main weaknesses are minor command repetition across sections and the absence of any progressive file split despite a >50-line length.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanation of PHPUnit, Pint, or Traits), but validation commands and steps recur across sections 4, 5, and 6, giving minor instances of repetition that could be tightened — matching 'Efficient; minor instances of over-explanation that could be trimmed'.

4 / 5

Actionability

It provides concrete copy-paste-ready commands (`php -l`, `vendor/bin/pint --dirty --format agent`, `migrate:fresh --seed`) and specific sequencing, but references PHPUnit and static analysis by name without exact invocations — 'Mostly executable guidance; concrete code or commands with minor gaps'.

4 / 5

Workflow Clarity

The workflow is explicitly sequenced with validation checkpoints ('Never proceed if any of the following fail'), feedback loops ('Fix failures immediately', 'Continue only if repository is clean'), and a final success-criteria checklist — matching 'Clear sequence with explicit validation steps; feedback loops for error recovery; checklists'.

5 / 5

Progressive Disclosure

Content is well-organized into numbered sections with no nested references and easy navigation, but it exceeds 50 lines as a single self-contained file with no one-level-deep references, so it sits at 'Good structure; most content is appropriately placed' rather than the reference-split level 5.

4 / 5

Total

17

/

20

Passed

Description

37%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.

The description states a clear purpose but is light on concrete actions and lacks any explicit 'Use when...' trigger guidance, which caps its completeness. It is distinguishable enough from unrelated skills but overlaps with general coding-workflow skills.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g. 'Use when making repository-wide code changes, refactoring across modules, or running long autonomous coding tasks').

Replace the generic verb 'Governs' with 2-3 concrete actions the skill performs (e.g. 'Modifies, refactors, and validates code repository-wide in incremental steps').

Include more natural synonyms users would say ('repo-wide changes', 'safe refactoring') alongside the current technical terms.

DimensionReasoningScore

Specificity

The description names the domain ('repository-wide development workflow') but the only verb is the generic 'Governs', with characteristics ('safe, incremental, validation gates') rather than concrete actions — matching the anchor 'Names the domain but actions are minimal or generic'.

2 / 5

Completeness

It gives a clear 'what' but there is no 'Use when...' or equivalent explicit 'when' trigger guidance, which per the judging guidelines caps completeness at 3 — the 'when' is entirely missing rather than weakly implied.

3 / 5

Trigger Term Quality

Terms like 'development workflow' and 'continuous validation gates' are moderately relevant but lean technical/jargon-y and omit the natural phrases a user would say (e.g. 'make repo-wide changes', 'refactor safely'); closer to 'one or two generic keywords; missing the natural phrases users say' than level 3.

2 / 5

Distinctiveness Conflict Risk

'Repository-wide ... development workflow with continuous validation gates' is somewhat specific but still overlaps with general coding/refactor and other workflow skills, matching 'Somewhat specific but could still overlap with similar skills'.

3 / 5

Total

10

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Bottelet/DaybydayCRM
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.