CtrlK
BlogDocsLog inGet started
Tessl Logo

stack-trace-js-probe

Internal helper for meta-stack-trace-investigator. Use when a JavaScript or TypeScript stack trace needs npm/node/tsc-specific checks, reproduction guidance, and patch targets.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 compact, well-structured probe skill that gives Claude a clear output format and example commands without padding. Its main limitation is that the per-line CHECKS/PATCH_TARGETS entries are placeholders rather than concrete, executable guidance, and no verify-retry loop is specified.

Suggestions

Replace the angle-bracket placeholders in CHECKS and PATCH_TARGETS with one or two concrete filled-in examples so Claude has a copy-paste-ready reference, keeping the flexible template as a secondary note.

Add a one-line retry instruction under VERIFY (e.g., 'If verification fails, revise PATCH_TARGETS and re-run VERIFY') to close the validation feedback loop.

Clarify the fallback selection rule with a single concrete default (e.g., 'default to `npm test` and `npx tsc --noEmit`') rather than offering both generic and example phrasings.

DimensionReasoningScore

Conciseness

The body is a lean output template plus two short sentences; it assumes Claude's competence and explains nothing Claude already knows, so every token earns its place.

5 / 5

Actionability

Provides a concrete output skeleton (LANGUAGE_PROBE/CHECKS/REPRODUCER/PATCH_TARGETS/VERIFY) and example commands like `npm test -- <pattern>` and `npx tsc --noEmit`, but the CHECKS/PATCH_TARGETS lines are placeholder slots rather than fully executable code, leaving minor gaps.

4 / 5

Workflow Clarity

The template implies a clear sequence (checks → reproducer → patch targets → verify) and includes a VERIFY checkpoint, but there is no explicit fix/retry feedback loop for failed verification.

4 / 5

Progressive Disclosure

A short, single-purpose skill under 50 lines with no external references needed; the code block plus trailing note is well organized and self-contained, matching the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

87%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 well-constructed description: it states a concrete functional purpose, an explicit 'Use when' trigger, and is tightly scoped to a distinct JS/TS stack-trace niche. Minor gains possible from adding a few more natural trigger synonyms.

DimensionReasoningScore

Specificity

Names the JS/TS stack-trace domain and three concrete deliverables — 'npm/node/tsc-specific checks, reproduction guidance, and patch targets' — which is several specific actions with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (internal helper providing checks, reproduction guidance, patch targets) and 'when' via the clear 'Use when a JavaScript or TypeScript stack trace needs...' trigger phrase.

5 / 5

Trigger Term Quality

Includes natural user phrasing like 'JavaScript or TypeScript stack trace' and 'npm/node/tsc-specific checks', giving good keyword coverage though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Scoped to a narrow niche (JS/TS stack-trace probing under a named parent skill 'meta-stack-trace-investigator'), with distinct triggers and minimal overlap risk.

5 / 5

Total

18

/

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
TokenRhythm/opensquilla
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.