oma-backend

Backend specialist for APIs, databases, authentication with clean architecture (Repository/Service/Router pattern). Use for API, endpoint, REST, database, server, migration, and auth work.

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-backend/SKILL.md

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured backend skill with a clear sequenced workflow and validation feedback loop, but it is verbose in places and lacks executable code examples. Several referenced bundle files are absent, weakening progressive disclosure.

Suggestions

Trim framework overhead (the 'Scheduling', 'Logical Operations', 'SSL primitive', and 'Resource scope' tables) and remove restatements of architecture concepts Claude already knows to recover tokens.

Add at least one copy-paste executable example showing a router -> service -> repository slice in a common stack, so the core pattern is actionable rather than only described.

Create the referenced bundle files (resources/execution-protocol.md, checklist.md, orm-reference.md, examples.md, stack/stack.yaml) or remove the dangling references so progressive disclosure points at real content.

Dimension	Reasoning	Score
Conciseness	The body is mostly purposeful but carries framework boilerplate ('Scheduling', 'Logical Operations', 'SSL primitive' columns, 'Resource scope' tables) and re-explains architecture layers Claude already knows, so it could be tightened.	2 / 3
Actionability	It gives concrete rules (parameterized queries, JWT+bcrypt, env config) and ripgrep commands, but lacks executable, copy-paste code examples for the router/service/repository implementation it centers on.	2 / 3
Workflow Clarity	A clear PREPARE/ACQUIRE/ACT/VERIFY/FINALIZE sequence with an explicit VERIFY checkpoint and a feedback loop ('If verification fails, fix root cause before handoff') plus defined exit criteria.	3 / 3
Progressive Disclosure	References are clearly signaled and one-level-deep in the References section, but the referenced bundle files (resources/.md, ../_shared/core/.md, stack/*) do not exist on disk, and heavy inline content (Core Rules, Guardrails) could be partly externalized.	2 / 3
	Total	9 / 12 Passed

Description

90%

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, third-person description that clearly states its purpose and gives explicit, natural trigger terms. Its only weakness is naming domains rather than enumerating concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('APIs, databases, authentication') and the clean-architecture pattern, but lists domains rather than multiple concrete actions (e.g. 'build REST APIs, design schemas, implement auth flows'), so it stops at 'names domain and some actions'.	2 / 3
Completeness	It states what the skill does ('Backend specialist for APIs, databases, authentication...') and provides an explicit 'Use for...' trigger clause, answering both what and when.	3 / 3
Trigger Term Quality	The 'Use for API, endpoint, REST, database, server, migration, and auth work' clause gives good coverage of natural terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Backend/server-side triggers (REST, endpoint, server, migration) carve a clear niche distinct from frontend/mobile/db skills, with low risk of triggering the wrong skill.	3 / 3
	Total	11 / 12 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-backend/SKILL.md
Commit: 3021301

Reviewed: about 21 hours 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.