CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

db-identify

Identify database file formats by scanning magic bytes and file signatures. Use FIRST when encountering any unknown database file. Returns format type, version, confidence level, and DBeaver CLI compatibility. Pure identification only - for routing decisions, pass results to db-router.

Quality

82%

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

The canonical home for this skill is db-identify in KennethJefferson/cc_sdk_knowledge_extractor

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 tight, well-structured skill body: executable quick-start commands, exact human and JSON output examples, and accurate format/compatibility tables, all appropriately externalized to a real bundled script. The few gaps are minor — an inconsistent script path in Typical Workflow and a missing derby row in the formats table.

Suggestions

Fix the Typical Workflow command to use the 'scripts/' path prefix ('python scripts/db_identify.py mystery.db --json') so it is copy-paste executable, consistent with Quick Start.

Add derby to the Supported Formats table since the bundled script detects it and reports it as DBeaver-supported.

Consider merging the CLI Reference into Quick Start (or trimming it to only options not already shown) to remove the small redundancy.

DimensionReasoningScore

Conciseness

Mostly lean: compact tables, exact output examples, and no explanations of concepts Claude already knows. Minor trimmable duplication remains — the CLI Reference re-lists the -j/--json and -l/--list-formats flags already demonstrated in Quick Start, and Typical Workflow re-covers the identify step.

4 / 5

Actionability

Quick Start commands are executable and both output formats are documented exactly, but two minor gaps remain: the Typical Workflow example runs 'python db_identify.py mystery.db' without the 'scripts/' path prefix used in Quick Start (the command would fail as written), and the Supported Formats table omits derby, which the bundled script detects and reports as DBeaver-supported.

4 / 5

Workflow Clarity

A simple single-task, read-only skill: the action is unambiguous (one command, documented output), results include a confidence level as a built-in checkpoint, and the next step is explicitly delegated to db-router. No destructive or batch operations, so no validation cap applies; fits the simple-skill exception for an unambiguous single action.

5 / 5

Progressive Disclosure

Well-organized single-file overview with implementation properly externalized to scripts/db_identify.py (verified to exist and match the documented CLI). No content is inlined that belongs in a separate file, sections are clean, and there are no nested references.

5 / 5

Total

18

/

20

Passed

Description

71%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 strong description with concrete capabilities, an explicit when-to-use clause, and excellent boundary discipline that cleanly separates it from the companion db-router skill. The main weakness is trigger-term coverage: it lacks the file extensions and format-name synonyms users would naturally mention.

Suggestions

Add natural trigger phrases with file extensions and format names, e.g. 'Use when encountering unknown .db, .mdb, .accdb, .sqlite files or when the user asks what database format a file is'.

Include one or two format-name synonyms (sqlite, Access, dBase) so the description matches how users actually refer to these files.

Optionally mention the JSON output explicitly as the handoff format for db-router to reinforce the routing workflow.

DimensionReasoningScore

Specificity

Lists several concrete actions ('scanning magic bytes and file signatures', 'Returns format type, version, confidence level, and DBeaver CLI compatibility') with an explicit scope boundary, but centers on one core action rather than the multiple distinct actions of the top anchor.

4 / 5

Completeness

Both 'what' (identify formats via signature scanning with specific outputs) and 'when' ('Use FIRST when encountering any unknown database file') are explicitly stated. Not 5 because the when-clause covers a single trigger condition without the concrete trigger phrase variations the top anchor expects; not 3 because the when is explicit, not weakly implied.

4 / 5

Trigger Term Quality

'database file formats' and 'unknown database file' are natural terms, but the description omits common variations users would say, such as file extensions (.db, .mdb, .accdb) and format names (sqlite, access). Not 4 because anchor-level keyword coverage including synonyms and extensions is absent.

3 / 5

Distinctiveness Conflict Risk

'Pure identification only - for routing decisions, pass results to db-router' draws an explicit boundary against the closely related router skill, and the niche (database file identification) has distinct triggers with minimal overlap risk.

5 / 5

Total

16

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

KennethJefferson/cc_skill_monorepo_db_tools

Path

db-identify/SKILL.md

Revision

edc9701

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill