CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rtl-specification-consistency-checker

Check behavioral consistency between high-level hardware specifications and RTL implementations. Use when asked to check RTL consistency, verify RTL against spec, check hardware specification compliance, validate RTL implementation, find spec violations in RTL, check behavioral consistency, or when working with hardware designs that need verification against protocol specifications, timing requirements, or functional specifications in Verilog, VHDL, or SystemVerilog.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/rtl-specification-consistency-checker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 skill presents a clear, well-sequenced consistency-checking workflow with genuinely useful report templates and pattern examples. Its main weaknesses are token inefficiency from re-teaching HDL fundamentals and generic tips, and duplication between the body's pattern sections and the provided reference files.

Suggestions

Remove the duplicated "Common Verification Patterns" and "HDL-Specific Considerations" sections from the body, keeping one short representative example inline and pointing to references/hdl_patterns.md and references/common_violations.md for the rest — this would improve both conciseness and progressive disclosure.

Cut the HDL-basic checklists (blocking vs non-blocking, sensitivity lists, latch inference) and the generic Tips section; Claude already knows these, and the reference file already covers the patterns.

Add an explicit validation checkpoint in the workflow (e.g., re-verify the signal mapping for each requirement before classifying it, and re-examine counterexamples before marking a requirement violated) with a worked trace example for the timing-check step.

DimensionReasoningScore

Conciseness

The body is mostly efficient structured guidance, but it includes unnecessary explanation of concepts Claude already knows: the HDL-Specific Considerations section lists HDL basics ("Blocking vs non-blocking assignments", "Sensitivity list completeness", "Signal vs variable usage", "Latch inference"), and the Tips section offers generic advice ("Check edge cases", "Document assumptions") Claude would apply anyway. This fits anchor 3 (mostly efficient, some unnecessary explanation that could be tightened) rather than 2, since the material is organized and task-relevant rather than padded prose.

3 / 5

Actionability

Concrete, usable artifacts dominate: a violation report template with a filled example trace table, an executive summary format, per-requirement report structure, and spec-pattern-to-RTL-check examples with Verilog/VHDL snippets. It falls short of anchor 5 because several verification steps remain hints rather than procedures (e.g., "Trace signal propagation through the pipeline", "Count register stages") with no worked example.

4 / 5

Workflow Clarity

The 7-step process (parse inputs, extract requirements, map to RTL, check consistency, classify, document violations, generate report) is clearly numbered and sequenced, with the classification taxonomy and per-requirement documentation checklist acting as implicit checkpoints. It does not reach anchor 5 because there are no explicit validation or feedback-loop steps (e.g., re-checking a mapping before classifying), though the read-only analysis nature of the task limits the risk.

4 / 5

Progressive Disclosure

The two references (references/hdl_patterns.md, references/common_violations.md) are real, clearly signaled, and one level deep, but the body inlines roughly 130 lines of "Common Verification Patterns" and "HDL-Specific Considerations" content that duplicates material already provided in those reference files (e.g., the state machine pattern appears both in the body and in hdl_patterns.md). This matches anchor 3 (content that should be separate is inline) rather than 4, where placement would be consistently appropriate.

3 / 5

Total

14

/

20

Passed

Description

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

A strong description with an explicit what/when structure and comprehensive, natural trigger coverage including all three major HDL languages. Its main weakness is modest capability specificity — it states one umbrella action rather than the skill's distinct extraction, mapping, and classification capabilities — and minor trigger overlap with general RTL verification skills.

Suggestions

Enumerate the skill's core actions in the opening sentence (e.g., "Extract behavioral requirements from specifications, map them to RTL logic, and classify each as satisfied, violated, underspecified, or uncheckable") to lift specificity.

Narrow the broad trigger "validate RTL implementation" to the consistency-checking context (e.g., "validate RTL implementation against a written spec") to reduce overlap with general RTL review/lint skills.

DimensionReasoningScore

Specificity

"Check behavioral consistency between high-level hardware specifications and RTL implementations" names the domain and one concrete action, but the description does not enumerate the fuller capability set the skill actually performs (extract requirements, map to RTL, classify as satisfied/violated/underspecified/uncheckable). It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than 4, since the remaining sentences are trigger phrases rather than distinct actions.

3 / 5

Completeness

It explicitly answers both questions: the what ("Check behavioral consistency between high-level hardware specifications and RTL implementations") and the when ("Use when asked to check RTL consistency... or when working with hardware designs that need verification against protocol specifications, timing requirements, or functional specifications"). Concrete trigger phrases accompany the when-clause, matching anchor 5 exactly; not 4 because the when-clause is already fully explicit and specific.

5 / 5

Trigger Term Quality

The trigger list covers many natural user phrasings and their synonyms ("check RTL consistency", "verify RTL against spec", "check hardware specification compliance", "validate RTL implementation", "find spec violations in RTL", "check behavioral consistency") plus the domain's equivalent of file extensions ("Verilog, VHDL, or SystemVerilog"). This is comprehensive natural-term coverage matching anchor 5; it is above anchor 4 because no common variation is obviously missing.

5 / 5

Distinctiveness Conflict Risk

The hardware-spec-vs-RTL niche is clear and most triggers are domain-qualified, but phrases like "validate RTL implementation" could reasonably fire for broader RTL review, lint, or simulation skills. This is minor overlap risk with closely related skills (anchor 4) rather than minimal conflict risk (anchor 5).

4 / 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

ArabelaTso/Skills-4-SE

Path

skills/rtl-specification-consistency-checker/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.