CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dev

Load when implementing an issue or applying review fixes as a dev agent.

Quality

67%

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 ./.agents/skills/dev/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a dense, information-rich contract layer: it assumes full competence, carries no padding, and wraps its multi-step workflows in an unusually thorough validation and recovery regime with concrete commands and config keys throughout. Its one structural weakness is that the workflow files it defers to for step-level detail are absent from the bundle, leaving the navigation hub pointing at files a reader cannot open.

Suggestions

Ship the referenced workflow files (workflows/dev-implement.md, workflows/dev-fix.md, workflows/long-running-validation.md) in the skill bundle, or inline the essential step sequences for each workflow so the SKILL.md is self-sufficient.

If the workflow files cannot be bundled, add a one-line inline summary of each workflow's key steps (as is done for the completion tail) so the arrow-notation sequences are actionable without the external files.

Trim the passages that restate rules owned by referenced files (round mechanics, DEV_VALIDATE_* semantics duplicated from dev-implement.md § 5) to resolve the twin-rule violation the skill itself defines.

DimensionReasoningScore

Conciseness

The body is highly compressed project-specific contract with no explanations of concepts Claude already knows and no padding — every rule is non-derivable — but a few passages restate constraints owned by referenced files (e.g. round mechanics orch's skill-rules.md owns, and the Configuration section repeats what dev-implement.md § 5 and dev-return-write --help state), keeping it below the every-token-earns-its-place level 5.

4 / 5

Actionability

Concrete anchors abound: the literal command "git diff --no-renames --name-only [PREVIOUS_ROUND_COMMIT] HEAD -- <paths>", named tools (dev-return-write, dev-validate-run, workflow-state new-local-key), the run-notes file path pattern, and the implementer-selection table. It falls short of fully-executable level 5 because many actions resolve only through files outside the body (dev-return.md schema, dev-implement.md § 5, dev-return-write --help), and several rules are policy prose rather than runnable steps.

4 / 5

Workflow Clarity

Both workflows are sequenced with numbered section anchors ("activate → plan → implement → validate → commit → QA labels → summary → artifact → return (§ 1-11)") and validation is exceptionally covered — the validation gate, investigation-run question/answer protocol with a two-inconclusive back-off rule, and interrupted-run recovery all act as explicit checkpoints. It is not level 5 because the full step detail is deferred to workflow files rather than presented with inline feedback loops.

4 / 5

Progressive Disclosure

Section organization is good and references are one level deep with precise section anchors, but the primary workflow detail is delegated to bundle files — workflows/dev-implement.md, workflows/dev-fix.md, workflows/long-running-validation.md — that are not present in the bundle (no workflows/, references/, scripts/, or assets/ directories exist), so the disclosure structure cannot be followed as shipped. That broken deferral is more than a minor organization gap, placing it below level 4.

3 / 5

Total

15

/

20

Passed

Description

50%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 is a clean third-person load trigger that says precisely when to activate the skill, but it only answers "when" — it gives no statement of what the skill provides, its two actions are generic, and its trigger vocabulary has no synonyms or variations. All four dimensions land at the midpoint, and the "applying review fixes" wording creates overlap risk with the sibling reviewer skill.

Suggestions

Add a "what" clause stating what the skill provides, e.g. "Selects the implementer agent by domain, applies engineering and test rules, runs the validation gate, and writes the round return artifact."

Broaden trigger coverage with natural variations users would say: "fix review findings", "address review comments", "dev round", "implementation delegation".

Sharpen the boundary with the reviewer skill, e.g. "applies fixes only; performing reviews and QA-reviews belongs to the reviewer skill."

DimensionReasoningScore

Specificity

"implementing an issue or applying review fixes" names the domain and exactly two actions, matching the 1-2-concrete-actions anchor; it never says what implementation entails (code, tests, commits, artifact), so it is not the several-specific-actions level 4.

3 / 5

Completeness

The "when" is explicit ("Load when implementing an issue or applying review fixes"), but the "what" is only implied by the trigger — the skill's actual content (implementer selection, engineering rules, validation gate, round artifact) is entirely unstated. That mirrors the level-3 anchor of one dimension clear and the other weak, not level 4 where both are present.

3 / 5

Trigger Term Quality

"implementing an issue", "review fixes", and "dev agent" are natural phrases within this orchestration ecosystem, but no synonyms or variations are offered (e.g. "fix findings", "address review comments", "dev round"), fitting the missing-common-variations anchor rather than the good-coverage level 4.

3 / 5

Distinctiveness Conflict Risk

"applying review fixes as a dev agent" is somewhat specific but overlaps with the reviewer skill's review/QA-review territory (the body itself has to clarify that boundary), fitting the could-still-overlap-with-similar-skills anchor rather than the mostly-distinct level 4.

3 / 5

Total

12

/

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: 6 missing, 14 suspicious

Warning

Total

14

/

16

Passed

Repository

vanillagreencom/kendex

Path

.agents/skills/dev/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.