room-migration-audit

Audit M3UAndroid Room schema and migration changes for versioning, schema artifacts, data preservation, indices, defaults, DAO compatibility, and migration validation.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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.

A compact, well-structured audit skill with concrete validation and a clear sequenced workflow. The main gap is an implicit rather than explicit fail→fix→retry feedback loop in the validation step.

Suggestions

Make the validation feedback loop explicit, e.g. "If tests fail, cite the failing migration path, propose a fix, and re-run."

Tighten the abstract Process steps (e.g. "Compare old and new schema semantics") with a concrete method such as diffing the schema JSON fields.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — short bulleted sections with no explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	Provides a concrete validation command (`./gradlew :data:testDebugUnitTest`) and verifiable audit-check criteria, though some Process steps ("Compare old and new schema semantics") remain slightly abstract.	4 / 5
Workflow Clarity	A clear 5-step Process plus an explicit Validation checkpoint with a fallback ("state the remaining migration risk"), but the error-recovery feedback loop is only weakly articulated.	4 / 5
Progressive Disclosure	Under 50 lines with no bundle files needed; content is organized into clearly labeled sections (When To Use, Required Context, Audit Checks, Process, Validation, Output) with easy navigation.	5 / 5
	Total	18 / 20 Passed

Description

75%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.

A specific, well-scoped description that clearly conveys what the skill audits, but it omits any explicit "when to use" trigger clause, which limits completeness. Adding a Use-when clause would lift the weakest dimension.

Suggestions

Add an explicit trigger clause, e.g. "Use when a task changes Room entities, DAOs, database versions, migrations, or schema JSON."

Include natural synonyms or file extensions (e.g. "Room database", "schema JSON", ".db") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete audit actions — "versioning, schema artifacts, data preservation, indices, defaults, DAO compatibility, and migration validation" — giving comprehensive coverage of the domain.	5 / 5
Completeness	The "what" is clear and detailed, but there is no "Use when…" clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Strong domain keywords ("Room schema", "migration", "DAO", "indices") a developer would naturally say, but no synonyms or file extensions (e.g. ".db", schema JSON) are included.	4 / 5
Distinctiveness Conflict Risk	Scoped specifically to M3UAndroid Room schema/migration auditing — a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: oxyroid/M3UAndroid
Path: .claude/skills/room-migration-audit/SKILL.md
Commit: 650d06b

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