oma-scm

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

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.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 content is highly actionable with strong command coverage, explicit validation for destructive operations, and useful checklists, so destructive-operation caps do not bind. Its main weaknesses are redundancy (repeated commit templates and guardrails) and inlined reference material pointing to non-existent bundle files.

Suggestions

De-duplicate the commit message template: define the HEREDOC form once and reference it from the workflow steps instead of repeating it 3-4 times.

Move the full Conventional Commits spec and CM process map into the referenced resources/*.md files (and create those files), keeping SKILL.md a lean overview.

Consolidate the Guardrails and the closing 'Important notes' section, which restate the same NEVER/ALWAYS rules, to recover tokens.

Dimension	Reasoning	Score
Conciseness	The body largely assumes Git competence (no 'what is a merge' prose) and uses dense tables/commands, but repeats the full HEREDOC commit template 3-4 times and duplicates the guardrails in the closing 'Important notes', plus carries a heavy Scheduling/Scenes/SSL-primitive meta-framework that could be tightened.	3 / 5
Actionability	Many concrete executable commands (git status -sb, git diff --staged, git push --force-with-lease, gitleaks protect --staged, gh pr create) and a full commit-type table, but commit examples stay as placeholders (<type>(<scope>): <description>) rather than a single fully filled-in message, leaving a minor gap below 5.	4 / 5
Workflow Clarity	Clear sequenced workflows (Entry/Scenes, CM workflows 1-6, Conventional Commits Steps 1-5, push/amend procedures) with explicit validation (VERIFY scene, secret scan before staging, git diff --staged before amend, protected-branch check) and checklists, but the dual Quick/Full-path structure and scattered checkpoints leave minor gaps versus the clean 5 anchor.	4 / 5
Progressive Disclosure	Clear section headers and navigation exist, but the full Conventional Commits spec and CM process map are inlined even though resources/*.md files are referenced, and those referenced bundle files do not exist in the skill directory; content that could be separate is inline.	3 / 5
	Total	14 / 20 Passed

Description

66%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 an SCM/Git niche with solid natural trigger terms, but it omits any explicit 'Use when' guidance, which caps its completeness. Adding a trigger clause and a few common synonyms (commit, rebase, push, PR) would raise it.

Suggestions

Add an explicit 'Use when...' clause with concrete user trigger phrases (e.g. 'Use when the user asks to commit, branch, merge, resolve conflicts, rebase, or open a PR').

Include common natural synonyms currently missing: 'commit', 'rebase', 'push', and 'pull request'.

Lead with verb-based actions (e.g. 'Commits, branches, merges, and rebases Git changes...') to lift specificity toward the 5 anchor.

Dimension	Reasoning	Score
Specificity	Names the SCM/Git domain and lists several concrete capabilities ("branching, merges, conflicts, worktrees, baselines, audit readiness" plus "Conventional Commits and safe staging"), with only minor coverage gaps and no verb-action form, fitting just below the comprehensive 5 anchor.	4 / 5
Completeness	The 'what' is clear, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3; 'when' is only weakly implied by the topic list.	3 / 5
Trigger Term Quality	Good natural-keyword coverage ("Git", "branching", "merges", "conflicts", "worktrees", "Conventional Commits", "staging") that users would say, but misses common synonyms like "commit", "rebase", "push", and "pull request", so it is not the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	"SCM and Git" with triggers like Conventional Commits, worktrees, and audit readiness is a mostly distinct niche with only minor overlap risk against a generic commit or debug skill, not the clear-minimal-conflict 5.	4 / 5
	Total	15 / 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: .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.