CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/uat-script-author

Emits User Acceptance Testing scripts in stakeholder-readable format - pre-conditions / business-language steps / expected business outcome / pass-fail / sign-off. Tailored for non-developer testers (end users, SMEs, solution owners) per the UAT canonical definition. Output is one TC per stakeholder-meaningful scenario with explicit sign-off, suitable for compliance / contract / audit records. Use when a release requires formal UAT before sign-off - typical for B2B contracts, regulated industries, or any delivery where the customer's acceptance is the contractual gate.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A dense, actionable skill body with a complete template, explicit validation feedback loop, and clean organization. The only weakness is minor redundancy of the three-tasks rule across Step 1 and Step 4.

Suggestions

Consolidate the 'three most common or difficult tasks' guidance into one place (Step 1 or Step 4) and cross-reference it from the other to remove the duplication.

Tighten the Overview so it frames the audience without restating the canonical UAT definition already covered by the linked reference.

DimensionReasoningScore

Conciseness

Mostly efficient and actionable, but the 'three most common or difficult tasks' rule is restated in both Step 1 and Step 4, and the Overview lightly restates context, so it could be tightened.

2 / 3

Actionability

Provides a complete, copy-paste-ready UAT template with concrete pre-conditions, step/outcome tables, AC-mapping table, sign-off block, and an implementation-to-business-language translation table.

3 / 3

Workflow Clarity

Steps 1-6 are clearly sequenced and Step 5 includes an explicit validation feedback loop: re-run failed scripts and 'do not proceed to sign-off with an open failing AC'.

3 / 3

Progressive Disclosure

Well-organized sections with a clearly signaled, one-level-deep References list (uat-wiki, sibling skill, upstream plugin); no nested references and no bundle files to misroute.

3 / 3

Total

11

/

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, third-person description that states concrete capabilities, gives an explicit 'Use when' trigger with natural domain terms, and carves out a distinct niche. It answers both what and when without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - 'pre-conditions / business-language steps / expected business outcome / pass-fail / sign-off' and 'one TC per stakeholder-meaningful scenario with explicit sign-off'.

3 / 3

Completeness

Explicitly answers what ('Emits User Acceptance Testing scripts...') and when ('Use when a release requires formal UAT before sign-off...').

3 / 3

Trigger Term Quality

Natural domain terms a requester would say are well covered: 'UAT', 'sign-off', 'B2B contracts', 'regulated industries', 'acceptance'.

3 / 3

Distinctiveness Conflict Risk

Clear niche (stakeholder-facing UAT sign-off scripts) with distinct triggers and an explicit contrast to the developer-facing manual-test-script-author sibling.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents