CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lit-filecheck

Write lit tests with FileCheck for LLVM 22 IR transforms, pass output, and codegen. Covers RUN lines, CHECK patterns, common directives, negative checks, and running tests with llvm-lit.

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

The canonical home for this skill is lit-filecheck in hbarve1/tessl-llvm

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 executable examples throughout and a sensible step-by-step workflow including a debugging feedback loop. It is concise and well-structured, though the main write-test flow could surface an explicit validation checkpoint.

Suggestions

Make the validate-then-iterate loop explicit in the main workflow (e.g. 'run tests → if failing, use --dump-input=fail to diagnose → fix → re-run') rather than relegating it to the debugging section.

Consider splitting the directive reference (Step 3) or lit.cfg.py config into a reference file to shorten the single-file body and ease navigation.

DimensionReasoningScore

Conciseness

Lean and efficient — assumes Claude knows LLVM/IR/opt/llc without padding explanations — with only minor instances (e.g. inline glosses) that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready RUN lines, opt/llc invocations, lit.cfg.py, and debugging commands cover the common cases comprehensively.

5 / 5

Workflow Clarity

Steps 0–10 give a clear sequence with a debugging feedback loop in Step 10 (--dump-input, run manually, inspect output), though validation within the main write-test flow is mostly implicit.

4 / 5

Progressive Disclosure

No bundle files exist, but the body is well-organized into clearly headed sections; as a single cohesive skill it is appropriately placed, with only minor length-related organization gaps.

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 and distinctive with strong action coverage, but lacks an explicit 'Use when...' trigger clause, capping completeness. Adding a trigger phrase would round it out.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when adding tests for an LLVM pass, IR transform, or codegen output.'

Add natural synonyms and file extensions like '.ll files' or 'regression tests' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'IR transforms, pass output, and codegen' plus 'RUN lines, CHECK patterns, common directives, negative checks, and running tests with llvm-lit' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' trigger clause; the 'when' is only weakly implied, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural domain keywords (lit tests, FileCheck, LLVM, IR transforms, codegen) that a user would say, but missing common synonyms and file extensions like .ll or 'regression test'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (LLVM 22 lit/FileCheck testing) with distinct, specific 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

.tessl/tiles/hbarve1/tessl-llvm/skills/lit-filecheck/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.