Back to skill
Skillv1.0.0
ClawScan security
Muguozi1 Openclaw Git Helper · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
ReviewMar 16, 2026, 3:27 AM
- Verdict
- Review
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill largely matches a simple git-wrapper but contains inconsistencies (references a git-helper CLI that is not provided) and incomplete documentation; it will run git commands in your repo and could use your existing git credentials to contact remotes.
- Guidance
- This skill appears to be a simple wrapper for git, but the SKILL.md references a 'git-helper' CLI that is not included — the repository only contains example/test scripts that call git directly. Before installing: 1) Inspect the code yourself — the provided scripts call git via subprocess (safe-looking but will run in the current directory). 2) Be aware that pull/push use your existing git credentials (SSH keys or stored HTTPS creds) and can contact and modify remote repos. 3) Don't run this in a sensitive repository until you confirm what commands will be executed; run tests/examples in a throwaway repo. 4) If you expect a 'git-helper' command, ask the author for the missing CLI or installation instructions — the documentation appears incomplete.
Review Dimensions
- Purpose & Capability
- noteThe name/description match a git helper and the included files call git via subprocess, which is expected. However SKILL.md shows a 'git-helper' CLI (commands like `git-helper status`) but there is no provided CLI or install step that creates such a command — only example/test scripts that invoke git directly. This mismatch suggests the package is incomplete or the documentation is out of sync.
- Instruction Scope
- noteRuntime instructions and examples are limited to normal git operations (status, log, branch, pull, push). They do not request unrelated files or secrets. However many sections are placeholders/TODOs and the SKILL.md does not define how/when the skill runs (no safeguards). The example/test scripts run git in the current working directory — which means behavior depends on repo state and config.
- Install Mechanism
- okNo install spec (instruction-only), no downloads, and the only required binary is git. This is low-risk from an installation perspective.
- Credentials
- concernThe skill requires no environment variables, which is proportionate. However it implicitly relies on the system's git configuration and credentials (SSH keys, credential helpers, stored HTTPS credentials). That means pull/push operations can contact remotes and authenticate using your existing keys/creds without the skill explicitly requesting them.
- Persistence & Privilege
- okThe skill is not forced-always and uses default autonomous invocation. That is normal. Note: if an agent is allowed to invoke the skill autonomously, it could execute git operations (including push/pull) that modify remote repositories using the user's configured git credentials.