stack-trace-generic-probe

Generates language-neutral failure checks, reproducers, and patch targets from parsed stack traces.

6.8k|540|Updated May 6, 2026
One-click install
npx skills add https://github.com/opensquilla/opensquilla --skill stack-trace-generic-probe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stack-trace-generic-probe
Source: https://github.com/opensquilla/opensquilla/tree/main/src/opensquilla/skills/bundled/stack-trace-generic-probe
Command: npx skills add https://github.com/opensquilla/opensquilla --skill stack-trace-generic-probe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a stack trace arrives in an unknown or unsupported programming language, language-specific analyzers cannot run, leaving debugging workflows without structured failure-contract checks, reproduction guidance, or patch targets.

Core Features & Use Cases

  • Language-Neutral Probing: Emits a generic LANGUAGE_PROBE result when the trace language cannot be identified.
  • Structured Output Contract: Returns schema/contract checks, boundary checks, a minimal language-neutral reproducer shape, patch targets (defensive parsing, null handling, error propagation), and verification steps.
  • Grounded Analysis: Bases every item strictly on the parsed trace supplied by the caller, without inventing files or dependencies.
  • Use Case: Inside the meta-stack-trace-investigator workflow, when a trace's language is unrecognized, this probe supplies fallback failure-contract checks and patch targets so the investigation can proceed.

Quick Start

Ask the meta-stack-trace-investigator to analyze a stack trace whose language is unknown, and it will invoke this probe to produce generic checks, a reproducer shape, and patch targets.

Frequently Asked Questions about stack-trace-generic-probe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a stack trace from an unknown programming language?

Use a language-neutral probe that derives failure-contract checks, boundary checks, and patch targets directly from the parsed trace structure. This avoids depending on language-specific analyzers that cannot run when the language is unidentified.

What is the stack-trace-generic-probe used for?

It is an internal helper for the meta-stack-trace-investigator that runs when a stack trace's language is unknown. It returns generic schema checks, a minimal reproducer shape, patch targets, and verification steps based only on the supplied trace.

Can I invoke the stack-trace-generic-probe directly as a user?

No. The skill is marked user-invocable: false and disable-model-invocation: true, so it runs only as an internal helper called by the meta-stack-trace-investigator workflow, not as a standalone user-facing tool.

Does the generic probe invent files or dependencies not in the trace?

No. Its instructions explicitly require basing every check, reproducer step, and patch target on the parsed trace supplied by the caller, and prohibit inventing files or dependencies absent from the request.

What are the limitations of language-neutral stack trace analysis?

Language-neutral analysis cannot apply runtime-specific knowledge such as framework conventions or compiler behaviors. It provides defensive parsing, null handling, and error propagation targets, but language-specific probes give deeper insight when the language is known.