mime-detection-routing

MIME type detection and extractor routing in core/mime.rs — the FORMATS registry that EXT_TO_MIME and SUPPORTED_MIME_TYPES are derived from, the path-based and bytes-based detection functions, priority-based registry selection, wildcard MIME families, and the real procedure for adding a format. Load when adding a format, wiring an extractor to a MIME type, or debugging why a file routes to the wrong (or no) extractor.

Quality

85%

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

82%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 dense, well-structured reference body that gives executable code, exact paths, and a sequenced procedure with a verify step. It could push higher by adding an explicit error-recovery loop to the add-format workflow and splitting deeper reference detail into bundle files.

Suggestions

Add an explicit feedback loop to the 'Adding a New Format' workflow: after `verify`, state what to do if it fails (fix counts/entries and re-run sync+verify) before proceeding to registration.

Pull the detailed registry/format reference (FORMATS entries, count constants, alias rules) into a references/ bundle file and link to it, keeping SKILL.md as the lean overview.

Lead the actionability with one fully copy-paste-ready end-to-end snippet (add FormatEntry → sync → verify → register) so the common case is reproducible verbatim.

Dimension	Reasoning	Score
Conciseness	Lean, technical prose that assumes Claude's competence — tables, real Rust snippets, and numbered steps with no padding or explanations of what MIME types or libraries are; every line carries load.	5 / 5
Actionability	Provides concrete executable guidance — the registry lookup Rust block, exact script invocations (`scripts/sync_supported_counts.py sync` / `verify`), and precise file paths — but a portion of the content is rules/principles rather than copy-paste code, leaving minor gaps.	4 / 5
Workflow Clarity	The "Adding a New Format" sequence is clearly ordered with a verify checkpoint (sync then verify), but it lacks an explicit fix-and-retry feedback loop, so it stops just short of 5; a verification step is present so the destructive/batch cap at 3 does not apply.	4 / 5
Progressive Disclosure	Well-organized into focused sections with clearly signaled one-level references (to `plugin-architecture-patterns` and `scripts/sync_supported_counts.py`); no nested reference chains, though there is no dedicated reference bundle to split deeper detail into.	4 / 5
	Total	17 / 20 Passed

Description

87%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 explicitly covers both what the skill does and when to load it, anchored to a concrete codebase area. Minor room to lead with verb-led actions and include a few more natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists several specific capabilities — "path-based and bytes-based detection functions, priority-based registry selection, wildcard MIME families, and the real procedure for adding a format" — with only minor gaps in coverage; not a 5 because these read more as topics than verb-led actions.	4 / 5
Completeness	Clearly states both what (MIME detection and extractor routing, the FORMATS registry, detection/selection/wildcards/adding a format) and when ("Load when adding a format, wiring an extractor to a MIME type, or debugging why a file routes to the wrong extractor") with concrete triggers.	5 / 5
Trigger Term Quality	Concrete trigger phrases like "adding a format", "wiring an extractor to a MIME type", and "debugging why a file routes to the wrong (or no) extractor" map to natural developer requests; a few synonyms or file-extension terms are missing, so not 5.	4 / 5
Distinctiveness Conflict Risk	A tightly scoped niche (MIME detection & routing in core/mime.rs) with distinct triggers and minimal overlap with other skills; unlikely to fire for the wrong skill.	5 / 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: 2 missing	Warning

	Total	15 / 16 Passed

Repository: xberg-io/xberg
Path: .ai-rulez/skills/mime-detection-routing/SKILL.md
Commit: 04336bd

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