CtrlK
BlogDocsLog inGet started
Tessl Logo

oma-frontend

Frontend specialist for React, Next.js, TypeScript with FSD-lite architecture, shadcn/ui, and design system alignment. Use for UI, component, page, layout, CSS, Tailwind, and shadcn work.

66

Quality

80%

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

Quality

Content

81%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, actionable content with a clear validated workflow and good progressive disclosure via a References section. Weakest point is progressive disclosure: many referenced resource files live outside the bundle, so navigation depends on paths not shipped here.

Suggestions

Trim the Scheduling section (Intent signature / Expected inputs / Expected outputs) which restates the description and adds token overhead without new guidance.

Inline one or two short representative code snippets (e.g., a wrapper component pattern or useResponsive usage) so core actions are executable without leaving the skill.

Verify the referenced resources/*.md and ../_shared/core/*.md paths resolve within the bundle, or mark which are environment-injected vs. skill-shipped, so navigation is reliable.

DimensionReasoningScore

Conciseness

Largely lean and well-organized with tables and terse bullets, assuming Claude's competence (no basic React/Tailwind explanations); minor padding in the Scheduling section restating intent/inputs/outputs that overlaps the description.

4 / 5

Actionability

Provides concrete executable commands (rg queries), named shadcn registry tools, and a specific library table; mostly executable with minor gaps where inline code examples are deferred to external resources/ files.

4 / 5

Workflow Clarity

Clear PREPARE/ACQUIRE/ACT/VERIFY/FINALIZE sequence with an explicit VERIFY checkpoint, a Failure-and-recovery section, and a referenced checklist, giving explicit validation and feedback loops.

5 / 5

Progressive Disclosure

Good structure with a clear References section listing one-level-deep resources; however the referenced resources/ and ../_shared/ paths are not present in the skill bundle directory, slightly weakening navigability.

4 / 5

Total

17

/

20

Passed

Description

78%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, specific description that clearly states both the skill's purpose and its use triggers with natural terminology. Main weakness is that capabilities are framed as domains rather than concrete actions.

DimensionReasoningScore

Specificity

Names the domain and concrete stack (React, Next.js, TypeScript, FSD-lite, shadcn/ui) but the 'actions' are domain areas ('UI, component, page, layout, CSS') rather than concrete verbs; comprehensive stack coverage but not comprehensive action coverage.

3 / 5

Completeness

Explicitly answers both what ('Frontend specialist for React, Next.js, TypeScript with FSD-lite architecture, shadcn/ui, and design system alignment') and when ('Use for UI, component, page, layout, CSS, Tailwind, and shadcn work') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('UI, component, page, layout, CSS, Tailwind, and shadcn work') that users would say, with only minor synonyms missing (e.g., 'frontend', 'forms', 'styling').

4 / 5

Distinctiveness Conflict Risk

Clear frontend niche distinct from backend/mobile, with minor overlap risk against general web/UI skills; mostly distinct triggers.

4 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
first-fluke/oh-my-agent
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.