CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-alias-analysis

Use and extend alias analysis in LLVM 22. Covers querying AAResults from a function pass, using IR-level hints (noalias, TBAA) as the preferred approach, writing a custom AA analysis with the New Pass Manager, and common ModRef patterns.

Quality

85%

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

90%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 lean, actionable, and well-structured with executable code and a strong up-front decision table. The main gap is the absence of explicit validation checkpoints, though they are not strictly required for this non-destructive reference skill.

Suggestions

Add a short validation step for the custom AA pass (e.g., 'verify with -aa-eval / opt -passes=aa-eval to confirm NoAlias results match expectations') to strengthen workflow clarity.

Consider splitting the lengthy custom-AA example (Part 4) into a referenced file once a bundle is introduced, to improve progressive disclosure.

Verify the two 'See also' doc links resolve to real files, since they point outside the skill bundle to ../../docs/.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no basic-concept padding, brief justifications only where non-obvious (e.g., caching TBAA root nodes), and every section earns its tokens.

5 / 5

Actionability

Provides copy-paste-ready C++ for each part (noalias/nocapture attrs, TBAA metadata, AAResults queries, ModRef, custom AA + registration); the only stubbed helpers are explicitly justified as language-specific logic.

5 / 5

Workflow Clarity

A Step 0 decision table clearly sequences approach selection and a Common mistakes section acts as a checklist, but there are no explicit validation/feedback loops — acceptable here since the operations are not destructive or batch.

4 / 5

Progressive Disclosure

No bundle files exist, but the single-file body is well-organized into clearly headed sections with a one-level-deep 'See also' linking to external docs; content appropriately stays inline given the absence of a bundle.

4 / 5

Total

18

/

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 and well-scoped to a clear LLVM niche with strong capability listing, but it lacks an explicit 'Use when…' trigger clause, which caps its completeness. Adding a trigger sentence would lift the weakest dimension.

Suggestions

Add an explicit 'Use when…' clause naming the situations that should trigger this skill (e.g., 'Use when querying whether two memory references may alias, encoding language aliasing rules into the IR, or writing a custom alias analysis pass').

Include common synonyms and concrete file/extension triggers alongside the technical terms to broaden natural-language matching.

Optionally fold the version ('LLVM 22') into a trigger phrase so users referencing a specific LLVM version match naturally.

DimensionReasoningScore

Specificity

Names the domain (alias analysis in LLVM 22) and multiple concrete actions — querying AAResults, using IR-level hints (noalias, TBAA), writing a custom AA pass, and ModRef patterns — giving comprehensive coverage.

5 / 5

Completeness

The 'what' is clearly and thoroughly stated, but there is no 'Use when…' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Good coverage of natural terms an LLVM developer would say ('alias analysis', 'noalias', 'TBAA', 'AAResults', 'ModRef'), but missing common synonyms and file extensions that would push it to a 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (LLVM alias analysis) with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 suspicious

Warning

Total

15

/

16

Passed

Repository

hbarve1/tessl-llvm

Path

tiles/tessl-llvm/skills/add-alias-analysis/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.