oma-dev-workflow

Use when setting up or optimizing developer workflows in a monorepo, managing mise tasks, git hooks, CI/CD pipelines, database migrations, or release automation. Invoke for development environment setup, build automation, testing workflows, and release coordination.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%

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

The body is highly actionable with concrete commands and a clearly sequenced, validated workflow, but it is verbose from redundant workflow reframings and keeps too much detail inline while pointing to resource files that are not actually bundled.

Suggestions

Collapse the redundant workflow framings (Scheduling, Structural Flow, Logical Operations, How to Execute) into a single canonical sequence to cut ~40% of the body and raise conciseness.

Move the Environment Variables, Output Templates, and Troubleshooting blocks into the referenced resource files so the overview stays lean and progressive disclosure is genuine.

Either bundle the referenced files (resources/*.md, ../_shared/core/*.md) or remove the references, since pointing to non-existent files breaks navigation.

Dimension	Reasoning	Score
Conciseness	Operational content is mostly useful, but the same workflow is reframed four times (Scheduling, Structural Flow, Logical Operations, How to Execute) and generic boilerplate such as the 'Knowledge Reference' keyword dump and env-var examples pad the body — not a 1 since it avoids explaining known concepts, but not lean enough for a 3.	2 / 3
Actionability	Provides copy-paste-ready commands (`mise run //apps/api:dev`, `mise tasks --all`), executable TOML task-dependency examples, and a troubleshooting table with specific fixes like `lsof -ti:PORT`, matching the fully-executable score-3 anchor.	3 / 3
Workflow Clarity	Clear PREPARE→ACQUIRE→ACT→VERIFY→FINALIZE sequence with an explicit VERIFY checkpoint, a failure/recovery section, and guardrail #23 requiring confirmation for destructive (clean, reset) tasks — feedback loops are present for the batch/destructive operations the skill handles.	3 / 3
Progressive Disclosure	A well-signaled Reference Guide table with 'When to Load' columns is good, but the referenced files (resources/.md, ../_shared/core/.md) do not exist and substantial content that could live in those files (env vars, output templates, troubleshooting, project structure) remains inline, fitting the score-2 anchor better than score-3.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 with explicit trigger guidance, concrete enumerated actions, and a clear niche that minimizes conflict risk. It cleanly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'managing mise tasks, git hooks, CI/CD pipelines, database migrations, or release automation' — rather than vague language, matching the score-3 anchor.	3 / 3
Completeness	Explicitly answers both what (the enumerated actions) and when via the 'Use when…' and 'Invoke for…' trigger clauses, satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	Covers natural terms a developer would actually say — 'git hooks', 'CI/CD pipelines', 'database migrations', 'release automation', 'build automation', 'testing workflows' — with good breadth of variations.	3 / 3
Distinctiveness Conflict Risk	Carves a clear niche (mise-based monorepo dev-workflow automation) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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-dev-workflow/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.