edge-case-generator

Automatically identify potential boundary and exception cases from requirements, specifications, or existing code, and generate comprehensive test cases targeting boundary conditions, edge cases, and uncommon scenarios. Use this skill when analyzing programs, code repositories, functions, or APIs to discover and test corner cases, null handling, overflow conditions, empty inputs, concurrent access patterns, and other exceptional scenarios that are often missed in standard testing.

1.03x

Quality

92%

Does it follow best practices?

Impact

96%

1.03x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Discovery

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.

This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes comprehensive natural trigger terms that users would actually say, explicitly addresses both what the skill does and when to use it, and carves out a distinct niche in boundary/edge case testing that minimizes conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'identify potential boundary and exception cases', 'generate comprehensive test cases', and specifies targets like 'boundary conditions, edge cases, uncommon scenarios, corner cases, null handling, overflow conditions, empty inputs, concurrent access patterns'.	3 / 3
Completeness	Clearly answers both what ('identify potential boundary and exception cases...generate comprehensive test cases') AND when ('Use this skill when analyzing programs, code repositories, functions, or APIs to discover and test corner cases...').	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'boundary', 'exception cases', 'edge cases', 'corner cases', 'null handling', 'overflow', 'empty inputs', 'concurrent access', 'test cases', 'APIs', 'functions', 'code repositories'.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on boundary/edge case testing with distinct triggers like 'boundary conditions', 'corner cases', 'overflow conditions' that distinguish it from general testing or code analysis skills.	3 / 3
	Total	12 / 12 Passed

Implementation

85%

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

This is a strong, comprehensive skill with excellent actionability and clear workflow structure. The code examples are executable and cover multiple languages effectively. The main weakness is verbosity - some explanatory text and category descriptions could be condensed since Claude understands testing concepts. The progressive disclosure is well-implemented with appropriate references to external files.

Suggestions

Reduce explanatory prose in category introductions - Claude understands what boundary values and null handling are; focus on the specific patterns and code

Consider consolidating the checklist section with the category examples to reduce redundancy

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but verbose in places. The extensive category examples and checklists add value, but some sections explain concepts Claude already knows (e.g., what boundary values are, basic testing concepts). The content could be tightened by 30-40%.	2 / 3
Actionability	Excellent actionability with fully executable code examples across multiple languages (Python, JavaScript, Java, C, Go). Every category includes copy-paste ready test code with specific assertions and expected behaviors.	3 / 3
Workflow Clarity	Clear 5-step workflow for edge case analysis (Identify Input Domains → State/Preconditions → Output Scenarios → Interaction Patterns → Generate Test Cases). Each step has explicit substeps and the final example demonstrates the complete process.	3 / 3
Progressive Disclosure	Well-structured with clear sections progressing from core capabilities to detailed categories to patterns. Language-specific details appropriately deferred to reference files (references/python_edge_cases.md, etc.) with clear navigation links.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (671 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: ArabelaTso/Skills-4-SE
Commit: 0f00a4f

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