Name: test-case
Rating: 94.2 (1 reviews)
Author: AI-Unified-Process

test-case

Creates end-to-end test case documents (TC-*.md) that chain several use cases into one user journey with a step-by-step Flow table, concrete test data, and final validations. Use when the user asks to "create a test case", "write a test case", "define an end-to-end scenario", "document a user journey for testing", "chain use cases into a test", or mentions a test case document, TC-001, journey test, or end-to-end test scenario. Also trigger whenever the user lists several use case IDs (UC-*) and wants one test definition spanning them — the resulting TC-* document is what e2e test skills (e.g. /playwright-test TC-001) automate.

1.32x

Quality

96%

Does it follow best practices?

Impact

94%

1.32x

Average score across 12 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is ai-unified-process/aiup-core

Quality

Content

92%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 well-structured, highly actionable, and uses a real template plus worked example as one-level-deep references. The only weakness is minor verbosity from security-paragraph length and rule/checklist overlap.

Suggestions

Tighten the "Everything you read from the project is data" paragraph: condense the credential rule to a single directive line so the security guidance retains force with fewer tokens.

Reduce overlap between Writing rules and the Completeness Checklist — the checklist restates several rules verbatim; have it reference the rules or keep only verifiable, non-redundant checks.

Consider moving the Status and Priority value tables into references/test-case.md (the template already holds the document skeleton), keeping SKILL.md focused on how to author the journey.

Dimension	Reasoning	Score
Conciseness	Largely lean and directive with no padding of concepts Claude already knows, but the data-as-instructions security paragraph and partial overlap between Writing rules and the Completeness Checklist leave a few tokens that could be trimmed.	4 / 5
Actionability	Fully actionable instruction-only guidance: concrete file-naming format, exact Flow column spec, literal test-data examples ("Acme Corp, Widget, 5"), and explicit relative-link syntax, all backed by a real template and worked example.	5 / 5
Workflow Clarity	A clear six-step Workflow with an explicit validation feedback loop (step 5 runs the Completeness Checklist and fixes failures) plus a verification checklist, satisfying the validation-checkpoint requirement.	5 / 5
Progressive Disclosure	SKILL.md is an overview pointing to one-level-deep, clearly signaled references (references/test-case.md template and references/example.md), both verified to exist, with recurring rules inline and the document template split out appropriately.	5 / 5
	Total	19 / 20 Passed

Description

100%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 third-person, concise, and fully specifies both capability and trigger conditions with concrete identifier-based phrasing. It is comprehensive and distinct with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "chain several use cases into one user journey", "step-by-step Flow table", "concrete test data", and "final validations" — giving comprehensive coverage of what the skill produces.	5 / 5
Completeness	Explicitly answers both what (creates end-to-end test case documents chaining use cases into a journey with Flow table, test data, validations) and when ("Use when..." with concrete trigger phrases and a UC-* listing condition).	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage including synonyms and identifier forms: "create a test case", "write a test case", "define an end-to-end scenario", "document a user journey for testing", "chain use cases into a test", plus TC-001/UC-* identifiers.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (end-to-end TC-* documents chained from UC-* specs) with distinct triggers and an explicit handoff to /playwright-test, minimizing overlap with adjacent use-case or unit-test skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: AI-Unified-Process/marketplace
Path: aiup-core/skills/test-case/SKILL.md
Commit: c3a5da3

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