multi-version-behavior-comparator

Compare behavior across multiple versions of programs or repositories. Use when you need to analyze how functionality changes between versions, identify regressions, compare outputs and exceptions, or validate upgrades. The skill compares execution behavior, test results, outputs, exceptions, and observable states across versions, generating detailed reports showing behavioral divergences, potential regressions, added/removed functionality, and areas requiring validation. Supports multiple programming languages and can work with test suites or execution traces.

1.58x

Quality

75%

Does it follow best practices?

Impact

100%

1.58x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/multi-version-behavior-comparator/SKILL.md

Quality

Content

61%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 concise and well-structured with executable-looking commands, but two issues hold it back: the referenced scripts/compare.py is missing from the bundle (hurting actionability and navigation), and the batch comparison workflow lacks any validation or feedback-loop checkpoints, which caps workflow clarity. The Overview/Report sections also slightly restate the frontmatter.

Suggestions

Provide the referenced scripts/compare.py (or a scripts/ bundle) so the Quick Start and Usage commands are actually executable, or replace the script reference with inline, self-contained guidance.

Add a validation/feedback step to the workflow — e.g., after generating the report, verify it covers all requested versions, and instructions for triaging confirmed regressions before acting on them — to lift workflow clarity past the batch-operation cap of 3.

Trim the Overview paragraph and the Comparison Report bullet list, which restate the frontmatter description, to remove redundancy and improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is lean and mostly assumes competence — Quick Start commands and bulleted lists carry the content efficiently — but the Overview paragraph and the Comparison Report section restate the frontmatter description, minor over-explanation that could be trimmed; not 5 because of that redundancy, not 3 because padding is minimal.	4 / 5
Actionability	Provides concrete, copy-paste-ready commands ("python scripts/compare.py v1.0/ v2.0/", "--tests", "--output report.json"), but the referenced scripts/compare.py does not exist in the bundle, so the guidance is incomplete and not actually executable as written; fits the 3 anchor (concrete guidance but incomplete, missing key details) rather than 4.	3 / 5
Workflow Clarity	Quick Start shows a rough sequence (compare → with tests → generate report), but this batch operation has no validation or verification checkpoint — nothing on how to confirm the report is complete, handle a failed comparison, or triage detected regressions; per the rubric's batch-operation cap, workflow_clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Well-organized sections (Overview, Quick Start, What Gets Compared, Comparison Report, Usage, Tips) suit a sub-50-line skill, but the body references scripts/compare.py which is absent from the bundle — a navigation gap that keeps it from 5; not 3 because the structure itself is clean and clearly signaled.	4 / 5
	Total	14 / 20 Passed

Description

88%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 strong: it states concrete capabilities, uses third person, and provides an explicit, multi-trigger "Use when" clause answering both what and when. Its main limitation is slightly incomplete keyword coverage (missing synonyms like migration/diff) and minor overlap with general comparison skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "compare outputs and exceptions", "identify regressions", "validate upgrades", "generating detailed reports showing behavioral divergences, potential regressions, added/removed functionality" — giving comprehensive coverage; not the 4 anchor which expects only "several" actions with minor gaps.	5 / 5
Completeness	Explicitly answers both what ("Compare behavior across multiple versions... generating detailed reports") and when ("Use when you need to analyze how functionality changes between versions, identify regressions... validate upgrades") with concrete trigger phrases; not 4 because the "when" is explicit and specific rather than weakly implied.	5 / 5
Trigger Term Quality	Has a natural trigger clause ("Use when you need to analyze how functionality changes between versions, identify regressions, compare outputs and exceptions, or validate upgrades") with good keyword coverage, but misses common synonyms like "migration", "diff", or "before/after" that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	The "multi-version behavior comparison / validate upgrades" niche is mostly distinct, but "compare outputs", "regressions", and "validate upgrades" carry minor overlap risk with general diff or code-review skills; not 5 because conflict risk is not quite minimal.	4 / 5
	Total	18 / 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
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	15 / 16 Passed

Repository: ArabelaTso/Skills-4-SE
Path: skills/multi-version-behavior-comparator/SKILL.md
Commit: 4f38503

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