Menu
Use GliderTrace for .NET runtime evidence, test runs, failure summaries, exceptions, counters, traces, dumps, and artifact indexing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use TGlider for TypeScript and JavaScript semantic navigation, references, diagnostics, dependency topology, impact analysis, and refactoring.
Use GliderMCP for C#/.NET navigation, diagnostics, references, call graphs, impact analysis, and safe refactoring.
Use Scout for repo-wide code search in any language - ranked fuzzy discovery, exhaustive strict literal, regex, and word search, plus structural patterns, symbol outlines, and semantic queries.
| name | glider-trace-runtime |
| description | Use GliderTrace for .NET runtime evidence, test runs, failure summaries, exceptions, counters, traces, dumps, and artifact indexing. |
Use GliderTrace when working in a C# or .NET repository and the task needs runtime evidence rather than static source inspection alone.
Prefer GliderTrace for test runs, command runs, failure summaries, exception and stack evidence, stdout/stderr summaries, counters, traces, dumps, GC dumps, and artifact indexing. Use trace_status first when you need to confirm server state, workspace, artifact root, allowed commands, and local dependency availability.
For investigations, run commands through trace tools so stdout, stderr, exit status, timings, findings, and artifacts remain connected to one session. Use test-specific tools for .NET test evidence, and query/export session artifacts when summarizing the failure or handing evidence back to the user.
When an investigation needs to locate code, logs, or artifacts by text across the repository, prefer Scout's find if Scout is installed, and fall back to shell search when it is not. Use plain shell commands only for simple file operations or when captured runtime evidence is not useful.
