CtrlK
BlogDocsLog inGet started
Tessl Logo

add-exception-handling

Add exception handling (try/catch/finally) to an LLVM 22 IR frontend using invoke, landingpad, and the Itanium C++ ABI. Covers personality function, invoke vs call, catch dispatch, __cxa_begin/end_catch, resume, cleanup blocks, and Windows SEH notes.

72

Quality

87%

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

92%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a high-quality, expert-level skill that provides concrete, executable LLVM C++ API code for implementing exception handling. The step-by-step workflow is logically sequenced, the consolidated example ties everything together, and the common mistakes section serves as an effective validation checklist. The only minor weakness is that the content is somewhat long for a single SKILL.md and could benefit from splitting detailed steps into a referenced file.

DimensionReasoningScore

Conciseness

The skill is lean and efficient throughout. It assumes Claude knows C++, LLVM basics, and compiler concepts. Comments are minimal and purposeful, code examples carry the weight, and there's no padding or explanation of obvious concepts.

3 / 3

Actionability

Every step provides fully executable C++ code using the LLVM API with correct types, function signatures, and method calls. The consolidated example at the end is copy-paste ready and demonstrates a complete try/catch pattern.

3 / 3

Workflow Clarity

The 8-step sequence (Steps 0-7) is clearly ordered with logical dependencies. Validation is addressed in the 'Common mistakes' section with the explicit `verifyModule` call, and the workflow includes error recovery via resume/rethrow paths. The consolidated example ties all steps together.

3 / 3

Progressive Disclosure

The content is well-structured with clear sections and a consolidated example, but it's a fairly long single file (~180 lines of content). The Windows SEH section appropriately links to external docs, but the main content could benefit from splitting detailed API reference into a separate file while keeping the SKILL.md as an overview.

2 / 3

Total

11

/

12

Passed

Description

82%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong, highly specific description that clearly identifies a narrow technical domain (LLVM IR exception handling) with excellent trigger terms that match what users in this space would naturally say. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The technical depth and specificity are exemplary.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user is building an LLVM compiler frontend and needs to implement exception handling, or asks about invoke/landingpad instructions, C++ ABI exception support, or cleanup/resume semantics in LLVM IR.'

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and concepts: invoke, landingpad, personality function, invoke vs call, catch dispatch, __cxa_begin/end_catch, resume, cleanup blocks, and Windows SEH notes. Very detailed enumeration of capabilities.

3 / 3

Completeness

Clearly answers 'what does this do' with detailed coverage of exception handling in LLVM IR, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes highly specific natural keywords a user working in this domain would use: 'exception handling', 'try/catch/finally', 'LLVM', 'IR', 'invoke', 'landingpad', 'Itanium C++ ABI', '__cxa_begin_catch', 'cleanup blocks', 'Windows SEH'. These are the exact terms someone would mention when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Extremely niche and specific to LLVM 22 IR frontend exception handling with Itanium C++ ABI. This is unlikely to conflict with any other skill given its highly specialized domain and precise technical terminology.

3 / 3

Total

11

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
hbarve1/tessl-llvm
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.