CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gsd-forensics

Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./pi/package-skills/gsd-forensics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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.

The skill body is a tight, well-structured Pi-dispatch wrapper: it gives environment-specific mechanics, concrete data sources, measurable success criteria, and strong safety rules (read-only, redaction, evidence-grounding). Its main weakness is that the core investigative workflow lives entirely in an external referenced file, so the body itself provides only partial executable guidance and no explicit step sequence for the analysis.

Suggestions

Inline a brief numbered outline of the investigation sequence (gather evidence -> check the 4 anomaly types -> write report -> present findings) so the skill is actionable even before the external workflow file is read.

Add one or two example commands for evidence gathering (e.g. 'git log --oneline -20' or how to inspect .planning/phases/*/ artifacts) to strengthen actionability.

Add a validation checkpoint for the output, such as verifying the report file was written and that every anomaly finding cites a specific commit, file, or state entry before presenting it.

DimensionReasoningScore

Conciseness

The body is lean and operational — the Pi dispatch and includes sections convey genuinely environment-specific mechanics without explaining concepts Claude already knows — though the meta commentary around <arguments> and stray blank lines could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor.

4 / 5

Actionability

Concrete elements are present (git log/git status/git diff, specific .planning/ paths, named anomaly types, report-{timestamp}.md output pattern), but the actual investigation procedure is delegated to an external workflow file not present in the bundle, leaving key execution details missing from the skill itself.

3 / 5

Workflow Clarity

The sequence is largely delegated ('Execute end-to-end' after reading the @-referenced workflow file), and while dispatch failures have an explicit stop-and-surface checkpoint, the investigative steps themselves lack explicit sequencing or validation checkpoints in this file.

3 / 5

Progressive Disclosure

Well-organized sections (objective, context, process, success criteria, critical rules) with a single clearly-signaled, one-level-deep <execution_context> reference; the placeholder path (__GSD_PI_ENGINE_ROOT__) is not directly verifiable by a reader, keeping it just below the top anchor.

4 / 5

Total

14

/

20

Passed

Description

53%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.

The description is concise and appropriately third-person, clearly naming its niche (failed GSD workflows) and its core diagnostic purpose. However, it entirely lacks a 'when to use' trigger clause and lists few concrete actions, limiting completeness and trigger discoverability. Adding a 'Use when...' clause with natural user phrasings would address the main gaps.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a GSD workflow fails, gets stuck, or leaves the repo in an unexpected state and the user wants to know what went wrong.'

Enumerate 2-3 concrete capabilities (e.g. analyzes git history and .planning/ artifacts, generates a structured forensic report, offers GitHub issue creation) to raise specificity.

Include natural synonyms users would type, such as 'investigate', 'root cause', or 'stuck workflow', to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ("failed GSD workflows") and 1-2 actions ("Post-mortem investigation", "diagnoses what went wrong"), but does not enumerate the several concrete capabilities (git history analysis, forensic report generation, issue creation) needed for a higher score.

3 / 5

Completeness

The 'what' is clear (post-mortem investigation that diagnoses failures), but there is no 'Use when...' clause or equivalent trigger guidance; the 'when' is only weakly implied by 'failed', which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"Post-mortem", "failed", and "diagnoses what went wrong" are relevant keywords, but common natural variations such as "investigate", "stuck", "debug", or "root cause" are missing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"GSD workflows" carves out a clear niche with minimal conflict risk against unrelated skills, but the absence of explicit trigger phrasing leaves minor overlap risk with generic debugging or git-analysis skills, fitting the 'mostly distinct' anchor.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

open-gsd/gsd-core

Path

pi/package-skills/gsd-forensics/SKILL.md

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.