oma-db

Database specialist for SQL, NoSQL, and vector database modeling, schema design, normalization, indexing, transactions, integrity, concurrency control, backup, capacity planning, data standards, anti-pattern review, and compliance-aware database design. Use for database, schema, ERD, table design, document model, vector index design, RAG retrieval architecture, migration, query tuning, glossary, capacity estimation, backup strategy, database anti-pattern remediation work, and ISO 27001, ISO 27002, or ISO 22301-aware database recommendations.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/oma-db/SKILL.md

Quality

Content

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

Well-structured with a clear sequenced workflow and validation checkpoint, but verbose with redundant sections and an ornamental action table, and its progressive-disclosure references point to resource files that are not present in the bundle.

Suggestions

Bundle the referenced resources/*.md files (execution-protocol, checklist, document-templates, anti-patterns, migration-playbook, query-tuning, vector-db, iso-controls) or remove the references so navigation is not broken.

Tighten redundancy: collapse 'Intent signature' into 'When to use', fold guardrails that restate Default Workflow points, and drop the contrived 'SSL primitive' column from the Actions table.

Move the inlined guardrail list and Required Deliverables into the already-referenced document-templates.md / anti-patterns.md so the body stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly directive rather than padded, but verbose: the 'When to use' list overlaps the 'Intent signature', the ornamental Actions table maps actions onto contrived 'SSL primitives', and the 17 guardrails repeat ideas already in the Default Workflow.	3 / 5
Actionability	Concrete design directives and deliverables are present, plus one executable rg block, but the substantive executable detail is deferred to resources/*.md files that are not bundled, leaving the body's own guidance high-level.	3 / 5
Workflow Clarity	A clear sequenced workflow (Entry -> PREPARE/ACQUIRE/REASON/ACT/VERIFY/FINALIZE -> Exit) with a VERIFY checkpoint, a failure-and-recovery section, and a checklist reference for destructive migration work.	4 / 5
Progressive Disclosure	There is a dedicated References section with one-level-deep pointers, but no bundle directory exists so every resources/*.md path is unverified/dangling, and sizable content (the 17 guardrails, deliverables) is inlined that could live in those files.	3 / 5
	Total	13 / 20 Passed

Description

96%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, information-dense description that explicitly states both capabilities and use-conditions with natural trigger terms. Slightly broad at the compliance/capacity edges, which raises minor overlap risk with adjacent skills.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'modeling, schema design, normalization, indexing, transactions, integrity, concurrency control, backup, capacity planning, data standards, anti-pattern review' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' (the long capability sentence) and 'when' ('Use for ... and ISO 27001, ISO 27002, or ISO 22301-aware database recommendations') with concrete trigger phrases.	5 / 5
Trigger Term Quality	The 'Use for' clause covers natural user phrasings and synonyms — 'database, schema, ERD, table design, document model, vector index design, RAG retrieval architecture, migration, query tuning, glossary, capacity estimation, backup strategy' — with strong breadth.	5 / 5
Distinctiveness Conflict Risk	Databases are a clear niche with distinct triggers, but the breadth (capacity planning, backup, ISO compliance) creates minor overlap risk with infra, observability, and security/compliance skills referenced elsewhere in the ecosystem.	4 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: first-fluke/oh-my-agent
Path: .agents/skills/oma-db/SKILL.md
Commit: 7721120

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.