CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-anything-lldb

Stateful LLDB debugging via LLDB Python API

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./lldb/agent-harness/cli_anything/lldb/skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 strong, highly actionable command reference with executable examples and a clear error contract, held back by duplication between the DAP section and Agent Usage Notes and by the absence of an explicit ordered debugging workflow with validation checkpoints. Organization is good, though the DAP deep-dive might live better in a separate reference file.

Suggestions

Deduplicate the DAP behavioral guidance: the Agent Usage Notes bullets on non-blocking continue, async-interrupt pause, interrupt-before-breakpoint-mutation, and stop-rule profiles repeat the DAP section nearly verbatim — keep one canonical location and cross-reference it.

Add a short explicit workflow (1. target create, 2. process launch/attach, 3. breakpoint set, 4. continue, 5. thread backtrace / frame locals, 6. session close) with the structured-error check as a validation checkpoint at each step.

Move the deep DAP protocol details (stop-rule profiles, autoContinueInternalBreakpoints, non-blocking continue semantics) into a reference file and keep a brief DAP overview with the entry-point commands in SKILL.md.

DimensionReasoningScore

Conciseness

The body is a lean command reference with no concept over-explanation, but the "Agent Usage Notes" section repeats DAP guidance already stated verbatim in the DAP section (non-blocking continue, async-interrupt pause, interrupt-before-breakpoint-mutation, stop-rule profiles/restart), and "Quick Commands" duplicates "Command Groups". Mostly efficient but could be noticeably tightened, fitting anchor 3 rather than 4's "minor instances."

3 / 5

Actionability

Commands are fully executable and copy-paste ready with concrete flags (e.g. "breakpoint set --file main.c --line 42 --condition \"i > 10\"", "memory find \"needle\" --start 0x1000 --size 4096"), and the structured error contract "{"error": "...", "type": "..."}" tells the agent how failures look. Coverage spans the common debugging cases.

5 / 5

Workflow Clarity

The typical sequence (target create → launch/attach → set breakpoints → continue → inspect) is only implicit in listing order; the sole sequencing note is "Call `target create` before process or core commands." There are no explicit ordered workflow steps or validation checkpoints beyond "Expect structured errors," matching anchor 3 (sequence present but checkpoints missing or implicit) rather than 4.

3 / 5

Progressive Disclosure

The body is well organized into capabilities, quick commands, DAP details, command groups, and usage notes, with content mostly appropriately placed inline for a ~150-line CLI skill with no bundle files. The ~40 lines of deep DAP behavioral prose (stop-rule profiles, auto-continue semantics) could arguably move to a reference file, which keeps this below 5.

4 / 5

Total

15

/

20

Passed

Description

48%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 short and names a clear, specific niche, but it functions only as a domain label: it lists no concrete capabilities, includes no trigger guidance for when the skill should activate, and misses natural terms users would say. Adding a capability list and a "Use when..." clause would lift most dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions LLDB, debugging native processes, breakpoints, backtraces, or core dumps."

Enumerate 2-4 concrete capabilities in the description (set breakpoints, inspect frames/locals, read memory, load core dumps) to raise specificity from a domain label to an action list.

Include natural synonyms and related trigger terms ("debugger", "crash", "attach to process") so the skill matches how users actually phrase debugging requests.

DimensionReasoningScore

Specificity

"Stateful LLDB debugging via LLDB Python API" names the domain and adds modifiers but lists no concrete actions (no breakpoints, backtraces, core dumps, memory inspection). It matches anchor 2 ("Names the domain but actions are minimal or generic"), not 3, which requires 1-2 concrete actions.

2 / 5

Completeness

A domain-level "what" is present (stateful LLDB debugging) but the "when" is entirely absent — no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3. Not 2 because the what is unambiguous; not 4 because there is no when clause at all.

3 / 5

Trigger Term Quality

"LLDB" and "debugging" are natural terms a user would say, but common variations and synonyms ("debugger", "breakpoints", "backtrace", "core dump", "crash") are missing. This is "some relevant keywords but missing common variations," not 4's "good keyword coverage."

3 / 5

Distinctiveness Conflict Risk

"LLDB" carves a clear, distinct niche with minimal conflict risk, but the bare "debugging" keyword leaves minor overlap with other debugger/debugging-adjacent skills. Mostly distinct with minor overlap risk fits anchor 4; not 5 because distinct trigger phrases are absent.

4 / 5

Total

12

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

HKUDS/CLI-Anything

Path

lldb/agent-harness/cli_anything/lldb/skills/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.