How do I install the Arc Skill Gitops skill?

Run npx skillmds@latest add modbender/arc-skill-gitops in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Arc Skill Gitops safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Arc Skill Gitops?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Arc Skill Gitops free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Arc Skill Gitops?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Arc Skill Gitops by modbender — Agent Skill

Name: Arc Skill Gitops
Rating: 4.2 (5 reviews)
Author: modbender

File contents

Agent GitOps

Automated deployment and rollback for agent workflows. Track skill versions, deploy with confidence, roll back when things break.

Why This Exists

Agents install and update skills constantly. When an update breaks something, you need to:

Know what changed
Roll back fast
Track which version was stable

This skill manages that lifecycle.

Commands

Initialize tracking for a skill

python3 {baseDir}/scripts/gitops.py init --skill ~/.openclaw/skills/my-skill/

Snapshot the current state (before updating)

python3 {baseDir}/scripts/gitops.py snapshot --skill ~/.openclaw/skills/my-skill/ --tag "pre-update"

Deploy a skill update (snapshots current state first)

python3 {baseDir}/scripts/gitops.py deploy --skill ~/.openclaw/skills/my-skill/ --tag "v1.1"

List all snapshots for a skill

python3 {baseDir}/scripts/gitops.py history --skill ~/.openclaw/skills/my-skill/

Roll back to a previous snapshot

python3 {baseDir}/scripts/gitops.py rollback --skill ~/.openclaw/skills/my-skill/ --tag "pre-update"

Check status of all tracked skills

python3 {baseDir}/scripts/gitops.py status

Run pre-deploy checks (integrates with arc-skill-scanner if available)

python3 {baseDir}/scripts/gitops.py check --skill ~/.openclaw/skills/my-skill/

Data Storage

Snapshots and metadata are stored in ~/.openclaw/gitops/.

How It Works

init creates a git repo in the skill directory (if not already one) and records it in the tracking manifest
snapshot commits the current state with a tag
deploy takes a pre-deploy snapshot, then commits the new state
rollback restores a tagged snapshot using git checkout
check runs arc-skill-scanner (if installed) as a pre-deploy gate
history shows all tagged snapshots with timestamps
status shows all tracked skills and their current/latest versions

Tips

Always snapshot before updating a skill manually
Use deploy instead of manual updates — it snapshots automatically
Combine with arc-skill-scanner for security-gated deployments
Tags should be descriptive: "v1.2", "pre-security-patch", "stable-2026-02-15"

---name: arc-skill-gitopsdescription: Automated deployment, rollback, and version management for agent workflows and skills.--- # Agent GitOps Automated deployment and rollback for agent workflows. Track skill versions, deploy with confidence, roll back when things break. ## Why This Exists Agents install and update skills constantly. When an update breaks something, you need to: 1. Know what changed 2. Roll back fast 3. Track which version was stable This skill manages that lifecycle. ## Commands ### Initialize tracking for a skill ```bash python3 {baseDir}/scripts/gitops.py init --skill ~/.openclaw/skills/my-skill/ ``` ### Snapshot the current state (before updating) ```bash python3 {baseDir}/scripts/gitops.py snapshot --skill ~/.openclaw/skills/my-skill/ --tag "pre-update" ``` ### Deploy a skill update (snapshots current state first) ```bash python3 {baseDir}/scripts/gitops.py deploy --skill ~/.openclaw/skills/my-skill/ --tag "v1.1" ``` ### List all snapshots for a skill ```bash python3 {baseDir}/scripts/gitops.py history --skill ~/.openclaw/skills/my-skill/ ``` ### Roll back to a previous snapshot ```bash python3 {baseDir}/scripts/gitops.py rollback --skill ~/.openclaw/skills/my-skill/ --tag "pre-update" ``` ### Check status of all tracked skills ```bash python3 {baseDir}/scripts/gitops.py status ``` ### Run pre-deploy checks (integrates with arc-skill-scanner if available) ```bash python3 {baseDir}/scripts/gitops.py check --skill ~/.openclaw/skills/my-skill/ ``` ## Data Storage Snapshots and metadata are stored in `~/.openclaw/gitops/`. ## How It Works 1. **init** creates a git repo in the skill directory (if not already one) and records it in the tracking manifest 2. **snapshot** commits the current state with a tag 3. **deploy** takes a pre-deploy snapshot, then commits the new state 4. **rollback** restores a tagged snapshot using git checkout 5. **check** runs arc-skill-scanner (if installed) as a pre-deploy gate 6. **history** shows all tagged snapshots with timestamps 7. **status** shows all tracked skills and their current/latest versions ## Tips - Always snapshot before updating a skill manually - Use `deploy` instead of manual updates — it snapshots automatically - Combine with `arc-skill-scanner` for security-gated deployments - Tags should be descriptive: "v1.2", "pre-security-patch", "stable-2026-02-15"

Frequently asked questions

Arc Skill Gitops