SKILLEMALL.ai

AC git-sync

Manage whitelisted git repositories from chat. Status, log, diff, pull, push with security controls — only approved repos, write commands need confirmation. Repo list configurable via ~/.config/git-sync/repos.json (overrides defaults). Triggers on "git status", "repo status", "push thesis", "pull polito", "check repo", "uncommitted changes", "commit recenti". NOT for: arbitrary git repos, destructive operations (clean, reset --hard).

ClawHub Agent Skills author: LookUpMark v1.3.0 MIT-0 3 files body ≈ 303 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 50/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
83
Run on models
none yet
Process rating
C
50/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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 · 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 description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "dependencies"

Process rating: all ten parameters 50/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 2 mutating operations with no state check
  • 40Consistency. Frontmatter name (git-sync) differs from the folder (lookupmark-git-sync)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Steps. 5 steps
  • 100When it triggers. States when to use and when not to
  • 100Execution cost. Instruction body is 303 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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

  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 7 example trigger phrases
  • +4Description says when NOT to use the skill
  • +3Description length 437: enough signal without eating the budget
  • +4Structure: 4 headings
  • +3Step-by-step instructions: 5 items
  • +4Has examples (1 code blocks)
  • +3All 1 scripts are documented

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

External checks

ClawHub: clean
This is a small git helper for configured local repositories; it has real git read/write power but the behavior is disclosed, bounded, and not deceptive.
LLM: benign (high) · VirusTotal: · 29 May 2026