CtrlK
BlogDocsLog inGet started
Tessl Logo

rdd-advisory-transport

Trigger: reviewer transport, advisory transport, review adapter, lens prompt/schema, OpenCode reviewer plugin, Codex reviewer, ReviewProviderContract. Enforce the shared Go advisory reviewer transport contract.

69

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 concise, well-structured governance overview that assumes domain competence and splits detail into clearly signaled one-level-deep references. It could improve actionability and workflow feedback loops with more concrete commands and explicit fix-and-retry cycles.

DimensionReasoningScore

Conciseness

Lean and dense throughout, assuming Claude's competence by referencing native sources (reviewLensContextBlock, ReviewerResultSchema) without explaining basics; every token earns its place.

5 / 5

Actionability

Concrete instruction-only guidance naming specific artifacts and guards (adapter-minimality static guards, differential-test against current admission), but it offers process direction rather than copy-paste executable commands, leaving minor gaps.

4 / 5

Workflow Clarity

A clear 6-step sequence with explicit validation gates (corpus-diff gate in step 6, regression-baseline STOP in Decision Gates), but the checkpoints are gates rather than explicit fix-and-retry feedback loops.

4 / 5

Progressive Disclosure

A well-sectioned overview pointing to two real, one-level-deep reference files (shared-advisory-transport-proposal.md, issue-impact-matrix.md) with clear descriptive labels, giving easy navigation.

5 / 5

Total

18

/

20

Passed

Description

82%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 clearly and explicitly covers both what the skill does and when to use it, with a strong, distinctive trigger-term list for a niche governance domain. Its only weakness is that the 'what' rests on a single action verb rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("Enforce the shared Go advisory reviewer transport contract") but the remainder is a list of trigger nouns rather than several distinct actions, matching the 1-2 concrete actions anchor.

3 / 5

Completeness

Explicit "Trigger:" label provides concrete when-guidance and "Enforce...contract" gives a clear what, so both are explicitly answered with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage with synonyms (reviewer transport, advisory transport, review adapter) and specific tool names (OpenCode, Codex), though the terms are domain jargon rather than broadly natural user phrasing.

4 / 5

Distinctiveness Conflict Risk

A highly niche domain (Go advisory reviewer transport contract, OpenCode/Codex reviewers) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

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