CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-db

Design schemas and migrations, tune queries, or plan vector retrieval and database operations. Application API implementation uses oma-backend.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/oma-db/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-structured, policy-dense instruction skill with a clear sequenced workflow, validation checkpoints, and concrete procedural guidance (expand-contract migrations, ownership review, deliverable templates). Its weaknesses are re-explanation of standard database concepts and a broken reference layer — most resources/*.md files cited in the body are absent from the bundle.

Suggestions

Trim guardrails that restate textbook knowledge (3NF/ACID/BASE definitions, 'measure before tuning', 'vector search is not a drop-in replacement') down to the project-specific policy they enforce, cutting token cost without losing guidance.

Fix the reference layer: the 10 cited resources/*.md files (checklist, anti-patterns, migration-playbook, query-tuning, vector-db, iso-controls, etc.) are missing from the bundle — either add them or correct the paths so navigation works.

Add an explicit validate-fix-revalidate loop for migration and query-tuning steps (e.g. 'if the migration dry-run or checklist fails, fix and re-run before delivering') to close the workflow's remaining feedback-loop gap.

DimensionReasoningScore

Conciseness

The body is dense and directive rather than padded, but several guardrails re-explain textbook database knowledge Claude already has: "enforce at least 3NF", "document ACID expectations explicitly", "document BASE and consistency tradeoffs", "Query tuning starts from measurement and execution plans, never guesswork", and "Never treat vector search as a drop-in replacement for lexical search". There is also redundancy between the Scheduling, Intent signature, When to use, and Expected outputs sections. This fits anchor 3 ('mostly efficient but includes some unnecessary explanation') better than anchor 4, where over-explanation would be only minor.

3 / 5

Actionability

For an instruction-only skill, the guidance is largely concrete: step 2 names specific tools ("find_file, search_for_pattern, get_symbols_overview, and find_symbol"), step 7 points to "resources/anti-patterns.md §5 application ownership review", guardrail 16 specifies a full expand-contract procedure ("additive expand, dual-write + batched backfill, verified read switch, delayed contract"), and the Deliverables section enumerates concrete artifacts. It is not a 5 because actual commands are deferred to unspecified "project's migration, query, lint, or validation commands" with no illustrative examples, leaving minor gaps.

4 / 5

Workflow Clarity

The 10-step canonical workflow is clearly sequenced with validation checkpoints (step 8 runs migration/query-plan/retrieval-quality commands, step 9 applies the anti-pattern review and checklist sections, step 10 notes residual risks and validation steps), plus a dedicated Failure and recovery section. It falls short of anchor 5 because there is no explicit validate-fix-revalidate feedback loop for failed migrations (the referenced resources/error-playbook.md would carry this but is not in the bundle), leaving a minor validation gap.

4 / 5

Progressive Disclosure

The SKILL.md itself is a well-organized overview with a clearly labeled, one-level-deep References section (each entry annotated with its purpose, e.g. "Self-check (check the sections relevant to the task before handoff)"). However, scored against the actual bundle: 10 of the 14 referenced files under resources/ (execution-protocol.md, checklist.md, examples.md, document-templates.md, anti-patterns.md, migration-playbook.md, query-tuning.md, vector-db.md, iso-controls.md, error-playbook.md) do not exist in the bundle, so most reference navigation fails in practice. This is more than the 'minor organization gaps' of anchor 4, but the in-body structure and clearly signaled references keep it above anchor 2.

3 / 5

Total

14

/

20

Passed

Description

66%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 concise, third-person description with concrete, natural trigger terms covering the core database-design domain. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness and leaves activation guidance implicit.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about schema design, ERDs, migrations, query tuning, vector/RAG retrieval, capacity, or database anti-patterns."

Include a few missing natural synonyms users would say (SQL, NoSQL, ERD, indexing, RAG) and a brief nod to the governance/backup/capacity scope the body covers.

DimensionReasoningScore

Specificity

"Design schemas and migrations, tune queries, or plan vector retrieval and database operations" lists several concrete actions (design schemas, design migrations, tune queries, plan vector retrieval, plan database operations). It falls short of anchor 5 because significant capabilities from the body (capacity estimation, backup/recovery, data governance/glossary, anti-pattern review, ISO compliance) are omitted, but it clearly exceeds anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

The 'what' is clear ("Design schemas and migrations, tune queries, or plan vector retrieval and database operations"), but there is no 'Use when...' clause or equivalent trigger guidance; the second sentence ("Application API implementation uses oma-backend") routes away from a sibling skill rather than stating when to use this one. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3; it is not a 2 because the 'what' is concrete and a weak boundary signal exists.

3 / 5

Trigger Term Quality

Natural trigger terms are present: "schemas", "migrations", "tune queries", "vector retrieval", "database operations" — phrases users would naturally say. Missing common variations like "SQL", "NoSQL", "ERD", "indexing", "RAG", and "backup", so it does not reach anchor 5's comprehensive synonym coverage, but coverage is good rather than partial.

4 / 5

Distinctiveness Conflict Risk

The domain is a clear niche (schema design, migrations, query tuning, vector retrieval) with mostly distinct triggers, and the routing note "Application API implementation uses oma-backend" explicitly disambiguates from a backend skill. Minor overlap risk remains with infra or QA skills (the body itself lists TF Infra and QA agents), keeping it below anchor 5.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 4 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

first-fluke/oh-my-agent

Path

skills/oma-db/SKILL.md

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.