oma-scm

SCM (software configuration management) and Git — branching, merges, conflicts, worktrees, baselines, audit readiness, plus Conventional Commits and safe staging.

Quality

67%

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-scm/SKILL.md

Quality

Content

63%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 highly actionable with well-sequenced workflows and guardrails, but it carries duplicated command blocks and relies on references to files that are not present in the bundle, leaving progressive disclosure and conciseness mid-range.

Suggestions

De-duplicate the `git status -sb` / `git diff --staged` / `git log --oneline -5` and heredoc-commit blocks that recur in 'Canonical command path' and the Conventional Commits steps; keep one canonical copy and link to it.

Move the detailed CM workflows, CODEOWNERS maintenance checklist, and onboarding risk scan into the referenced `resources/*.md` files and link out, so SKILL.md stays an overview.

Either create the cited `config/commit-config.yaml`, `config/cm-config.yaml`, `resources/conventional-commits.md`, `resources/onboarding-risk-signals.md`, `resources/codeowners-playbook.md`, and `../../workflows/scm.md` files, or remove the references, since none exist in the current bundle.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and does not over-explain basics, but the `git status/diff/log` block and the heredoc commit block are each duplicated across "Canonical command path" and the Conventional Commits steps, which could be tightened by referencing one location.	3 / 5
Actionability	Concrete, executable commands throughout (`git add <specific-files>`, heredoc and `-F` commit variants, `git worktree add`, `merge-base`) with a clear commit format; only minor gaps from template placeholders like `<type>(<scope>)` and `<specific-files>`.	4 / 5
Workflow Clarity	Clear sequences (PREPARE→VERIFY scenes, Quick vs Full CM Path, CM workflows 1–6, commit steps 1–5) with verification checkpoints and approval gates for destructive/history-rewrite operations; just short of a 5 because explicit validate→fix→retry feedback loops are limited.	4 / 5
Progressive Disclosure	Good section structure, but no bundle files exist while the body cites `config/.yaml`, `resources/.md`, and `../../workflows/scm.md`, and detailed CM workflows, the CODEOWNERS checklist, and the onboarding scan are inlined rather than split into the referenced files.	3 / 5
	Total	14 / 20 Passed

Description

71%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 specific and well-targeted to the SCM/CM niche, but it omits an explicit "Use when..." trigger clause and leaves out several common user trigger terms, capping completeness and trigger coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to commit, branch, merge, rebase, resolve conflicts, manage worktrees, tag a release, or apply Conventional Commits.'

Broaden natural trigger keywords to include "commit", "rebase", "pull request", "tag", and "release" alongside the existing terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete SCM capabilities — "branching, merges, conflicts, worktrees, baselines, audit readiness, plus Conventional Commits and safe staging" — giving comprehensive coverage of the domain rather than vague abstraction.	5 / 5
Completeness	The "what" is clear (SCM/Git operations) but there is no explicit "Use when..." trigger clause, so per the rubric guideline completeness is capped at 3 with "when" only weakly implied by the listed operations.	3 / 5
Trigger Term Quality	Strong natural terms ("Git", "branching", "merges", "conflicts", "worktrees", "Conventional Commits", "staging") but omits common variations users say such as "commit", "rebase", "pull request", "tag", or "release".	4 / 5
Distinctiveness Conflict Risk	The CM-governance / audit-readiness / Conventional-Commits framing carves a clear niche distinct from a plain Git helper, with only minor overlap risk against closely related version-control skills.	4 / 5
	Total	16 / 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-scm/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.