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

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 ./internal/assets/skills/rdd-defect-workflow/SKILL.md

The canonical home for this skill is rdd-defect-workflow in Gentleman-Programming/gentle-ai

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.

The body is a lean, well-structured policy workflow with a clear sequence, decision gates, and validation checkpoints, and it appropriately avoids bundle files. Its main weakness is actionability: heavy domain jargon ("CodeGraph-first impact mapping", "source-mutating normalization", "receipt reviews") is never grounded in concrete commands, file locations, or examples, leaving execution details to guesswork.

Suggestions

Ground the jargon in executable specifics: show how to check the RDD kill switch (command or file path), what a receipt review concretely involves, and where "CodeGraph" is invoked.

Add a short example of the Output Contract payload (field names with one-line sample values) so the required deliverable is unambiguous.

Either define domain terms like "receipts/lineage", "correction transaction", and "bounded review defect" inline in a few words, or move their definitions to a small reference file linked from the References section.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence with no filler or explanations of known concepts, but the Decision Gates table ("Forecast exceeds 400 lines | Chain or approved exception before edits") and several other rows largely restate the Hard Rules, so minor trimming is possible — anchor 4 rather than 5.

4 / 5

Actionability

There are concrete anchors ("status:approved", the 400-additions-plus-deletions budget, named output fields like "Return `rdd_mode`, `issue_pr`"), but key execution details are missing: no command or location for checking the "user-owned RDD kill switch", no example of a receipt review, and no output-format example — anchor 3 rather than 2 since Execution Steps and the Output Contract provide more than high-level hints.

3 / 5

Workflow Clarity

Execution Steps gives a clear five-step sequence with checkpoints ("clean current `main` reproduction", "Require independent read-only candidate validation before publication") and a feedback loop ("findings require a new candidate"), so the destructive-operation cap does not apply; minor gaps remain, such as no explicit re-validation loop after test failures — anchor 4.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files (honestly declared: "No supporting files. Current repository policy remains authoritative."), and is organized into clear sections (Activation Contract, Hard Rules, Decision Gates, Execution Steps, Output Contract, References), so the simple-skill exception applies.

5 / 5

Total

16

/

20

Passed

Description

62%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 establishes a clear, bounded niche with an explicit trigger clause and a useful negative boundary, but it is terse and jargon-saturated. It names the domain well without listing multiple concrete actions or natural trigger variations.

Suggestions

List the concrete actions the skill performs during defect fixing (e.g., 'audits PRs for supersession, maps impact, runs bench-journey validation, chains oversized fixes') instead of only enumerating sub-areas.

Add natural trigger phrasing users would actually say, such as 'Use when fixing an RDD bug, repairing a failed delivery gate, or correcting a receipt/lineage defect'.

Include common synonyms like 'bug', 'fix', or 'repair' alongside 'defect' so the trigger matches how users naturally phrase the request.

DimensionReasoningScore

Specificity

"fixing RDD defects" names the domain and one concrete action, but the parenthetical ("review authority, receipts/lineage, correction/recovery, delivery gate") enumerates sub-areas of the domain rather than additional concrete actions, so coverage is not comprehensive as anchor 4 requires.

3 / 5

Completeness

It has an explicit trigger clause ("Trigger: fixing RDD defects") plus a negative boundary ("Not for using or toggling RDD"), giving both what and when; it falls short of anchor 5 because the what and when are near-identical phrasing without concrete trigger variations.

4 / 5

Trigger Term Quality

Terms like "RDD", "receipts/lineage", and "delivery gate" are the natural vocabulary of this niche, but the description is jargon-heavy and misses common variations a user might say ("bug", "fix", "repair", "broken RDD check"), matching anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

The explicit exclusion "Not for using or toggling RDD" clearly separates it from a general RDD-usage skill, but broadly shared terms like "review authority" and "delivery gate" leave minor overlap risk with adjacent repository-workflow skills, matching anchor 4 rather than 5.

4 / 5

Total

14

/

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

internal/assets/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.