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

80%

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

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/runs/oma/.agents/skills/oma-dev-workflow/SKILL.md

Quality

Content

71%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.

Highly actionable with executable mise commands and a well-sequenced workflow including validation and recovery, but it is padded and monolithic — guardrails are redundant, troubleshooting is duplicated, and the signaled resource references point to files that do not exist in the bundle.

Suggestions

Collapse the 24-item guardrail list into a concise set of distinct rules, removing positive/negative duplicates (e.g., rule 1 'Always use mise run' vs rule 15 'Never use direct package manager commands') to cut tokens.

Merge the 'Failure and recovery' section with the 'Troubleshooting Guide' table so each failure mode appears once with its diagnostic command and fix.

Move the bulk reference material (validation pipeline, database patterns, release coordination) into real, one-level-deep files under references/ and confirm the paths in the Reference Guide table resolve, instead of inlining and pointing at missing `resources/` paths.

Dimension	Reasoning	Score
Conciseness	Mostly concrete commands and tables, but padded in places: a 24-item guardrail list with redundant positive/negative duplicates, troubleshooting duplicated across 'Failure and recovery' and 'Troubleshooting Guide', and a terminal 'Knowledge Reference' keyword dump that adds little.	3 / 5
Actionability	Copy-paste-ready commands throughout (`mise tasks --all`, `mise run //apps/api:dev`, `lsof -ti:PORT`), executable toml task definitions, env-var patterns, and a task-type table covering the common cases.	5 / 5
Workflow Clarity	Clear sequence (Entry → PREPARE/ACQUIRE/ACT/VERIFY/FINALIZE → Exit) with an explicit VERIFY checkpoint and a 'Failure and recovery' feedback loop; validation is present for the batch/destructive operations, so no cap applies, though some checkpoints remain implicit.	4 / 5
Progressive Disclosure	Has a Reference Guide table and clear section headers, but no bundle files exist and the referenced `resources/.md` and `../_shared/.md` paths do not resolve; substantial content (24 guardrails, troubleshooting, env patterns) is inlined that would fit better in separate files.	3 / 5
	Total	15 / 20 Passed

Description

88%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, concrete description that explicitly pairs capabilities with 'Use when'/'Invoke for' trigger guidance and lists many specific actions in the monorepo/mise niche. Minor gains possible by adding concrete artifact cues (e.g., 'mise.toml', '.env') to lift trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'setting up or optimizing developer workflows', 'managing mise tasks, git hooks, CI/CD pipelines, database migrations, or release automation' — with comprehensive domain coverage rather than generic phrasing.	5 / 5
Completeness	Explicitly answers both what (managing mise tasks, hooks, CI/CD, migrations, releases) and when via two trigger clauses ('Use when setting up or optimizing…', 'Invoke for development environment setup, build automation…') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keywords ('mise tasks', 'git hooks', 'CI/CD pipelines', 'database migrations', 'build automation', 'testing workflows') with synonyms like 'release automation'/'release coordination', but lacks the equivalent of file-extension cues (e.g., 'mise.toml') that would push it to comprehensive.	4 / 5
Distinctiveness Conflict Risk	The mise/monorepo niche is fairly distinct and unlikely to fire for unrelated skills, but the broad CI/CD and 'build automation' framing could overlap marginally with general devops or release-tooling skills.	4 / 5
	Total	18 / 20 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: benchmarks/runs/oma/.agents/skills/oma-dev-workflow/SKILL.md
Commit: 032c988

Reviewed: 2 days 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.