CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gsd-audit-uat

Cross-phase audit of all outstanding UAT and verification items

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

86%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 body is a lean, highly operational dispatcher: exact commands, tool parameters, error-handling rules, and precise scope globs with no wasted tokens. The core workflow is appropriately delegated to a single clearly-signaled one-level-deep reference. Its only weakness is that in-body actionable detail ends at the dispatch mechanics.

DimensionReasoningScore

Conciseness

Every sentence is operational (dispatch parameters, fail-closed rules, exact globs, exact file path) with zero explanation of concepts Claude already knows; the body assumes competence throughout, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Guidance is concrete and executable — the exact invocation command, gsd_dispatch role/task parameters, and precise glob patterns — but the core audit steps (scan, cross-reference, produce test plan) are only named in the objective and deferred to an external workflow file, leaving a minor gap versus fully copy-paste-ready coverage.

4 / 5

Workflow Clarity

Ordering is explicit ('Before doing anything else, read every file...') with a clear error-recovery loop ('If gsd_dispatch reports the role unresolved or the child failed, STOP... offer to skip and continue; if required, stop the run'), but the main step sequence itself lives in the referenced workflow file rather than being laid out with checkpoints in-body, so it falls short of the 5 anchor.

4 / 5

Progressive Disclosure

This is a short, single-purpose skill with well-organized sections; its single external reference (@__GSD_PI_ENGINE_ROOT__/gsd-core/workflows/audit-uat.md) is one level deep, clearly signaled under <execution_context>, and accompanied by explicit read-first instructions, matching the simple-skill exception for a 5.

5 / 5

Total

18

/

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 states a clear, appropriately niche 'what' but entirely lacks trigger guidance and natural-language synonyms. It reads as a functional label rather than a discovery-optimized description. Adding an explicit 'Use when...' clause and enumerating the concrete actions would lift most dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to audit pending UAT items, run user acceptance testing checks, or review verification status across phases.'

Enumerate the concrete actions from the body: 'Scans phase planning files for pending, skipped, blocked, and human-needed UAT items, cross-references them against the codebase to detect stale documentation, and produces a prioritized human test plan.'

Include natural synonyms such as 'user acceptance testing', 'QA', 'test plan', and 'verification checklist' so users' phrasing matches without knowing the term 'UAT'.

DimensionReasoningScore

Specificity

Names the domain ("UAT and verification items") and one concrete action ("audit") but omits the actual capabilities the skill performs (scan phases, cross-reference codebase, produce a test plan), so coverage is not comprehensive — matching the 3 anchor rather than 4.

3 / 5

Completeness

The 'what' is clear (cross-phase audit of outstanding UAT and verification items) but there is no 'Use when...' clause or any trigger guidance, which caps completeness at 3; it cannot score 4 without an explicit 'when'.

3 / 5

Trigger Term Quality

"audit", "UAT", and "verification" are relevant keywords, but common natural variations users would say ("testing", "QA", "test plan", "acceptance testing") are missing, fitting the 'some relevant keywords but missing variations' anchor rather than good coverage.

3 / 5

Distinctiveness Conflict Risk

"UAT" and "verification items" scoped to phases form a mostly distinct niche with only minor overlap risk against general review/audit skills; it lacks the explicit trigger phrases that would distinguish it further for a 5.

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-audit-uat/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.