gstack-openclaw-investigate

Use when asked to debug, fix a bug, investigate an error, or do root cause analysis, and when users report errors, stack traces, unexpected behavior, or say something stopped working.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured systematic-debugging skill: concise, highly actionable, with explicit validation checkpoints and feedback loops across all phases. It assumes Claude's intelligence while supplying only the process scaffolding Claude would not already follow.

Dimension	Reasoning	Score
Conciseness	Lean, directive instruction with no padding about what debugging is or how tools work; nearly every token earns its place and assumes Claude's competence.	3 / 3
Actionability	Concrete commands (git log --oneline -20 -- <affected-files>), named diagnostic patterns (NoMethodError, TypeError), explicit output formats, and a copy-ready DEBUG REPORT template give fully executable guidance.	3 / 3
Workflow Clarity	Five clearly sequenced phases with explicit validation checkpoints (confirm hypothesis before fixing, return-to-Phase-1 on failure, 3-strike STOP, regression test, fresh verification) and strong error-recovery feedback loops.	3 / 3
Progressive Disclosure	Self-contained SKILL.md with no bundle files; content is well-organized into focused sections and appropriately kept inline for a process skill with no external detail worth splitting.	3 / 3
	Total	12 / 12 Passed

Description

100%

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 strong description: concrete actions, natural trigger terms, explicit what-and-when guidance, and a clearly scoped debugging niche. It reads exactly as a user would describe the need that invokes the skill.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "debug, fix a bug, investigate an error, or do root cause analysis" — matching the anchor for listing several specific actions.	3 / 3
Completeness	Explicitly answers both what (debug/fix/investigate/root cause analysis) and when via a clear "Use when..." clause covering both user requests and user-reported problems.	3 / 3
Trigger Term Quality	Uses natural phrasing users actually say ("fix a bug", "investigate an error", "stack traces", "something stopped working") with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Targets a clear debugging/root-cause niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: garrytan/gstack
Commit: 11de390

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