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.
85
78%
Does it follow best practices?
Impact
93%
1.78xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/metamorphic-property-extractor/SKILL.mdQuality
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 well-crafted description with strong specificity and completeness, including an explicit 'Use when...' clause with multiple trigger scenarios. The main weakness is that trigger terms are highly technical and may not match how users naturally phrase requests for this functionality. The description excels at distinguishing itself from other skills through its specialized metamorphic testing focus.
Suggestions
Add more natural user phrases alongside technical terms, such as 'property-based testing', 'finding test invariants', or 'automatic test generation'
| 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 around metamorphic testing and property discovery. The specific terminology (metamorphic properties, test oracles, input invariances) creates a clear, distinct domain 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 property extraction output and verification results, making it harder to understand what success looks like. The workflow would benefit from error handling guidance and validation checkpoints.
Suggestions
Add an example showing sample input function and the resulting properties.json output structure
Include what to do when verification fails - how to interpret errors and iterate on property refinement
Show a concrete example of at least one property applied to real code (e.g., demonstrating symmetry detection on a specific function)
| 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 apply them to actual code or what the output looks like. | 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 results, or feedback loops for iterating on discovered properties. | 2 / 3 |
Progressive Disclosure | Clean structure with overview, workflow, property definitions, and well-signaled one-level-deep references to detailed 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.
- Repository
- ArabelaTso/Skills-4-SE
- Commit
0f00a4f
- 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.