CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-attributes-metadata

Add function/parameter attributes and IR metadata to LLVM 22 IR to unlock optimizer opportunities. Covers NoUnwind, ReadNone, NoCapture, Noundef, loop vectorization hints, branch weights, TBAA, !range, and !nonnull.

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.

A lean, highly actionable reference with executable LLVM 22 C++ patterns and clear guardrails; the main gap is the absence of explicit verification checkpoints and any external reference files.

Suggestions

Add a short verification step per annotation task (e.g. run `opt -passes=verify` or check `llvm-dis` output) so each step has a feedback checkpoint.

Consider moving the full TBAA and loop-metadata worked examples into a references file and keeping SKILL.md as an overview, to improve progressive disclosure for this ~230-line skill.

DimensionReasoningScore

Conciseness

Efficient use of tight code blocks and tables that assumes Claude's domain competence, with only minor instances that could be trimmed (e.g. the 'Why this matters' framing and a few restating inline comments).

4 / 5

Actionability

Fully executable, copy-paste-ready C++ throughout (addFnAttr, AttrBuilder, MDBuilder, the self-referential loop MDNode pattern) with key/value/effect tables covering the common annotation cases.

5 / 5

Workflow Clarity

A clear Step 0–6 sequence for per-function annotation with a 'Common mistakes' guardrail section, but no explicit validate-then-retry checkpoint; acceptable for this single-purpose, non-destructive task.

4 / 5

Progressive Disclosure

Well-organized into clear sections with tables and code and no nested references, though all content is inline in SKILL.md with no bundle files; the longer worked examples (TBAA, loop metadata) could optionally be split out.

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.

A specific, well-scoped description with concrete attribute/metadata coverage, but it lacks an explicit 'when to use' trigger clause, which caps its completeness.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when emitting or refining LLVM IR for a frontend, optimizing alias analysis/vectorization, or when the user mentions IR attributes or metadata.'

Broaden trigger terms with synonyms a user might say (e.g. 'function attributes', 'IR annotations', 'optimizer hints', 'alias analysis metadata') alongside the precise attribute names.

DimensionReasoningScore

Specificity

Names the domain ('Add function/parameter attributes and IR metadata to LLVM 22 IR') and lists multiple concrete actions ('NoUnwind, ReadNone, NoCapture, Noundef, loop vectorization hints, branch weights, TBAA, !range, and !nonnull'), giving comprehensive coverage.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when...' clause; the only trigger guidance is weakly implied by 'to unlock optimizer opportunities', capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Good keyword coverage of domain-natural terms an LLVM frontend author would say, but it relies on narrow jargon with no synonyms, file extensions, or common phrasings users might also voice.

4 / 5

Distinctiveness Conflict Risk

The 'LLVM 22 IR' attribute/metadata annotation niche is sharply scoped with distinct triggers and minimal risk of firing for an unrelated skill.

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-attributes-metadata/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.