CtrlK
BlogDocsLog inGet started
Tessl Logo

mime-detection-routing

MIME type detection and extractor routing in core/mime.rs and core/extractor/bytes.rs — the extension→EXT_TO_MIME→validate→registry→extractor flow, key detection functions, the 118+ case-insensitive extension map, priority-based registry selection, wildcard MIME families, and how to add a new MIME type. Load when adding a format, wiring an extractor to a MIME type, or debugging why a file routes to the wrong (or no) extractor.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A lean, well-organized codebase reference with clear sequencing and validation guidance. Its main gap is actionability: the 'add a new MIME type' workflow omits the concrete registration call and a DocumentExtractor trait example, leaving two steps as directives rather than copy-paste-ready code.

Suggestions

Show the concrete registration call in 'Adding New MIME Types' (e.g. the exact registry.register(...) line used inside register_default_extractors()) so step 3 is executable rather than a pointer.

Add a minimal DocumentExtractor trait impl skeleton (with supported_mime_types() returning the new MIME) so step 2 is concrete instead of a directive.

Add a verification checkpoint to the add-MIME workflow (e.g. 'validate_mime_type("application/x-new") returns true, then select_extractor_for_mime routes correctly') to confirm the new type is wired end-to-end.

DimensionReasoningScore

Conciseness

The body is lean — tables, terse rules, and code blocks — with no padding explaining what MIME types or registries are; every line is codebase-specific, matching the score-3 'every token earns its place' anchor.

3 / 3

Actionability

Provides exact function names, file locations, and a real insert snippet, but the 'Register in register_default_extractors()' step shows no registration call and 'Implement DocumentExtractor…' is a directive without a trait example — missing key details that fit the score-2 rather than the copy-paste-ready score-3 anchor.

2 / 3

Workflow Clarity

The detection flow is a clearly sequenced pipeline (Extension -> EXT_TO_MIME -> validate -> Registry -> Extractor) and Critical Rules #1 mandates validate_mime_type() before extraction; as a self-contained reference skill with clear sequencing and an explicit validation rule it meets the score-3 simple-skills bar.

3 / 3

Progressive Disclosure

A roughly 50-line self-contained reference with no external files needed, organized into clear headed sections (Detection Flow, Key Functions, Registry Selection, etc.), matching the score-3 guideline for short skills needing no external references.

3 / 3

Total

11

/

12

Passed

Description

100%

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 strong, specific description that pairs a concrete capability list with an explicit 'Load when…' trigger clause and a narrowly scoped niche. It is well-distinguished and clearly answers both what the skill does and when to load it.

DimensionReasoningScore

Specificity

Enumerates multiple concrete capabilities ('MIME type detection and extractor routing', 'how to add a new MIME type', 'priority-based registry selection', 'wildcard MIME families'), matching the score-3 anchor for listing several specific actions rather than just naming a domain.

3 / 3

Completeness

Clearly states what the skill covers (detection/routing capabilities) and provides an explicit 'Load when…' trigger clause, satisfying the score-3 anchor requiring both 'what' and 'when' with explicit triggers.

3 / 3

Trigger Term Quality

The 'Load when adding a format, wiring an extractor to a MIME type, or debugging why a file routes to the wrong (or no) extractor' clause supplies three natural developer utterances with good coverage, matching the score-3 anchor; the first sentence's internal jargon (EXT_TO_MIME, registry selection) is offset by these natural triggers.

3 / 3

Distinctiveness Conflict Risk

Scoped to specific files (core/mime.rs, core/extractor/bytes.rs) and a narrow internal routing flow, giving it a clear niche unlikely to conflict with other skills per the score-3 anchor.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
xberg-io/xberg
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.