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

70%

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 ./benchmarks/runs/oma/.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.

The body is well-structured with a clear workflow and validation checkpoint, but it is padded by redundant overlapping frameworks, light on executable guidance beyond search commands, and critically relies on resource files that are not present in the bundle.

Suggestions

Collapse the redundant workflow frameworks (Intent signature / When to use / Structural Flow scenes / Logical Operations / Default Workflow) into a single canonical sequence to cut padding and raise conciseness.

Provide concrete, executable examples for the most common tasks (e.g., a sample migration command, an index-tuning query, or a deliverable template snippet) instead of only declarative guardrail and deliverable lists.

Ship the referenced bundle files (`resources/execution-protocol.md`, `resources/checklist.md`, `resources/document-templates.md`, `resources/anti-patterns.md`, `resources/vector-db.md`, `resources/iso-controls.md`, `resources/examples.md`, `resources/error-playbook.md`, and `../_shared/core/*.md`) or remove the dead references so navigation actually resolves.

Dimension	Reasoning	Score
Conciseness	Mostly efficient directives, but several overlapping frameworks (Intent signature, When to use, Structural Flow scenes, Logical Operations actions, Default Workflow) restate the same workflow, and the 'SSL primitive' action table adds abstract overhead that does not earn its tokens.	3 / 5
Actionability	Provides real executable commands (the `rg` canonical workflow path), yet the bulk of the body is declarative process, guardrail, and deliverable lists rather than concrete executable code or migration/query steps, leaving key execution details implicit.	3 / 5
Workflow Clarity	A clear sequence (Entry → six Scenes → Exit) with an explicit VERIFY validation checkpoint, a Failure-and-recovery section, and a guardrail against risky migrations; minor gaps remain because the referenced checklist is external/absent.	4 / 5
Progressive Disclosure	References are well-signaled with one-level-deep 'Use X when…' guidance, but none of the referenced `resources/.md` or `../_shared/core/.md` files exist in the bundle, making them dead links, and large guardrail/deliverable blocks that could live in separate files are inlined.	3 / 5
	Total	13 / 20 Passed

Description

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

The description is specific, complete, and explicit about both capabilities and trigger conditions, with strong keyword coverage. Its main weakness is mild buzzword redundancy in the long action enumeration rather than any lack of coverage.

Dimension	Reasoning	Score
Specificity	Lists many concrete database actions ('schema design, normalization, indexing, transactions, integrity, concurrency control, backup, capacity planning'), but the long enumeration contains redundant near-synonyms (schema design / ERD / table design / document model), keeping it just below fully comprehensive.	4 / 5
Completeness	Clearly answers both 'what' ('Database specialist for … modeling, schema design, normalization …') and 'when' with an explicit 'Use for database, schema, ERD, table design …' clause containing concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage with synonyms ('database, schema, ERD, table design, document model, vector index, RAG retrieval, migration, query tuning, backup'), though no file-extension triggers are included (largely N/A for this domain).	4 / 5
Distinctiveness Conflict Risk	A clearly distinct database-specialist niche with specific triggers, with only minor overlap risk against compliance/audit skills via the ISO 27001/27002/22301 framing.	4 / 5
	Total	17 / 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: benchmarks/runs/oma/.agents/skills/oma-db/SKILL.md
Commit: 032c988

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