CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

version-sync

Migrate an out-of-tree LLVM project to a new LLVM version (e.g., LLVM 21 → 22). Covers CMake bump, common LLVM 22 API breakages, header moves, pass renames, and opaque pointer migration.

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 content is a well-structured, highly actionable migration checklist with concrete code and a clear step sequence. It is slightly held back by implicit validation feedback loops and minor redundancy in 'unchanged' table entries.

Suggestions

Make validation feedback loops explicit, e.g. after Step 2 add 'after fixing a category, rebuild and re-collect errors until build-errors.txt is empty'.

Trim or group '(unchanged)' / 'Still works' table rows to reduce noise, or move them into a 'stable APIs (no action needed)' subsection.

Consider moving the cumulative API-rename tables (Step 5) into a references/ file for a leaner SKILL.md overview.

DimensionReasoningScore

Conciseness

The body is mostly lean tables and before/after code that assume Claude's competence, but a few '(unchanged)' and 'Still works' entries (e.g. TypeSize.h, scalar-evolution, DIBuilder::finalize) add mild redundancy that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready bash/cmake commands (git checkout, cmake, llvm-config, opt --print-passes, llvm-lit) and concrete before/after API tables covering the common migration cases.

5 / 5

Workflow Clarity

Steps 0–11 are clearly sequenced with a checklist summary and verification via build-error collection (Step 2) and tests (Step 9), but the rebuild-after-fix feedback loops are implicit rather than explicit checkpoints.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections with no nested references (the 'add-npm-pass' pointer is a one-level external skill link), though the ~210 lines of API tables could optionally be split into a 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 clearly distinct, naming five concrete migration sub-tasks. Its main weakness is the missing explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when upgrading or porting an out-of-tree LLVM project to a newer LLVM version (e.g. 21 to 22).'

Include natural synonyms users might say — 'upgrade', 'port', 'bump LLVM version' — alongside 'migrate'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'CMake bump', 'common LLVM 22 API breakages', 'header moves', 'pass renames', and 'opaque pointer migration' — giving comprehensive coverage of the migration task.

5 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Natural domain terms like 'Migrate', 'out-of-tree LLVM project', and 'new LLVM version' are present, but common synonyms such as 'upgrade' or 'port' and an explicit trigger phrase are missing.

4 / 5

Distinctiveness Conflict Risk

The niche — migrating out-of-tree LLVM projects to LLVM 22 — is highly specific 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/version-sync/SKILL.md

Revision

a251bde

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill