CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-debug-info

Add DWARF debug info to an existing LLVM 22 IR frontend. Covers DIBuilder setup, compile unit, function subprograms, local variable declarations, source locations on instructions, and module flags.

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 add-debug-info 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 a tight, highly actionable, well-sequenced guide with real LLVM 22 code and built-in validation steps; its only minor gaps are a couple of trimmable comments and a less-than-explicit error-recovery loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's LLVM competence, with minimal prose around complete code blocks; a few inline comments ('closest standard language code', 'insertDeclare returns DbgInstPtr in LLVM 22 — usually ignored') could be trimmed but overall token use is efficient.

4 / 5

Actionability

Every step ships real, copy-paste-ready LLVM 22 API calls (DIBuilder, createCompileUnit, createFunction, insertDeclare, DILocation) plus concrete shell commands (clang -c, llvm-dwarfdump --verify, lldb), fully covering the common cases.

5 / 5

Workflow Clarity

Steps 0–9 are clearly sequenced with explicit validation checkpoints (verifyModule in Step 7, llvm-dwarfdump --verify in Step 8) and a 'Common mistakes' checklist, but the error-recovery feedback loop ('if errors, fix and re-validate') is not spelled out as explicitly as the top anchor.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections (Steps 0–9 plus Common mistakes) and the linear procedural nature justifies keeping it inline in SKILL.md with no external bundle files, though a complete worked example or extended DIType reference 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.

The description is specific, action-rich, and highly distinct, but it omits any explicit 'when to use' trigger guidance, which caps its completeness score.

Suggestions

Add an explicit trigger clause such as 'Use when adding debuggable output (gdb/lldb stepping and variable inspection) to an LLVM IR code generator' to satisfy the 'when' half of completeness.

Include a couple of natural user-facing synonyms like 'debuggable', 'gdb/lldb', or 'source-line mapping' to broaden trigger-term coverage.

Keep the existing concrete action list intact — it is the strongest part of the description.

DimensionReasoningScore

Specificity

The description lists six concrete sub-tasks ('DIBuilder setup, compile unit, function subprograms, local variable declarations, source locations on instructions, and module flags'), giving comprehensive coverage of the skill's actions rather than vague language.

5 / 5

Completeness

A clear, comprehensive 'what' is present but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

'Add DWARF debug info' and 'debug info' are natural terms for the target audience, but common synonyms like 'debuggable', 'gdb/lldb support', or 'source-line mapping' are absent, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Add DWARF debug info to an existing LLVM 22 IR frontend' carves out a precise niche with distinct, domain-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/add-debug-info/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.