CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-frontend

Implement or modify web UI in React, Next.js, or Angular. Use for components, pages, styles, forms, and frontend state or data flows.

Quality

83%

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

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.

The body is a well-structured, highly actionable agent specification with an explicit sequenced workflow, validation checkpoints, and error-recovery loops, and it organizes detail into clearly signaled one-level-deep resources. Its weaknesses are token efficiency — systematic repetition of the same guardrails across sections and process-meta scaffolding — and inline version/policy detail that duplicates what its own resource files are designated to own.

Suggestions

State each guardrail once and cross-reference it: the components/ui read-only rule appears in Effects ("Does not edit components/ui/* directly"), Guardrail 2, and UI Implementation Customization; the RxJS marble-test mandate appears in Guardrail 9, Tools and instruments, and the Stack Reference row. Deduplicating these would materially tighten the body.

Move version-sensitive detail ("next@16+", "react@19+", "zod (v4)", the @tanstack/react-form v0/v1 adapter caveat) fully into resources/tech-stack.md, which already owns framework versions and mutation policy, keeping only the library-choice table inline.

Trim process-meta sections that describe the agent's own operation rather than instructing the task (the SSL-primitive Actions table, the Resource scope table, and the scene-label scaffolding), which add tokens without adding executable guidance.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and is dense with directive rules, but the same rules repeat systematically — "components/ui/*" read-only appears in Effects, Guardrails, and UI Implementation; the RxJS marble-test mandate appears in Guardrails, Tools, and the Stack Reference table; "proxy.ts" guidance appears three times — and process-meta sections (the SSL-primitive Actions table, Resource scope table) add scaffolding rather than task guidance. This is anchor 3's "mostly efficient but could be tightened", beyond anchor 4's "minor instances" of over-explanation.

3 / 5

Actionability

Guidance is largely executable: named shadcn MCP tools ("shadcn_search_items_in_registries"), concrete file-naming examples ("order-summary-card.tsx", "use-order-polling.ts", "cart.atoms.ts"), explicit decision rules ("Server Actions for form-shaped, revalidate-only flows; TanStack Query for cache-coupled or non-form writes"), and a concrete wrapper example ("components/common/ProductButton.tsx"). It falls short of anchor 5 because verification commands stay generic ("the project's frontend verification commands") and all code examples are deferred to resources/snippets.md rather than covering common cases inline.

4 / 5

Workflow Clarity

The sequence is explicit (Entry → PREPARE/ACQUIRE/ACT/VERIFY/FINALIZE → Exit) with explicit validation ("VERIFY: Run checklist, automated checks, and browser/responsive validation when applicable"; "Run the execution checklist before handoff and include relevant verification results"), feedback loops for error recovery ("If verification fails, fix before handoff or report the blocker"; registry-failure fallback), and a checklist resource (resources/checklist.md). All anchor-5 elements are written out, and no destructive/batch cap applies.

5 / 5

Progressive Disclosure

References are one level deep, each annotated with its purpose (Stack Reference table plus a closing References section), and conditionally gated ("Ordinary UI work does not preload these paths"; "load only for the affected capability"). No bundle files are present to verify, but as declared the structure is good; it falls short of anchor 5 because the ~226-line body inlines detail that resources/tech-stack.md already owns (framework version pins, mutation policy, shadcn engine specifics), a placement gap versus "content appropriately split".

4 / 5

Total

16

/

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 strong: it explicitly states what the skill does and when to use it, with concrete trigger artifacts and framework scoping that make it highly discoverable. Its main limitations are a narrow set of action verbs and a few missing natural synonyms (e.g., CSS, Tailwind, hooks) that would sharpen trigger matching and distinctiveness further.

DimensionReasoningScore

Specificity

"Implement or modify web UI in React, Next.js, or Angular" combined with "components, pages, styles, forms, and frontend state or data flows" names the domain and several concrete work artifacts. It lists more than the 1-2 actions of anchor 3 but the action verbs are limited to "implement or modify", falling short of anchor 5's comprehensive enumeration of distinct concrete actions.

4 / 5

Completeness

The "what" is explicit ("Implement or modify web UI in React, Next.js, or Angular") and the "when" is an explicit trigger clause with concrete trigger objects ("Use for components, pages, styles, forms, and frontend state or data flows"), matching anchor 5's both-answered-with-concrete-triggers profile. Anchor 4's caveat that the 'when' "could be more explicit" does not apply since the trigger list is enumerated.

5 / 5

Trigger Term Quality

"components, pages, styles, forms", "frontend state", and the framework names "React, Next.js, Angular" are phrases users naturally say when needing this skill. Common variations like "CSS", "Tailwind", "shadcn", or "hooks" are absent, so coverage is good but not the comprehensive synonym set of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The frontend-UI niche scoped to React/Next.js/Angular is clearly distinguishable from backend, mobile, or data skills, but broad terms like "forms" and "data flows" carry minor overlap risk with closely related backend or design skills. This matches anchor 4's "mostly distinct; minor overlap risk" rather than anchor 5's minimal-conflict profile.

4 / 5

Total

17

/

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