CtrlK
BlogDocsLog inGet started
Tessl Logo

analyze-and-convert

Analyze a HuggingFace model and attempt OpenVINO conversion — probe properties, run strategy matrix, classify failures, and produce a structured routing report.

51

Quality

56%

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 ./.github/agents-prototype/skills/analyze-and-convert/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

55%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 content is exceptionally concise and cleanly sequenced, but it provides almost no executable detail and references four bundle files that are absent, so the progressive-disclosure structure is unfulfilled and guidance stays at a high level.

Suggestions

Add concrete, copy-paste-ready commands for each step (e.g. the optimum-cli / ovc / convert_model invocations) so the table is actionable rather than descriptive.

Provide the referenced bundle files (probe-model.md, try-conversion.md, classify-failure.md, build-report.md) or inline the key instructions so the references are real.

Insert an explicit validation checkpoint after the conversion step (e.g. 'If conversion succeeds, skip classify-failure; otherwise capture stderr and proceed') to add a feedback loop for the batch operation.

DimensionReasoningScore

Conciseness

The body is extremely lean — a short 'When to use' clause and a four-row step table — with zero padding and no explanation of concepts Claude already knows, so every token earns its place.

5 / 5

Actionability

It gives high-level purpose per step ('Gather model profile', 'Run conversion strategy matrix') but no concrete commands, code, or exact steps to execute each step, so it lands at 'minimal concrete guidance; high-level hints but missing the specific steps.'

2 / 5

Workflow Clarity

Steps are clearly numbered and sequenced in a table with files and purpose, but the batch conversion process lacks explicit validation checkpoints and feedback loops despite classifying failures, which caps clarity at 3.

3 / 5

Progressive Disclosure

The body references four .md files (probe-model.md, try-conversion.md, classify-failure.md, build-report.md) that do not exist in the bundle, so the disclosed structure is not actually present; this is buried/missing references rather than a real one-level-deep split.

2 / 5

Total

12

/

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 states concrete capabilities clearly in third person but omits any 'Use when...' trigger guidance, which caps its completeness and limits natural trigger-term coverage. It is distinctive within a narrow OpenVINO-conversion niche.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when converting a HuggingFace model to OpenVINO IR, diagnosing why a model fails to convert, or routing conversion failures.'

Add natural user-facing trigger terms and synonyms — 'convert to OpenVINO', 'OpenVINO IR', 'conversion error', 'model fails to convert' — beyond the technical phrasing.

Include the .xml/.onnx artifact phrasing or model-id reference to round out keyword coverage toward a 5.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'probe properties, run strategy matrix, classify failures, and produce a structured routing report' — giving clear, specific coverage, though it stops just short of the comprehensive multi-action list of a 5.

4 / 5

Completeness

The 'what' is clearly stated but there is no 'Use when...' clause or explicit trigger guidance; per the rubric a missing explicit-when clause caps completeness at 3.

3 / 5

Trigger Term Quality

It names the relevant domain (HuggingFace model, OpenVINO conversion) but lacks the natural user-facing phrases and synonyms (e.g. 'convert', 'IR', 'model ID', 'failures') a user would actually say, so it sits at 'some relevant keywords but missing common variations.'

3 / 5

Distinctiveness Conflict Risk

The OpenVINO/HuggingFace conversion niche is specific and distinct from generic skills, with only minor overlap risk against other model-tooling skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing

Warning

Total

15

/

16

Passed

Repository
openvinotoolkit/openvino
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.