CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

devloop

Goal-driven development loop — define objective, write rules with key-results, verify visually, sync to issue tracker.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./mod/skill0/lib/skill0/core/devloop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is an exemplary lean, command-first skill: a concrete rule.yml example, executable verification commands with cost/time hints, and an explicit visual-verification feedback loop. Remaining gaps are minor — a duplicated command summary, placeholder arguments, and no explicit build/gate step backing the 'Build passes' key-result.

DimensionReasoningScore

Conciseness

The body is lean and command-driven with no concept explanations, but the 'Agent tools' section repeats the x rule scan/check/audit commands already shown in step 3 — a small redundancy that could be trimmed.

4 / 5

Actionability

Commands are copy-paste ready (x rule init, agent-browser screenshot invocations, a complete rule.yml example with all field semantics), but agent-browser lines use <url>/<proj> placeholders and issue posting is deferred entirely to another skill — minor gaps.

4 / 5

Workflow Clarity

The goal → rule.yml → code → verify → issue sequence is explicit with an iteration feedback loop ('If mismatch → iterate and re-screenshot') and MUST gates for before/after screenshots; however kr-3 ('Build passes') has no corresponding build command and no gate before posting to the issue tracker.

4 / 5

Progressive Disclosure

The ~80-line body is well organized into setup/workflow/related sections with nothing that belongs in a separate file; all cross-skill references (../rule/SKILL.md, ../issue/SKILL.md, etc.) are one level deep and clearly labeled with what each provides.

5 / 5

Total

17

/

20

Passed

Description

58%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 communicates a coherent four-step capability but reads as a tagline rather than a trigger: it answers 'what' clearly yet omits any 'when to use' guidance. Adding concrete artifacts (rule.yml, before/after screenshots) and natural trigger phrases would lift most dimensions.

Suggestions

Append an explicit trigger clause, e.g., 'Use when starting a dev task that needs defined goals, verifiable key-results, and visual before/after proof before syncing to an issue tracker.'

Ground the actions in concrete artifacts users would recognize — 'write a rule.yml with key-results', 'capture before/after screenshots with agent-browser' — instead of generic verbs like 'define objective' and 'verify visually'.

Include natural user phrasings/synonyms such as 'development loop', 'dev workflow', 'goal and key-results', and 'issue tracker sync' so the skill triggers on real requests.

DimensionReasoningScore

Specificity

Lists four named actions ('define objective, write rules with key-results, verify visually, sync to issue tracker') covering the loop, but phrasing stays generic — no concrete artifacts like rule.yml or before/after screenshots that would make it comprehensive.

4 / 5

Completeness

The 'what' is clear, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Contains relevant keywords ('goal', 'rules', 'key-results', 'verify', 'issue tracker') but misses the natural phrases and synonyms a user would say when needing this skill (e.g., 'dev loop', 'define requirements', 'verify changes visually').

3 / 5

Distinctiveness Conflict Risk

The niche (rules with key-results, visual verification, issue sync) is mostly distinct with only minor overlap risk against closely related dev-workflow skills; the lack of trigger guidance keeps it below a 5.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 8 suspicious

Warning

Total

14

/

16

Passed

Repository

x-cmd/x-cmd

Path

mod/skill0/lib/skill0/core/devloop/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.