SKILLEMALL.ai

BC Git Sentinel (Code Reviewer)

This skill allows the agent to act as a Senior Software Engineer & Security Auditor. It retrieves code from the current git repository (staged changes) or specific files, and then performs a rigoro...

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

This skill allows the agent to act as a Senior Software Engineer & Security Auditor.

As a process C 53/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, consistency

AnalyzerSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
94
Quality 40%
66
Run on models
none yet
Process rating
C
53/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
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 · 6

✓ No critical or high findings

Medium and low: 6
  • low Secrets in code secret-high-entropy-token clawhub-auth.json:3
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "token": "clh_…8uQ"
    quoted
  • low Secrets in code secret-high-entropy-token package-lock.json:74
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…lh5/QnVs…M7y/WU9j+236K…xwI+0sEO…EXw==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:109
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…5Pi+N3MrBi3hlO5/m9bV…ti9+01c2U5n/SKhU…oSA==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:244
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…oyg+GOH3rYX++Kpzr…3Nk+U8XO…syg==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:303
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…vAm+c/Slfz…0Nt+v8wr…WwQ==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:382
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…8CM+MzKM…4lA==",
    detector

Files scanned: 7. 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 53/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 40Consistency. Frontmatter name (Git Sentinel (Code Reviewer)) differs from the folder (git-sentinel)
  • 60Tools and files. Uses tools (web, node) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 9 steps
  • 100Execution cost. Instruction body is 410 tokens

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)
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 200: enough signal without eating the budget
  • +4Structure: 5 headings
  • +3Step-by-step instructions: 9 items
  • +3Output format is stated explicitly

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