room-migration-audit

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

Quality

83%

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

100%

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

The content is lean, actionable, and well-structured with a clear sequenced workflow and validation checkpoint. As a simple single-purpose skill it needs no bundle references and organizes its material effectively.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations or padding; it assumes Claude's competence and every section earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	Concrete audit checks, a specific executable validation command ('./gradlew :data:testDebugUnitTest'), and explicit file targets give actionable, copy-paste-ready guidance for this instruction-only skill.	3 / 3
Workflow Clarity	A clearly sequenced five-step Process with an explicit Validation checkpoint and error-recovery guidance ('state the remaining migration risk') fits the anchor for clear sequence with validation steps.	3 / 3
Progressive Disclosure	This is a short (under 50 lines), single-purpose skill with no bundle files; its well-organized sections satisfy the simple-skill scoring note allowing a 3 without external references.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 specific and distinct within its niche, but lacks natural trigger terms and any explicit 'Use when' guidance, so it answers 'what' but not 'when'.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers, e.g. 'Use when a task changes Room entities, DAOs, database versions, migrations, or schema JSON.'

Soften technical jargon like 'schema artifacts' and 'DAO compatibility' with user-friendlier keywords such as 'Room database migration', 'schema changes', and 'database version bumps'.

Include common phrasings users would actually say (e.g. 'Room migration', 'database schema change') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions such as 'versioning, schema artifacts, data preservation, indices, defaults, DAO compatibility, and migration validation', matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	It clearly answers 'what' the skill does, but there is no explicit 'when' trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	'Room schema and migration changes' is a relevant keyword, but phrasing like 'schema artifacts' and 'DAO compatibility' is technical jargon rather than natural user language, and common variations are absent.	2 / 3
Distinctiveness Conflict Risk	The 'M3UAndroid Room schema and migration' niche is highly specific and unlikely to trigger for unrelated skills, matching the anchor for a clear distinct niche.	3 / 3
	Total	10 / 12 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: e68a71e

Reviewed: about 20 hours 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.