CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hsb-ip-create-top

Create or explain fixed-format HSB FPGA_top.sv wrappers from validated HOLOLINK_def.svh files. Do not use for def generation or validation.

Quality

72%

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/hsb-ip-create-top/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, actionable, and uses progressive disclosure effectively with a clear reference-loading table and verified one-level-deep references. Main improvements are removing the repeated generic note and the source-policy duplication, and adding an output-validation feedback loop.

Suggestions

State the generic reference/template note once (e.g. in Instructions) and reference it from the workflow steps instead of repeating it three times.

Trim the duplicated source-root/revision detail in 'Live HSB IP Source Policy' by deferring to references/source-policy.md, keeping only the decision rule inline.

Add an explicit output-validation step (e.g. re-check emitted signal groups against the active defs macros and live HOLOLINK_top port map) with a fix-and-retry loop after scaffold generation.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes Claude's competence (no basic SystemVerilog concept padding), but the generic reference/template note is restated three times and the source-policy detail duplicates content in references/source-policy.md, which are minor instances that could be trimmed.

4 / 5

Actionability

Concrete decision tree (Workflow Decision), per-workflow numbered steps, a Reference Loading table, and three fully-walked examples give mostly executable guidance; the executable signal-shape code is appropriately delegated to references/fixed-format.md rather than inlined.

4 / 5

Workflow Clarity

Standalone, Handoff, and Explain workflows are clearly sequenced with input-validation checkpoints ('stop before generation', 'do not proceed from an unvalidated defs file') and a Troubleshooting section, but there is no explicit output validation or fix-and-retry feedback loop after scaffold generation.

4 / 5

Progressive Disclosure

The body is a clear overview with a Reference Loading table that signals each one-level-deep reference (fixed-format.md, source-policy.md, handoff-contract.md) and its trigger; all referenced files exist and content is appropriately split out.

5 / 5

Total

17

/

20

Passed

Description

57%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 specific and well-bounded with a strong anti-conflict disclaimer, but it lacks a positive 'Use when...' trigger clause and relies on technical terms rather than natural user phrasing. Adding an explicit trigger clause with synonyms would raise completeness and trigger-term quality.

Suggestions

Add an explicit positive trigger clause, e.g. 'Use when creating or explaining an HSB FPGA_top.sv top-level wrapper from a validated HOLOLINK_def.svh.'

Include natural-language synonyms users might say (e.g. 'HSB top-level', 'FPGA top wrapper', 'HOLOLINK top instantiation') alongside the technical file names.

Keep the negative boundary but pair it with the positive trigger so the 'when' is stated explicitly rather than only implied.

DimensionReasoningScore

Specificity

Names the domain ('fixed-format HSB FPGA_top.sv wrappers from validated HOLOLINK_def.svh files') and two concrete actions ('Create or explain'), which matches the anchor for 1-2 concrete actions without being comprehensive.

3 / 5

Completeness

There is a clear 'what' but no positive 'Use when...' trigger clause; only a negative boundary ('Do not use for def generation or validation') weakly implies the when, so completeness is capped at 3 per the missing-trigger-clause guideline.

3 / 5

Trigger Term Quality

Relevant keywords exist (HSB, FPGA_top.sv, HOLOLINK_def.svh, wrappers) but they are technical jargon with no natural-user synonyms or variations, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche (HSB FPGA_top.sv wrappers from validated defs) and explicitly disclaims the adjacent def skill ('Do not use for def generation or validation'), giving minimal conflict risk.

5 / 5

Total

14

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NVIDIA/skills

Path

skills/hsb-ip-create-top/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.