CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rdd-defect-workflow

Trigger: fixing RDD defects (review authority, receipts/lineage, correction/recovery, delivery gate). Not for using or toggling RDD.

Quality

65%

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 ./skills/rdd-defect-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 disciplined, well-organized policy skeleton with genuine decision gates, but it operates entirely at the level of named abstractions — CodeGraph mapping, source-mutating normalization, bench journeys — without any concrete commands, examples, or definitions that would let an executor actually run the workflow. The extreme compression that earns top conciseness marks is the same thing that undermines actionability and workflow clarity.

Suggestions

Define or operationalize the domain-specific operations (e.g., what 'source-mutating normalization' and 'CodeGraph-first impact mapping' concretely involve, with a command or worked example), since every step currently rests on undefined proprietary vocabulary.

Expand the Execution Steps with the specific verification actions for each gate (how reproduction is confirmed, how the 400-line budget is measured, what read-only validation runs), turning implicit checkpoints into explicit ones.

Make the error-recovery loop explicit in the numbered steps (e.g., 'if validation finds issues, discard the candidate and return to step 3') rather than leaving it implied in the Hard Rules.

DimensionReasoningScore

Conciseness

The body is exceptionally lean — terse imperative bullets, a compact decision table, and five one-line steps with zero padding or explanation of concepts Claude already knows — matching 'Lean and efficient; every token earns its place'. It is not lower because no section could be cut without losing a rule.

5 / 5

Actionability

Guidance references proprietary operations with no concrete execution detail — 'Use CodeGraph-first impact mapping', 'Run source-mutating normalization before candidate freeze', 'one truthful black-box bench journey' — with no commands, examples, or definitions of how to perform them, matching 'Minimal concrete guidance; high-level hints but missing the specific steps to execute'. It is above anchor 1 because the Hard Rules and Execution Steps do give high-level direction.

2 / 5

Workflow Clarity

A sequence exists (five Execution Steps) with a validation gate ('Freeze, validate read-only') and a Decision Gates table mapping conditions to actions, but the steps are so compressed and jargon-laden that checkpoints and the error-recovery loop ('findings require a new candidate') remain implicit rather than spelled out — matching 'Steps listed but validation gaps'. It is not 4 because a reader cannot concretely follow or verify most steps.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no external references needed; sections are well-organized (Activation Contract, Hard Rules, Decision Gates, Execution Steps, Output Contract) and the References section explicitly declares 'No supporting files', which satisfies the simple-skill exception for a top score.

5 / 5

Total

15

/

20

Passed

Description

48%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 has a well-scoped, distinctive trigger and an explicit boundary, but it never states what the skill does, and its vocabulary leans on internal RDD jargon rather than natural user phrases. It functions as a trigger filter more than a capability description.

Suggestions

Add a 'what' clause stating the skill's concrete capability (e.g., what it does during defect fixing: enforcing gates, validating candidates, structuring evidence), since 'only when without what' caps completeness low.

Include natural trigger synonyms users might say, such as 'bug', 'issue', 'regression', or 'review failure', instead of relying solely on internal RDD terminology like 'receipts/lineage' and 'delivery gate'.

DimensionReasoningScore

Specificity

The description names the domain ("fixing RDD defects") with sub-areas ("review authority, receipts/lineage, correction/recovery, delivery gate"), but the only action stated is 'fixing' — comparable to 'Names domain and 1-2 concrete actions'. It does not list several distinct actions, so it falls short of anchor 4.

3 / 5

Completeness

Only the 'when' is present ('Trigger: fixing RDD defects') with an explicit exclusion ('Not for using or toggling RDD'), but there is no statement of what the skill actually does — matching anchor 2, 'only when is present without what'. It is not a 3 because no capability description exists, even a weak one.

2 / 5

Trigger Term Quality

"Trigger: fixing RDD defects" includes the natural phrase 'fixing defects', but the parenthetical terms ('review authority', 'receipts/lineage', 'delivery gate') are internal jargon rather than phrases a user would naturally say, and common synonyms (bug, issue, regression) are missing — matching 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (fixing RDD defects) and explicitly disambiguates the adjacent case ('Not for using or toggling RDD'), giving minimal conflict risk with other skills — matching anchor 5's 'Clear niche with distinct triggers'.

5 / 5

Total

13

/

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

Gentleman-Programming/gentle-ai

Path

skills/rdd-defect-workflow/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.