Git Essentials
v1.0.0Essential Git commands and workflows for version control, branching, and collaboration.
⭐ 29· 22.7k·227 current·235 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (Git commands and workflows) matches the SKILL.md content. The SKILL.md metadata declares a dependency on the git binary (requires bins: ["git"]), which is appropriate for this purpose — note the registry metadata earlier listed no required binaries, so there is a minor inconsistency between the manifest and the in-file metadata.
Instruction Scope
Instructions are limited to Git usage (config, clone, commit, branch, merge, push, reset, clean, etc.). They do modify user state (e.g., writing to ~/.gitconfig via git config --global) and include destructive operations (git reset --hard, git clean -fdx, force pushes), which are expected for a Git reference but can cause data loss if used carelessly.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is downloaded or written to disk by the skill itself — lowest-risk install footprint.
Credentials
The skill does not request environment variables or credentials, which is proportional. Note that interacting with remotes (clone/push/pull) will use whatever Git auth is available on the host (SSH keys, credential helpers, or interactive username/password), but the skill itself does not ask for or exfiltrate credentials.
Persistence & Privilege
The skill does not request always:true and is user-invocable; it does not attempt to modify other skills or system-wide agent settings. Its runtime instructions change local Git state as expected for Git operations, but it does not gain elevated platform privileges.
Assessment
This skill is essentially a published cheat-sheet of Git commands and is coherent with its stated purpose. Before using it: (1) ensure git is installed on the host (the SKILL.md expects the git binary); (2) be cautious with destructive commands (reset --hard, clean -fdx, force-push) — back up important work or operate on clones/branches; (3) be aware git config --global will alter your global Git identity; (4) the skill does not request credentials, but Git operations that contact remotes will use whatever auth is configured on your machine (SSH keys or credential helpers); and (5) there is a small metadata mismatch between the manifest and the SKILL.md regarding required binaries — that's likely benign but worth noting. If you want stricter safety, avoid running destructive commands provided here unless you understand their effects or test in a disposable repo.Like a lobster shell, security has layers — review code before you run it.
latestvk97bv3vwx3mphkf8xxyp8ggdmx805dn1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🌳 Clawdis
Binsgit