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

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/oma-dev-workflow/SKILL.md
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 an impressively lean, highly actionable operations manual with an excellent sequenced workflow, explicit validation checkpoints, and thorough failure-recovery guidance. Its one serious defect is that three-quarters of its referenced resource files are absent from the bundle, breaking the progressive-disclosure structure it depends on.

Suggestions

Create the six missing `resources/*.md` files (mise-basics, tooling-profiles, validation-pipeline, example-task-wiring, release-coordination, troubleshooting) or fix the reference paths to wherever they actually live, since steps 2, 4, and 5 of the canonical path depend on loading them.

Delete the trailing "Knowledge Reference" keyword list — it duplicates trigger terms already present in the description and Intent signature and adds tokens without operational value.

Inline one small executable example (e.g., a minimal mise.toml task with a quoted colon name and `monorepo_root = true`) so the most common wiring case is copy-paste ready without needing the missing profile files.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and free of explanations of concepts Claude already knows (no primer on what mise or CI/CD is), with nearly every line carrying operational guidance. Minor trimmable material keeps it below 5: the trailing "Knowledge Reference" keyword list duplicates trigger terms already in the description and intent signature, and the Intent signature / When to use sections restate each other.

4 / 5

Actionability

Concrete, executable specifics abound: `mise install`, `mise tasks --all`, `mise run check`, `mise run //{path}:{task}`, `[tasks."lint:changed"]` quoting, `monorepo_root = true`, hook names (`git:pre-commit`, `git:pre-push`, `validate:changed`), and named tools (Ruff, Biome, Hadolint, commitlint). It falls short of 5 because no complete copy-paste config snippet (e.g., a sample mise.toml task) is shown inline, and the referenced profiles that would contain them are missing from the bundle.

4 / 5

Workflow Clarity

The "Canonical command path" gives a clearly sequenced 6-step procedure, step 5 is an explicit validation checkpoint ("A skipped run is not a pass", check exit codes/logs/artifacts), the "Failure and recovery" section provides feedback loops for each error class (missing task -> `mise tasks --all`, missing runtime -> `mise install`, hangs, skipped checks), destructive tasks require confirmation, and Exit criteria define success/partial success. This matches the anchor requiring explicit validation steps plus error-recovery loops.

5 / 5

Progressive Disclosure

The References table is well designed (one level deep, with "Load when" conditions), but scoring against the actual bundle shows 6 of the 8 referenced paths (`resources/mise-basics.md`, `tooling-profiles.md`, `validation-pipeline.md`, `example-task-wiring.md`, `release-coordination.md`, `troubleshooting.md`) do not exist — only the two `references/_shared/core/...` links resolve. Since the canonical path repeatedly instructs the reader to load these missing files, navigation to the core detail content is effectively broken, which is worse than the merely unclear signaling of anchor 3.

2 / 5

Total

15

/

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 well-formed, third-person description that explicitly covers both what the skill does and when to use it, with strong natural trigger terms. The main improvement opportunities are richer trigger phrasing and more varied action verbs.

DimensionReasoningScore

Specificity

"Configure development tasks, git hooks, CI/CD, or release automation" names the domain plus four concrete capability areas (tasks, hooks, CI/CD, release automation), matching the 'several specific actions with minor gaps' anchor. It falls short of 5 because a single verb ('Configure') covers all actions, unlike the comprehensive multi-verb 5 anchor, and it is above 3 since it goes beyond naming just the domain with 1-2 actions.

4 / 5

Completeness

Both parts are explicit: what = "Configure development tasks, git hooks, CI/CD, or release automation", and when = "Use when creating or fixing a repository development workflow". The 'when' clause is a single condition and could be more specific with additional trigger phrases (e.g., setting up lint/pre-commit or fixing a failing pipeline), matching anchor 4 rather than the concrete multi-trigger phrasing of anchor 5.

4 / 5

Trigger Term Quality

Natural phrases users would say are present: "git hooks", "CI/CD", "release automation", "development workflow". A few common variations are missing (e.g., lint, pre-commit, pipeline, migrations, mise), which fits the 'good keyword coverage, a few natural terms missing' anchor rather than the comprehensive-synonym coverage of 5 or the partial coverage of 3.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (repo development-workflow automation) with distinct triggers like git hooks and release automation; risk of mis-triggering is minor. It is not a 5 because broad terms such as "CI/CD" and "development tasks" retain some overlap with generic devops or build skills.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 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

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

first-fluke/oh-my-agent

Path

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.