AB git-deployer
Push static site content to GitHub Pages repositories. Clone, copy files, commit with timestamp, force-push. Use when updating GitHub Pages sites, deploying static sites, or syncing local content to a git-based host.
As a process B 67/100 · Nearly there — weak spots: when it triggers, consistency, running it twice
ReferenceGitHubInfrastructureSoftware developmenttype and topics are labelled automatically from the skill text
This is a copy of a skill from another catalog; the rating counts the canonical one: git-deployer (ClawHub)
How to improve
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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 67/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 22 mutating operations with no state check
- 40Consistency. Frontmatter name (git-deployer) differs from the folder (git-deployer-kryzl19)
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 20 steps
- 100Execution cost. Instruction body is 547 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)
- +1No license
- +2Single-language instructions
- +3Description length 216: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 20 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.
External checks
ClawHub: suspicious
This skill does what it says, but it can overwrite a Git branch by default and lacks safety checks around the target repository and branch.
LLM: suspicious (high) · VirusTotal: · 29 May 2026