CtrlK
BlogDocsLog inGet started
Tessl Logo

analyze-error

Error Stack Trace Analysis for dd-trace-dotnet

75

1.56x
Quality

64%

Does it follow best practices?

Impact

94%

1.56x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/analyze-error/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 well-structured, concise, and gives specific guidance including a concrete source path and output spec. Its main weakness is workflow clarity: the analysis steps lack explicit validation checkpoints or a verification loop to confirm the reconstructed root cause against the stack trace.

Suggestions

Add an explicit verification step to the workflow, e.g. "Cross-check the reconstructed root cause against every stack frame before writing it up."

Make the reproduction step concrete by specifying how to reproduce (e.g. "build a minimal repro targeting the identified code path and confirm the exception is raised").

Sequence the workflow as a numbered list so the ordering of analysis, duck-typing review, and output is unambiguous.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, avoiding explanations of basic concepts; only minor phrasings ("The goal is to: understand...") could be trimmed, fitting the efficient-with-minor-over-explanation anchor.

4 / 5

Actionability

It gives concrete, specific guidance — first line = error message, the exact DuckTyping source path, and a precise output format with a git-diff fix section — but the reproduction step stays abstract with no concrete technique, leaving minor gaps.

4 / 5

Workflow Clarity

A sequence is present (read message, parse trace, check duck typing, consult external libs, format output) but there are no explicit validation checkpoints or feedback loops, fitting the steps-listed-but-checkpoints-implicit anchor.

3 / 5

Progressive Disclosure

This is a single-purpose, ~50-line skill with no bundle files, and it is well-organized into Workflow, Considerations, Constraints, and Output Format sections, so the simple-skill exception lets it score 5 with just well-organized sections.

5 / 5

Total

16

/

20

Passed

Description

57%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 distinctive and names its domain clearly, but it only states one action and lacks any "Use when" trigger clause. Adding natural trigger phrases and a couple more concrete actions would lift completeness and trigger-term quality.

Suggestions

Add a "Use when..." clause naming natural triggers, e.g. "Use when analyzing dd-trace-dotnet exceptions, stack traces, or Datadog log intake errors."

List 2-3 concrete actions instead of one (e.g. "Reconstructs redacted frames, identifies root cause, and suggests fixes for dd-trace-dotnet exceptions").

Include natural synonyms users would say ("exception", "crash", "trace") alongside the technical phrasing.

DimensionReasoningScore

Specificity

"Error Stack Trace Analysis for dd-trace-dotnet" names the domain plus one concrete action (analysis) but does not list multiple specific actions, matching the anchor that names the domain with 1-2 concrete actions.

3 / 5

Completeness

It gives a clear "what" (analyze redacted exceptions from dd-trace-dotnet) but contains no "Use when..." trigger clause, and the guideline caps completeness at 3 when explicit trigger guidance is missing.

3 / 5

Trigger Term Quality

It surfaces relevant keywords ("Error Stack Trace Analysis", "dd-trace-dotnet") but omits natural user synonyms like "exception", "crash", or "trace", fitting the anchor with some relevant keywords but missing common variations.

3 / 5

Distinctiveness Conflict Risk

The description is bound to a single product (dd-trace-dotnet), giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

14

/

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.

Validation15 / 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
DataDog/dd-trace-dotnet
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.