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

76%

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 ./.agents/skills/oma-db/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 dense, well-structured policy document: the workflow is clearly sequenced with explicit validation and destructive-operation safeguards, and references are annotated and one level deep. Its main weaknesses are redundancy across the scheduling/dependencies/guardrails sections and run-on workflow steps that could be tightened, plus an unverifiable reference set.

Suggestions

Merge "Intent signature" into "When to use" and fold the resource list in "Dependencies" into the References section to eliminate duplication.

Break the run-on workflow steps (1, 5, 6) into short imperative steps, keeping each step to a single action plus its precondition.

Consolidate overlapping guardrails (e.g. 3/4 on consistency tradeoffs, 12–15 on vector systems) or move their detail into the referenced migration/vector playbooks, keeping only the rule statement inline.

DimensionReasoningScore

Conciseness

The body mostly prescribes rather than explains known concepts (it enforces 3NF/ACID/BASE without tutorializing them), but it is noticeably redundant: "Intent signature" duplicates "When to use", "Dependencies" duplicates the References list, workflow step 7 restates guardrail 18, and steps 1, 5, and 6 are run-on sentences that could be tightened. This fits 'mostly efficient but could be tightened' better than the noticeably-padded level 2.

3 / 5

Actionability

Guidance is largely executable for an instruction-only skill: named tools (Serena's find_file, search_for_pattern, get_symbols_overview, find_symbol), spelled-out procedures (expand-contract with dual-write and batched backfill; measure, explain, nominate, re-measure), and section-level pointers (anti-patterns.md §5). Minor gaps remain: no inline worked example or concrete command — those are deferred to referenced files — and several steps like "run the project's migration... commands" stay high-level.

4 / 5

Workflow Clarity

The 10-step canonical workflow is clearly sequenced with explicit validation: migration commands run only after identifying the engine and tool, the checklist must be reviewed before handoff, deliverables require SQL/plan evidence and a verification outcome, guardrail 17 defines a measure-re-measure feedback loop, and the Failure-and-recovery section plus resources/error-playbook.md cover error recovery. Because this is a database skill with destructive migration risk, the presence of "verified read switch", soak windows, separate deploys for destructive steps, and "do not execute a risky migration without explicit user intent and verification" satisfies the validation requirement, so no cap applies.

5 / 5

Progressive Disclosure

The References section is a model of one-level-deep, well-signaled pointers — each of the ~13 files carries a scope note (e.g. "Examples: ... (worked outputs for full design, RAG retrieval, live-table remediation...)") — and detailed material (templates, playbooks, examples) is externalized. It falls short of 5 because no bundle files are present to verify the referenced resources/*.md and ../_shared paths actually exist, the "Dependencies" section duplicates the reference list, and 18 dense guardrails inline could partly live in the referenced playbooks.

4 / 5

Total

16

/

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 specific, readable capability statement with a useful sibling-skill boundary, but it lacks an explicit positive trigger clause ("Use when...") and natural synonyms like SQL, ERD, index, and RAG, which limits both completeness and trigger-term quality. It is clearly distinct from neighboring application-implementation skills.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions schema design, ERD, table design, migrations, query tuning, indexing, or vector/RAG retrieval."

Include natural synonyms users actually say — SQL, NoSQL, ERD, index, RAG, semantic search — alongside the existing terms.

Briefly extend the boundary note to cover the infra-provisioning and QA-audit cases already listed in the body's "When NOT to use" section.

DimensionReasoningScore

Specificity

The description lists three concrete actions ("Design schemas and migrations", "tune queries", "plan vector retrieval and database operations") rather than vague language, but omits capabilities the skill itself claims such as capacity estimation, backup strategy, and data governance, so coverage has minor gaps.

4 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when..." clause; the trailing boundary sentence "Application API implementation uses oma-backend" only says when not to use it and merely implies the positive trigger. Per the guideline, a missing explicit trigger clause caps completeness at 3, and the anchor 'clear what but when only weakly implied' is the best fit.

3 / 5

Trigger Term Quality

Natural terms users would say are present (schema, migrations, tune queries, database, vector retrieval), but common synonyms and variations like SQL, NoSQL, ERD, table design, index, and RAG are missing. Not 5 because coverage is good rather than comprehensive; not 3 because it goes well beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

The database design/tuning niche is distinct and the oma-backend boundary explicitly disambiguates from the closest sibling skill, but boundaries with other likely overlapping skills (infra provisioning, QA audit) named in the body are not addressed in the description, leaving minor overlap risk.

4 / 5

Total

15

/

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

first-fluke/oh-my-agent

Path

.agents/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.