CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stack-trace-exposure

Use when reviewing error handling middleware, API route handlers, or server responses for security-sensitive information disclosure.

Quality

75%

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 ./skills/stack-trace-exposure/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean, well-structured overview with concrete check/fix/review directives and an exemplary one-level-deep pointer to references/rule.md. Its only weaknesses are a slightly redundant threat-rationale paragraph and the absence of a post-fix validation step.

DimensionReasoningScore

Conciseness

The ~30-line body is tight and directive — a 4-bullet Quick Reference plus short Check/Fix/Explain/Code Review sections with no padding. Minor over-explanation that could be trimmed: the intro paragraph explains attacker technique and OWASP A09 rationale ('An attacker uses this information to identify the exact version of a framework or ORM, look up known CVEs...') that Claude already knows and that partially duplicates the Explain section's directive. This is anchor 4 ('Efficient; minor instances of over-explanation') rather than anchor 5's 'every token earns its place'.

4 / 5

Actionability

The guidance is concrete and executable for an instruction-only skill: 'Never return raw error objects or stack traces in API responses', 'Log full error details server-side; send only a generic message to the client', and a specific detection rule — 'Flag any location where error.stack, error.message (raw), or internal paths are serialised directly into a response body'. Per the rubric's code_vs_instruction note, absent inline code is not penalized; the minor gap is that the actual fix implementation lives one level deep in references/rule.md rather than inline. This is anchor 4, above anchor 3's 'missing key details' and short of anchor 5's copy-paste-ready coverage of common cases.

4 / 5

Workflow Clarity

The body lays out a clear single-purpose review flow — Check (what to look for), Fix (central error handler pattern), Explain, Code Review (where to flag) — so the sequence is unambiguous for a simple skill. It sits at anchor 4 ('Clear sequence with most checkpoints present') because there is no validation checkpoint after the fix (e.g., re-scan responses to confirm no error.stack or internal paths remain), which anchor 5 requires. It is not capped at 3 since this is a review/fix skill, not a destructive or batch operation.

4 / 5

Progressive Disclosure

The SKILL.md body is a concise overview and the single heavy material — 'full implementation details, code examples, and framework-specific guidance' — is clearly signaled and exactly one level deep at references/rule.md, which exists in the bundle (verified, 256 lines with code examples and framework-specific patterns). This matches anchor 5 ('Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation').

5 / 5

Total

17

/

20

Passed

Description

62%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 has an explicit and well-formed 'Use when...' trigger clause targeting a recognizable niche, but it describes only one generic action and omits high-value natural trigger terms like 'stack traces'. It is solid but under-specified relative to what the skill body actually offers (check, fix, explain, and code-review guidance).

Suggestions

Enumerate the skill's concrete capabilities in the description, e.g. 'Checks API error responses for stack traces and internal paths, implements central sanitized error handlers, and explains the disclosure risk' — this would raise specificity from anchor 3 toward anchor 4.

Add natural trigger keywords users would actually say, especially 'stack traces', 'error messages', and '500 error responses', which are currently missing despite being the skill's core subject.

Make the 'what' more concrete by naming the artifacts it works on (production error responses, catch blocks, error-handling middleware) so the description fully reaches anchor 5 for completeness.

DimensionReasoningScore

Specificity

The description names its domain ("error handling middleware, API route handlers, or server responses") and one concrete action ("reviewing ... for security-sensitive information disclosure"), but does not enumerate the distinct capabilities the skill provides (check, fix, explain, code review). This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' — it is below anchor 4, which expects several listed actions, and above anchor 2, whose actions are minimal or generic.

3 / 5

Completeness

Both parts are present: the 'what' ("reviewing ... for security-sensitive information disclosure") and an explicit 'when' ("Use when reviewing error handling middleware, API route handlers, or server responses"). It falls short of anchor 5 because the 'what' is a single generic action rather than a concrete list of what the skill does, and it is clearly above anchor 3, which requires 'when' to be missing or only weakly implied. Note the skill is single-purpose, and per the simple-skill exception an unambiguous action supports a high workflow score.

4 / 5

Trigger Term Quality

Relevant keywords are present ("error handling", "API route handlers", "server responses", "security"), but common natural phrasings are missing — most notably "stack traces" itself (the skill's name), plus synonyms like "error messages" or "500 errors". This fits anchor 3 ('Some relevant keywords but missing common variations or synonyms'), short of anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (security review of error responses) with targeted triggers, but 'reviewing ... API route handlers' has minor overlap risk with general code-review or security-review skills. Fits anchor 4 ('Mostly distinct; minor overlap risk with closely related skills') rather than anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

4 / 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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/stack-trace-exposure/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.