CtrlK
BlogDocsLog inGet started
Tessl Logo

failure-oriented-instrumentation

Selectively instruments code to capture runtime data for debugging failures and bugs. Use when investigating crashes, exceptions, unexpected behavior, test failures, or performance issues. Analyzes stack traces and error messages to identify suspicious code regions, then adds targeted logging, tracing, and assertions to capture variable values, execution paths, timing, and conditional branches. Supports Python, JavaScript/TypeScript, Java, and C/C++.

88

1.10x
Quality

92%

Does it follow best practices?

Impact

66%

1.10x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Evaluation results

76%

13%

Debug Incorrect Order Total Calculation

Python failure instrumentation patterns

Criteria
Without context
With context

logging module used

100%

100%

getLogger(__name__)

0%

25%

DEBUG level for tracing

87%

100%

ERROR with exc_info

0%

0%

Variable names in messages

100%

100%

Entry/exit markers

25%

100%

Branch decisions logged

100%

100%

Decorator or context manager

0%

0%

Minimal-first approach

50%

100%

No password/token logging

100%

100%

No side effects

100%

100%

Loop iterations tracked

100%

100%

64%

1%

Diagnose Intermittent Timeout in Data Sync Service

JavaScript async and proxy instrumentation

Criteria
Without context
With context

console.log with timestamps

100%

100%

performance.now() for timing

0%

0%

debug module used

0%

0%

Async ENTER/EXIT markers

62%

75%

Proxy-based instrumentation

0%

0%

Async error logging

37%

37%

External dependency timing

100%

100%

State variables captured

100%

100%

No API key or token logging

100%

100%

Minimal scope

100%

87%

Variable names in messages

100%

100%

No behavior change

83%

100%

60%

4%

Diagnose Segmentation Fault in Image Processing Pipeline

C/C++ macro and RAII instrumentation

Criteria
Without context
With context

fprintf to stderr

100%

100%

DEBUG macro guard

0%

10%

LOG_DEBUG macro defined

87%

100%

LOG_ENTER/LOG_EXIT macros

25%

100%

RAII instrumentation class

70%

0%

std::chrono timing

0%

22%

Variable values at crash site

100%

100%

Assertions added

87%

62%

GDB script produced

0%

33%

Minimal scope

100%

100%

No behavior change

50%

37%

instrumentation_plan.md produced

100%

100%

Repository
ArabelaTso/Skills-4-SE
Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

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.