CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-dev-workflow

Configure development tasks, git hooks, CI/CD, or release automation. Use when creating or fixing a repository development workflow.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/oma-dev-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-engineered operational skill: the canonical command path is a genuinely sequential workflow with explicit validation, error-recovery loops, and 19 concrete guardrails. Its main weaknesses are a dangling reference layer (the resources/ files it depends on are absent from the bundle, so the progressive-disclosure structure cannot actually be used) and some trimmable scaffolding, notably the keyword dump and the Scheduling section that re-states the description.

Suggestions

Ship the referenced bundle files (resources/mise-basics.md, tooling-profiles.md, validation-pipeline.md, example-task-wiring.md, release-coordination.md, troubleshooting.md) or remove/replace the links — every reference in the table currently points to a nonexistent path, which blocks the skill's progressive-disclosure design.

Delete the "Knowledge Reference" keyword list at the end; it is padding that Claude can infer and wastes context tokens.

Trim the "Scheduling" section (intent signature, expected inputs/outputs, dependencies), which largely duplicates the frontmatter description and the When to use/NOT to use lists, to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence with no basic-concept explanations, but the ~40-line "Scheduling" scaffolding (intent signature, when to use/not use, expected inputs/outputs) duplicates the description's trigger information, and the trailing "Knowledge Reference" keyword dump ("mise, task runner, monorepo, dev server, lint, format...") adds no actionable value — minor waste that could be trimmed, not the lean top anchor.

4 / 5

Actionability

Concrete, executable commands appear throughout ("mise tasks --all", "mise install", "mise run //{path}:{task}", quoting rules like "[tasks.\"lint:changed\"]", "monorepo_root = true"), and failure paths give specific recovery commands, but no complete config examples are inlined (they are delegated to reference files), leaving minor gaps.

4 / 5

Workflow Clarity

The "Canonical command path" provides a clearly sequenced 6-step procedure with explicit validation checkpoints ("A skipped run is not a pass", "Check exit codes, logs, generated artifacts, and CI compatibility"), a dedicated "Failure and recovery" section with feedback loops for each failure mode (missing task, missing runtime, hung task, skipped hook), and explicit exit criteria — matching the top anchor's validate-fix-retry pattern.

5 / 5

Progressive Disclosure

The References table is well-signaled with a "Load when" column and stays one level deep, but the referenced files (resources/mise-basics.md, resources/tooling-profiles.md, resources/validation-pipeline.md, etc.) do not exist in the bundle — no references/, scripts/, or assets/ directories are present — so every reference link is a dangling path a reader cannot actually load.

3 / 5

Total

16

/

20

Passed

Description

75%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 solid third-person description that clearly pairs a multi-action 'what' with an explicit 'Use when' clause and names a distinct dev-workflow niche. It falls short of top marks only on breadth: it omits several capabilities the skill body actually covers (lint/format/typecheck, migrations, dev servers) and lacks richer natural trigger synonyms.

Suggestions

Add the concrete check names users actually request — e.g. "run lint, format, typecheck, or test tasks", "pre-commit hooks", "database migrations" — to both broaden the 'what' and capture more natural trigger phrases.

Make the 'when' clause more concrete by enumerating trigger situations (e.g. "Use when setting up pre-commit validation, wiring CI pipelines, or troubleshooting mise task failures") instead of the abstract "repository development workflow".

DimensionReasoningScore

Specificity

The description lists several concrete action areas ("Configure development tasks, git hooks, CI/CD, or release automation") but omits capabilities the body covers such as lint/format/typecheck, migrations, and dev servers, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

Both what ("Configure development tasks, git hooks, CI/CD, or release automation") and when ("Use when creating or fixing a repository development workflow") are explicit, but the when-clause is a single abstract phrase rather than concrete trigger phrases, keeping it below the top anchor.

4 / 5

Trigger Term Quality

Natural terms users would say are present ("git hooks", "CI/CD", "release automation"), but common variations like "lint", "pre-commit", "pipeline", or "mise" are missing, so a few natural terms are absent.

4 / 5

Distinctiveness Conflict Risk

The dev-workflow automation niche is mostly distinct with specific triggers (git hooks, CI/CD, release automation), though the broad phrase "development tasks" carries minor overlap risk with general coding-assistant skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 possibly missing (resources/example-task-wiring.md, resources/mise-basics.md, resources/release-coordination.md, resources/tooling-profiles.md, resources/troubleshooting.md, +1 more)

Warning

Total

15

/

16

Passed

Repository

first-fluke/oh-my-agent

Path

.agents/skills/oma-dev-workflow/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.