SKILLEMALL.ai
GitHub ↗ RU Sign in

BC Git Commit Analyzer

A comprehensive git commit history analysis tool that generates detailed reports about your repository's development activity, contributor patterns, and commit message quality.

modbender/skill-library-mcp Agent Skills author: modbender MIT 3 files · 1 script body ≈ 2 252 tokens Open the sourcegithub.com↗ analyzed 2 d ago

A comprehensive git commit history analysis tool that generates detailed reports about your repository's development activity, contributor patterns, and…

As a process C 59/100 · Has gaps — weak spots: when it triggers, consistency, running it twice

AnalyzerSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
C
59/100
Has gaps
When it triggers w 12
20
Running it twice w 4
30
Consistency w 8
40
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 59/100

  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 22 mutating operations with no state check
  • 40Consistency. Frontmatter name (Git Commit Analyzer) differs from the folder (sovereign-git-commit-analyzer)
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, git) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 28 steps, 2 vague phrases
  • 100Execution cost. Instruction body is 2252 tokens
  • 100Progress reporting. Reports progress
  • low 12 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +1No license
  • +2Single-language instructions
  • +3Description length 176: enough signal without eating the budget
  • +4Structure: 33 headings
  • +3Step-by-step instructions: 28 items
  • +3Output format is stated explicitly
  • +4Has examples (19 code blocks)
  • +3All 1 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.