GSD Forensics (post-mortem)

Trust Score 91/100

Turn GSD runtime artifacts (.gsd/) into a filing-ready forensics report: trace symptom → root cause with file:line citations and propose a minimal fix; read-onl

triggers:forensicspost-mortemstucktrace the crashwhy did auto-mode faildebug

GitHub SKILL.md

What it does

This skill turns scattered GSD runtime artifacts (activity logs, journal, metrics, auto.lock) into a coherent, GitHub-issue-ready post-mortem. It reconstructs the failure chain, cites exact artifact paths (file and line or JSON field), names a falsifiable root cause and proposes a minimal, testable fix.

When to use it

Invoke when auto-mode exits unexpectedly, a session crashes, a unit is dispatched repeatedly (stuck loop), or when /gsd forensics or automated reports are insufficient. Use it when you need a careful, read-only investigation that preserves evidence.

What's included

Scripts: none (read-only investigative guidance)
References: detailed process steps and evidence checklist inside the skill body.
Instructions: stepwise process to locate evidence, reconstruct failure from activity logs, cross-reference the journal, name a specific root cause, and propose a minimal fix.

Compatible agents

Best for agents with filesystem access and the ability to read .gsd/ artifacts (local or attached logs). Works with dev-focused agents (Copilot/Codex/Claude) that can follow procedural diagnostics.

Audit Summary

GSD Forensics is a read-only post-mortem skill that traces runtime failures in GSD auto-mode via .gsd/ artifacts (activity logs, journal, metrics, lock files). No bundled scripts. The SKILL.md is thorough and well-structured with clear process steps, anti-patterns, and success criteria. Read-only constraint is explicitly enforced throughout.

Watch Out

Only useful if you use GSD (open-gsd/gsd-pi) — niche audience
References source map in src/resources/extensions/gsd/prompts/forensics.md which is external to the skill itself
No actual scripts to validate — purely instructional

Notes

Well-crafted skill with strong emphasis on read-only discipline and evidence-based reasoning. The success criteria and anti-patterns sections are excellent guardrails. Security is strong — no credentials, no network calls, no destructive commands, explicit prohibition on state mutation. Niche usefulness since it targets GSD users specifically. No scripts to test.

Information

Repository: gsd-pi
Stars: 610

Trust Score

Overall91

Security95

Code Quality88

Architecture85

Usefulness72

Related Skills

Starlark Dev

Create, debug, and test Kurtosis Starlark packages — write package structure, run dry-runs, and inspect plan execution for reliable orchestration.

Canary — Post-Deploy Visual Monitor

Run a short post-deploy monitor that captures screenshots, checks console errors, and compares performance against baselines to detect regressions and page fail

CTF Write-up Generator

Generate a concise, reproducible submission-style CTF writeup with a one-path solution script, metadata, and a short checklist for fast verification.

Monitoring Stack Deployer

Deploy and configure production-ready monitoring stacks (Prometheus, Grafana, Datadog) with collectors, dashboards, and alerting rules for Kubernetes, Docker, o

Agent Browser — Core

Core usage guide for agent-browser: snapshot-and-ref browser automation to navigate pages, interact with elements, extract data, take screenshots, manage sessio

Analyzing Ransomware Leak Site Intelligence

Collect and analyze ransomware data-leak site (DLS) posts to extract victim, group, sector and geographic trends for threat intelligence and proactive defense.

Analyzing Ransomware Leak Site Intelligence

Collect and analyze ransomware data-leak site (DLS) postings to extract victim, group, sector, and timeline intelligence for threat hunting and risk assessment.

Dune Analytics (MoonPay Integration)

Run Dune SQL and saved queries via the Dune REST API for on-chain analytics; pairs with MoonPay CLI to create/fund wallets for analysis.

Back to Skills