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++.

1.10x

Quality

81%

Does it follow best practices?

Impact

66%

1.10x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

67%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.

A well-structured, actionable skill with a clear workflow and properly separated language-specific references. Its main weakness is redundancy across the patterns, guidelines, best-practices, and tips sections, which inflates token cost.

Suggestions

Consolidate the overlapping 'common patterns', 'Best Practices', and 'Tips' sections into a single concise list to reduce redundancy and token cost (improves conciseness).

Add an explicit validation checkpoint in the workflow between inserting instrumentation and collecting data (e.g., 'Confirm instrumentation compiles and does not alter behavior before running') to strengthen feedback loops.

Move the three full Quick Start examples into the language-specific reference files, keeping only one short worked example inline, so the overview stays lean while retaining actionability.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and action-oriented, but guidance is repeated across the Workflow 'common patterns', Quick Start examples, Guidelines, Best Practices, and Tips sections, so it could be tightened; not below midpoint but not lean.	3 / 5
Actionability	Three complete, executable code examples (Java, Python, JavaScript) cover common cases and the body points to per-language reference files; minor gaps keep it just below fully copy-paste comprehensive.	4 / 5
Workflow Clarity	A clearly sequenced 6-step workflow with a minimal-to-expanded iteration loop ('Start small... Add instrumentation, run, analyze, repeat'); explicit validation is lighter than the top anchor but checkpoints are present.	4 / 5
Progressive Disclosure	Four one-level-deep, clearly signaled language references (verified to exist) with descriptive links, and the body keeps overview content inline; minor organization gaps from the body length keep it below the top anchor.	4 / 5
	Total	15 / 20 Passed

Description

96%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.

A strong, third-person description with concrete capabilities, explicit 'Use when' triggers, and broad natural keyword coverage. The only minor weakness is slight overlap risk with generic debugging skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Analyze stack traces and error messages', 'adds targeted logging, tracing, and assertions to capture variable values, execution paths, timing, and conditional branches'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both 'what' (instruments code to capture runtime data for debugging failures) and 'when' ('Use when investigating crashes, exceptions, unexpected behavior, test failures, or performance issues') with concrete triggers, matching the top anchor.	5 / 5
Trigger Term Quality	Natural user phrases are comprehensively covered ('crashes, exceptions, unexpected behavior, test failures, or performance issues') with synonyms across failure types a user would actually say.	5 / 5
Distinctiveness Conflict Risk	The 'failure-oriented instrumentation' niche is distinct with specific debugging triggers, but overlaps marginally with general debugging/logging skills, so it sits just below the minimal-conflict anchor.	4 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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: ArabelaTso/Skills-4-SE
Path: skills/failure-oriented-instrumentation/SKILL.md
Commit: 4f38503

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.