SKILLEMALL.ai

AC git-guardrails

Install a hook that blocks destructive git commands before an AI agent runs them. Use when an agent force-pushed or ran reset --hard, when adding git safety hooks, or when protecting main from agent pushes.

borghei/Claude-Skills Agent Skills author: borghei 8 files · 3 scripts body ≈ 3 446 tokens Open the sourcegithub.com↗ analyzed 7 h ago

Install a hook that blocks destructive git commands before an AI agent runs them.

As a process C 55/100 · Has gaps — References files that are not bundled: assets/pre-push, assets/pre-rebase

ProcedureSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
90
Run on models
none yet
Process rating
C
55/100
Has gaps
References files that are not bundled: assets/pre-push, assets/pre-rebase
Tools and files w 18
0
Inputs and preconditions w 11
0
When it triggers w 12
50
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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: 8. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: assets/pre-push
  • warning missing-ref reference to a missing file: assets/pre-rebase

Process rating: all ten parameters 55/100

Will not run. References files that are not bundled: assets/pre-push, assets/pre-rebase
  • 0Tools and files. 2 referenced file(s) missing: assets/pre-push, assets/pre-rebase
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 50When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 60Failures and branches. 2 branches
  • 100Steps. 42 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3446 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 11 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
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 206: enough signal without eating the budget
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 42 items
  • +3Output format is stated explicitly
  • +4Has examples (4 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)
  • +3All 2 scripts are documented
  • +1License stated

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