metamorphic-property-extractor
Automatically identify metamorphic properties (symmetry, linearity, additivity, input invariances) from programs or functions. Use when generating metamorphic tests, discovering program properties, validating transformations, or creating test oracles without explicit specifications. Analyzes control flow, data flow, and sample executions to output structured properties for metamorphic test generation and verification.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill metamorphic-property-extractor82
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
85%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 strong, well-structured skill description that clearly defines a specialized testing capability. It excels at specificity and completeness with an explicit 'Use when...' clause and concrete examples of metamorphic properties. The main weakness is that trigger terms are highly technical, which may limit discoverability when users describe their needs in more casual language.
Suggestions
Add more natural language trigger terms that users might actually say, such as 'property-based testing', 'automatic test generation', or 'finding program invariants'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'identify metamorphic properties (symmetry, linearity, additivity, input invariances)', 'Analyzes control flow, data flow, and sample executions', 'output structured properties'. The parenthetical examples add excellent specificity. | 3 / 3 |
Completeness | Clearly answers both what ('identify metamorphic properties', 'analyzes control flow, data flow') AND when ('Use when generating metamorphic tests, discovering program properties, validating transformations, or creating test oracles'). Has explicit 'Use when...' clause with multiple trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes some relevant technical terms like 'metamorphic tests', 'test oracles', 'transformations', but these are specialized jargon. Missing more natural user phrases like 'property-based testing', 'test generation', or simpler variations users might actually say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specialized niche focused specifically on metamorphic testing and property discovery. The specific terminology (metamorphic properties, test oracles, input invariances) creates clear boundaries unlikely to conflict with general testing or code analysis skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is admirably concise and well-structured, respecting token budget while providing clear navigation to additional resources. However, it lacks concrete examples of what the property extraction output looks like and what to do when verification fails, making it less actionable for practical use.
Suggestions
Add an example of the properties.json output format so Claude knows what to expect and how to interpret results
Include a brief error handling section: what to do if extraction finds no properties or verification fails
Add one concrete example showing a function and its extracted properties to make the abstract mathematical notation actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what metamorphic testing is or how properties work - assumes Claude's competence. Every section adds value without padding. | 3 / 3 |
Actionability | Provides concrete CLI commands for extraction and verification, but the property definitions are abstract mathematical notation without executable examples showing how to actually use them in tests or what the scripts produce. | 2 / 3 |
Workflow Clarity | Two-step workflow is clear but lacks validation checkpoints. No guidance on what to do if property extraction fails, how to interpret the JSON output, or how to handle verification failures. | 2 / 3 |
Progressive Disclosure | Clean structure with overview, workflow, property definitions, and well-signaled one-level-deep references to the testing guide and scripts. Appropriately concise for a skill file. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.