stack-trace-go-probe

Internal helper for meta-stack-trace-investigator. Use when a Go panic or stack trace needs Go-specific nil/error checks, go test reproducer guidance, and patch targets.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

A concise, well-structured probe skill that respects token budget and assumes Claude's competence. Its main limitation is that the guidance is template-placeholder-driven rather than fully executable, which slightly limits copy-paste actionability.

Suggestions

Replace one or two placeholder lines (e.g. the REPRODUCER and PATCH_TARGETS) with a concrete filled-in example so the template is copy-paste ready.

Add a brief one-line note on how to choose between 'nil pointer' and 'error-return' checks based on trace cues, to raise actionability without padding.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: a short output template plus two guidance lines, with no padding or explanation of concepts Claude already knows; every token earns its place.	5 / 5
Actionability	Provides a structured template and concrete guidance ('narrow go test ./path -run TestName'), but the body is template/placeholder-driven (e.g. '<nil guard>', '<minimal go test>') rather than fully executable, copy-paste-ready code.	3 / 5
Workflow Clarity	A clear sequence is implied via the LANGUAGE_PROBE/CHECKS/REPRODUCER/PATCH_TARGETS/VERIFY template with an explicit VERIFY step, but it is a single-action probe rather than a multi-step process with error-recovery feedback loops.	4 / 5
Progressive Disclosure	A short, single-purpose skill with no external references needed; content is well-organized into one self-contained block, which is appropriate for a sub-50-line skill.	5 / 5
	Total	17 / 20 Passed

Description

86%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 tight, third-person description that clearly states both capability and trigger conditions for a Go-specific stack-trace helper. It is specific and distinct, with only minor room to broaden trigger-term synonyms.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('Go-specific nil/error checks', 'go test reproducer guidance', 'patch targets') but these are framed as categories of output rather than fully enumerated actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' (Go-specific nil/error checks, reproducer guidance, patch targets) and 'when' via a clear 'Use when a Go panic or stack trace needs...' trigger clause.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('Go panic or stack trace', 'nil/error checks') with good coverage; missing common synonyms or file extensions, so not comprehensive.	4 / 5
Distinctiveness Conflict Risk	Scopes to a niche (Go-specific stack-trace analysis as a helper for a named investigator) with distinct triggers, making conflict with unrelated skills unlikely.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: TokenRhythm/opensquilla
Path: src/opensquilla/skills/bundled/stack-trace-go-probe/SKILL.md
Commit: 94ac35e

Reviewed: 4 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.