CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-vectorization-hint

Guide LLVM 22's auto-vectorizer and SLP vectorizer from a frontend. Covers loop vectorization metadata, interleaving, loop distribution, marking parallel accesses, controlling SLP, and how to check whether vectorization happened.

Quality

83%

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

82%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 highly actionable with real, executable LLVM C++ and a clear step sequence including a verification step. It is slightly held back by light conceptual padding in Step 0 and an implicit rather than explicit error-recovery loop.

Suggestions

Make the verification loop explicit in Step 7: when a 'missed' remark appears, list which hint/structure to check and re-run, mirroring a validate→fix→retry cycle.

Trim Step 0's conceptual explanation of what vectorizers do, or move it to a reference file, since Claude already understands loop vs SLP vectorization.

DimensionReasoningScore

Conciseness

Largely lean and code-driven, but Step 0's conceptual table of what each vectorizer does and several restating inline comments are minor over-explanation Claude largely already knows, keeping it just below a 5.

4 / 5

Actionability

Provides fully executable, copy-paste-ready LLVM IRBuilder C++ for every step plus runnable `opt` commands with pass-remarks, covering the common cases comprehensively.

5 / 5

Workflow Clarity

Steps 0–7 are clearly sequenced and Step 7 supplies a verification checkpoint via pass-remarks, but the error-recovery loop (what to fix when a 'missed' remark appears) is implicit rather than an explicit validate→fix→retry cycle.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references, but everything is inlined in one ~230-line file; the metadata reference table and 'Common mistakes' are reasonable inline yet are minor candidates for a separate reference file.

4 / 5

Total

17

/

20

Passed

Description

75%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, third-person, and occupies a well-defined niche, but it omits an explicit 'Use when...' trigger clause, which caps completeness. Adding a concrete trigger sentence would raise the score.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when generating LLVM IR for array/vector operations or counted loops that should vectorize to SIMD.'

Add natural synonyms users might say — 'SIMD', 'vectorize', 'vectorization hints' — alongside the engine-internal terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'loop vectorization metadata, interleaving, loop distribution, marking parallel accesses, controlling SLP, and how to check whether vectorization happened' — giving comprehensive coverage rather than the minor gaps of a 4.

5 / 5

Completeness

Has a clear 'what' ('Guide LLVM 22's auto-vectorizer and SLP vectorizer from a frontend') but no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Good on-point domain keywords ('auto-vectorizer', 'SLP vectorizer', 'loop vectorization', 'interleaving', 'parallel accesses'), but missing natural synonyms a user might say such as 'SIMD', 'vectorize', or 'hints'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche — emitting LLVM vectorization metadata from a compiler frontend — 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

hbarve1/tessl-llvm

Path

tiles/tessl-llvm/skills/add-vectorization-hint/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.