SKILLEMALL.ai

DC github-sync-skill

将本地创建或修改的 Claude Code 技能自动同步到 GitHub 仓库。支持增量同步、单技能同步、自动生成 README.md。

Not recommendedlow grade D
ClawHub Agent Skills author: Kuiil v2.0.0 MIT-0 8 files · 4 scripts body ≈ 785 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureGitHubSoftware developmentAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
D
41/100
safety, quality, tests
Safety 60%
27
Quality 40%
63
Run on models
none yet
Process rating
C
53/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

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

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 · 17

✓ No critical or high findings

Medium and low: 17
  • medium Dangerous commands cmd-shell-rc references/token-troubleshooting.md:118
    Writes to a shell startup file
    echo 'export GITHUB_TOKEN="ghp_xxx"' >> ~/.zshrc
  • medium Exfiltration net-credential-use references/token-troubleshooting.md:143
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "Authorization: token $GITHUB_TOKEN" \
  • medium Exfiltration net-credential-use references/token-troubleshooting.md:147
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "Authorization: token $GITHUB_TOKEN" \
  • medium Exfiltration net-credential-use references/token-troubleshooting.md:152
    Credential used in a network call (verify the destination is the intended service)
    curl -s -I -H "Authorization: token $GITHUB_TOKEN" \
  • medium Exfiltration net-credential-use scripts/cleanup_remote_repo.sh:61
    Credential used in a network call (verify the destination is the intended service)
    local items=$(curl -s -H "Authorization: token $TOKEN" \
  • medium Exfiltration net-credential-use scripts/cleanup_remote_repo.sh:74
    Credential used in a network call (verify the destination is the intended service)
    curl -s -X DELETE -H "Authorization: token $TOKEN" \
  • medium Exfiltration net-credential-use scripts/cleanup_remote_repo.sh:84
    Credential used in a network call (verify the destination is the intended service)
    remote_items=$(curl -s -H "Authorization: token $TOKEN" \
  • medium Exfiltration net-credential-use scripts/sync_to_github.sh:144
    Credential used in a network call (verify the destination is the intended service)
    response=$(curl -s -H "Authorization: token $TOKEN" \
  • medium Exfiltration net-credential-use scripts/sync_to_github.sh:180
    Credential used in a network call (verify the destination is the intended service)
    local skills=$(curl -s -H "Authorization: token $TOKEN" \
  • medium Exfiltration net-credential-use scripts/sync_to_github.sh:282
    Credential used in a network call (verify the destination is the intended service)
    local current_readme=$(curl -s -H "Authorization: token $TOKEN" \
  • medium Exfiltration net-credential-use scripts/sync_to_github.sh:322
    Credential used in a network call (verify the destination is the intended service)
    curl -s -X PUT -H "Authorization: token $TOKEN" \
  • medium Exfiltration net-credential-use scripts/verify_token.sh:55
    Credential used in a network call (verify the destination is the intended service)
    response=$(curl -s -H "Authorization: token $TOKEN" \
  • medium Exfiltration net-credential-use SKILL.md:82
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "Authorization: token $GITHUB_TOKEN" \
  • medium Exfiltration net-credential-use SKILL.md:86
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "Authorization: token $GITHUB_TOKEN" \
  • low Exfiltration net-credential-use scripts/sync_to_github.sh:128
    Credential used in a network call (verify the destination is the intended service) (destination is a well-known publishing service)
    response=$(curl -s -H "Authorization: token $TOKEN" https://api.github.com/user)
    known service
  • low Exfiltration net-credential-use scripts/verify_token.sh:22
    Credential used in a network call (verify the destination is the intended service) (destination is a well-known publishing service)
    response=$(curl -s -H "Authorization: token $TOKEN" https://api.github.com/user)
    known service
  • low Exfiltration net-credential-use scripts/verify_token.sh:36
    Credential used in a network call (verify the destination is the intended service) (destination is a well-known publishing service)
    scopes=$(curl -s -I -H "Authorization: token $TOKEN" https://api.github.com | grep -i x-oauth-scopes | tr -d '\r')
    known service

Files scanned: 8. 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")

Process rating: all ten parameters 53/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
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 100Tools and files. No external tools needed
  • 100Steps. 36 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 785 tokens
  • 100Running it twice. No mutating operations
  • low 10 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
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 68: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -41 reference files, but SKILL.md never points to them: the model will not open them
  • -31 of 4 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +4Structure: 25 headings
  • +3Step-by-step instructions: 36 items
  • +4Has examples (9 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This GitHub sync skill is mostly coherent, but it includes under-disclosed remote deletion and broad upload behavior that users should review carefully.
LLM: suspicious (high) · VirusTotal: · 29 May 2026