CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hsb-flash

Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must never be mixed.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/hsb-flash/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong operational skill body: the workflow is clearly sequenced with gates, destructive-operation safety checks, and error-recovery loops, and detail is properly split into real one-level-deep reference files. Its main weakness is redundancy — the phase plan, environment variables, and two-step rules are each stated multiple times, inflating token cost without adding information.

Suggestions

Remove the duplicated phase plan: keep it in one place (either the Gate 2 block or the 'Mandatory interaction pattern' section) and delete the other, along with the second env-var listing in 'Linux/Windows-friendly wrapper variables'.

Consolidate the repeated two-step upgrade/downgrade rules and the 'never mix board-type commands' warning into a single authoritative section, cross-referencing it elsewhere.

State the concrete flash command template (e.g. `program_lattice_cpnx100 --force ... --accept-eula` invocation form) in the body or reference instead of delegating to 'read the user guide of the HSB repo and extract the flash command'.

DimensionReasoningScore

Conciseness

The domain-specific procedure content mostly earns its tokens (no explanations of concepts Claude already knows), but the phase plan is duplicated in the Gate 2 block and the 'Mandatory interaction pattern' section, environment variables are listed twice, the two-step and never-mix rules are restated 3-4 times, and references/help-text.md is pointed to three times. The redundancy is more than minor trimming but is duplication rather than padded explanation, placing it between anchors 2 and 3.

3 / 5

Actionability

Concrete executable guidance throughout — `hololink enumerate` with `hololink --force fpga_version` fallback, exact `--force --accept-eula` flags with v2.0.0 flag placement, VERSION-file reads, session-state variables, and repo checkout logic. Not fully copy-paste ready because the core flash command itself is delegated ('Read the user guide of the HSB repo being used for flashing and extract the flash command') rather than stated.

4 / 5

Workflow Clarity

Phases 0-6 are clearly sequenced with required gates before any action, explicit validation checkpoints (board-type confirmation, post-flash FPGA version verification, power-cycle verification), a defined error-summary pattern (failed command / root cause / safe recommendation / blocking), and a cleanup phase — full feedback loops for a destructive operation.

5 / 5

Progressive Disclosure

Three well-signaled, one-level-deep reference files (phase-details.md, flashing-infrastructure.md, help-text.md — all verified present, no nested references) appropriately split detail from the overview. Not a 5 because the body still inlines a fully duplicated phase plan and repeats env-var and two-step detail that belongs in the references, and the help-text pointer is repeated three times.

4 / 5

Total

16

/

20

Passed

Description

70%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 specific, distinctive description that names concrete capabilities and precisely enumerates supported hardware and FPGA versions. Its one structural weakness is the missing 'Use when...' trigger clause, which caps completeness and leaves natural invocation phrasing (e.g. 'flash/upgrade the FPGA firmware') only partially covered.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to flash, upgrade, or downgrade FPGA firmware on an HSB Lattice board or VB1940 camera.'

Include natural synonyms such as 'firmware', 'upgrade', and 'downgrade' so users phrasing the request those ways still match the description.

DimensionReasoningScore

Specificity

Concrete actions are named ('Flash the FPGA', 'Uses release-specific YAML manifests and board-type-specific program commands') with exact hardware and FPGA-version enumeration — several specific actions with minor gaps (upgrade/downgrade and version verification are not mentioned as actions). Not a 5 because action coverage is narrower than the comprehensive multi-action top anchor.

4 / 5

Completeness

The 'what' is clear (flash the FPGA on an HSB board with manifest-driven, board-specific commands), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. Not a 2 because the 'what' is explicit rather than vague; not a 4 because 'when' is entirely absent, not merely implicit.

3 / 5

Trigger Term Quality

Natural user phrasing is well covered: 'Flash the FPGA', 'HSB board', 'NVIDIA devkit', 'Lattice', 'VB1940' are terms a user with this hardware would actually say. Not a 5 because common synonyms like 'firmware', 'upgrade', and 'downgrade' are absent from the description even though the body supports them.

4 / 5

Distinctiveness Conflict Risk

A clear niche with distinct triggers — HSB boards, Leopard Imaging VB1940 cameras, and specific FPGA version numbers are unlikely to match any other skill's invocation context, giving minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

68%

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

Validation — 11 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

11

/

16

Passed

Repository

NVIDIA/skills

Path

skills/hsb-flash/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.