CtrlK
BlogDocsLog inGet started
Tessl Logo

stack-trace-rust-probe

Internal helper for meta-stack-trace-investigator. Use when a Rust panic or backtrace needs Rust-specific Result/Option checks, cargo test 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.

An extremely lean, well-structured probe-format specification that assumes Claude's competence and gives a clear sequenced output template with a verify checkpoint. The only gap is the lack of a fully worked concrete example to anchor the placeholders.

Suggestions

Include one short worked example showing the filled-in template for a representative panic (e.g., an unwrap on None) to make the placeholders concrete and lift actionability.

Add a one-line note clarifying how VERIFY relates to PATCH_TARGETS (e.g., run the suggested cargo test after applying a patch) to make the feedback loop explicit.

DimensionReasoningScore

Conciseness

The body is a lean output template plus two short notes ('Prefer narrow cargo test <name>', 'Do not recommend unsafe broad rewrites') with zero concept padding, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Provides a concrete structured template (LANGUAGE_PROBE/CHECKS/REPRODUCER/PATCH_TARGETS/VERIFY) with specific fill-in examples like 'panic/unwrap/expect/Option/Result' and 'map_err', giving mostly executable guidance; not 5 because the angle-bracket placeholders are template scaffolding rather than a fully worked, copy-paste example.

4 / 5

Workflow Clarity

The template implies a clear sequence CHECKS → REPRODUCER → PATCH_TARGETS → VERIFY with an explicit VERIFY checkpoint, fitting 'clear sequence with most checkpoints present'; not 5 because there is no error-recovery feedback loop, though the simple-skill exception keeps it strong.

4 / 5

Progressive Disclosure

Under 50 lines with no external references needed and no bundle files present (references/scripts/assets directories absent), yet the body is well-organized into a labeled template plus notes, satisfying the simple-skill top anchor.

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-scoped, third-person description that concretely states both capability and trigger conditions for a narrow Rust stack-trace probe role. It is specific and distinctive, with only minor keyword-synonym gaps.

DimensionReasoningScore

Specificity

Quotes 'Rust-specific Result/Option checks, cargo test guidance, and patch targets' — names the Rust panic/backtrace domain and lists three concrete actions, fitting the 'several specific actions; minor gaps' anchor; not 5 because the body covers additional checks (trait/lifetime/thread) absent from the description.

4 / 5

Completeness

Explicitly answers both — 'what' via 'Rust-specific Result/Option checks, cargo test guidance, and patch targets' and 'when' via 'Use when a Rust panic or backtrace needs...', with concrete trigger phrases matching the top anchor.

5 / 5

Trigger Term Quality

Contains natural developer terms 'Rust panic or backtrace', 'Result/Option checks', 'cargo test' that a user would say, matching good keyword coverage; not 5 because synonyms like 'stack trace', 'unwrap', 'expect' are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped as an 'Internal helper for meta-stack-trace-investigator' with Rust panic/backtrace-specific triggers, giving it a clear niche with minimal conflict risk against other skills.

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.