BC gitguard
Git Security Scanner & Repo Health Auditor — entropy-based secret detection, composite health scoring, commit quality analysis, stale branch cleanup, and dependency freshness checks across all your local repos. Local-first, no data leaves your machine except optional GitHub API reads.
Git Security Scanner & Repo Health Auditor — entropy-based secret detection, composite health scoring, commit quality analysis, stale branch cleanup, and…
As a process C 52/100 · Has gaps — weak spots: result and completion, failures and branches, consistency
The same skill appears in 1 more place: ClawHub
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Secrets in code
secret-private-keygitguard_skill/entropy.py:59Private key material (key header without key body; quoted — discussed, not commanded)# '"-----BEGIN PRIVATE KEY----- …
header onlyquoted -
medium Secrets in code
secret-private-keygitguard_skill/entropy.py:130Private key material (key header without key body; quoted — discussed, not commanded)# '"-----BEGIN PRIVATE KEY----- …
header onlyquoted -
low Secrets in code
secret-high-entropy-tokenREADME.md:89High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- SOL: `3G5U…raz`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:92High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- SOL: `3G5U…raz`
quoted
Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 285 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "protocols"
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 14 mutating operations with no state check
- 40Consistency. Frontmatter name (gitguard) differs from the folder (gitguard-skill)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 17 steps
- 100Execution cost. Instruction body is 941 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +3Description length 285: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 17 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.