Implementing Gitops
ancoleman/ai-design-components
Implement GitOps continuous delivery for Kubernetes using ArgoCD or Flux.
Agent skill
Building Gitops Workflows
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Execute use when constructing GitOps workflows using ArgoCD or Flux.
Install Building Gitops Workflows
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill building-gitops-workflows -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace building-gitops-workflows --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/building-gitops-workflows .claude/skills/building-gitops-workflows && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "building-gitops-workflows" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/building-gitops-workflows into .claude/skills/building-gitops-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-gitops-workflows", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/building-gitops-workflowsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill building-gitops-workflows -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace building-gitops-workflows --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/building-gitops-workflows .agents/skills/building-gitops-workflows && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "building-gitops-workflows" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/building-gitops-workflows into .agents/skills/building-gitops-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-gitops-workflows", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill building-gitops-workflows -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace building-gitops-workflows --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/building-gitops-workflows .cursor/skills/building-gitops-workflows && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "building-gitops-workflows" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/building-gitops-workflows into .cursor/skills/building-gitops-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-gitops-workflows", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/building-gitops-workflows--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill building-gitops-workflows -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace building-gitops-workflows --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/building-gitops-workflows .gemini/skills/building-gitops-workflows && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "building-gitops-workflows" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/building-gitops-workflows into .gemini/skills/building-gitops-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-gitops-workflows", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace building-gitops-workflowsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill building-gitops-workflows -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/building-gitops-workflows .github/skills/building-gitops-workflows && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "building-gitops-workflows" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/building-gitops-workflows into .github/skills/building-gitops-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-gitops-workflows", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill building-gitops-workflows -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace building-gitops-workflows --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/building-gitops-workflows .opencode/skills/building-gitops-workflows && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "building-gitops-workflows" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/building-gitops-workflows into .opencode/skills/building-gitops-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-gitops-workflows", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
building-gitops-workflows- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 487 words
- Files
- 4 (incl. scripts, references, assets)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Execute use when constructing GitOps workflows using ArgoCD or Flux.
- Works in 9 steps: Choose the GitOps tool based on… → Design the repository structure:… → Generate ArgoCD Application or Flux… → …
- Constructing GitOps workflows using ArgoCD
- SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 3 more sections
- Calls argocd
What it does
Building Gitops Workflows is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute use when constructing GitOps workflows using ArgoCD or Flux. Trigger with phrases like "create GitOps workflow", "setup ArgoCD", "configure Flux", or "automate Kubernetes deployments". Generates production-ready configurations, implements best practices, and ensures security-first approach for continuous deployment.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts, reference files and assets (for example `assets/README.md`, `references/README.md` and `scripts/README.md`). Compatibility notes: Designed for Claude Code
It sits in DevOps & Cloud, covering Container orchestration, GitOps and CI/CD. It works with Argo CD, Kubernetes and Git. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- Constructing GitOps workflows using ArgoCD
- With phrases like create GitOps workflow
- Automate Kubernetes deployments
Example prompts
- “create GitOps workflow”
- “setup ArgoCD”
- “configure Flux”
- “/building-gitops-workflows”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash(kubectl:*), Bash(git:*)
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Choose the GitOps tool based on requirements: ArgoCD for UI-driven management, Flux for lightweight Git-native approach
- Design the repository structure: environments/{dev,staging,prod}/ with Kustomize overlays or Helm values per environment
- Generate ArgoCD Application or Flux Kustomization manifests pointing to the Git repository path for each environment
- Configure sync policy: enable automated.selfHeal and automated.prune for non-production; use manual sync for production
- Set up Git repository credentials as a Kubernetes Secret for the GitOps operator
- Implement environment promotion: update the image tag in staging manifests, test, then promote to production via PR
- Configure notifications: Slack/email alerts on sync success, failure, or health degradation via ArgoCD Notifications or Flux Alert Provider
- Add RBAC: restrict who can sync production applications and who can modify GitOps configurations
- Validate the setup: push a manifest change to Git and verify the GitOps operator detects and applies it within the sync interval
What it can do on your machine
Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditGrepGlobBash(kubectl:*)Bash(git:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
argocd
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
argo-cd.readthedocs.iofluxcd.ioopengitops.devkustomize.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Building Gitops Workflows loads about 1.1k tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 88 tokens; SKILL.md has 487 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 487 words, ~1,107 tokens.
Download SKILL.mdSave it as
.claude/skills/building-gitops-workflows/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- building-gitops-workflows
- description
- Execute use when constructing GitOps workflows using ArgoCD or Flux. Trigger with phrases like "create GitOps workflow", "setup ArgoCD", "configure Flux", or "automate Kubernetes deployments". Generates production-ready configurations, implements best practices, and ensures security-first approach for continuous deployment.
- allowed-tools
- Read, Write, Edit, Grep, Glob, Bash(kubectl:*), Bash(git:*)
- compatibility
- Designed for Claude Code
- version
- 1.22.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- devops, deployment, kubernetes, security
Building GitOps Workflows
Overview
Construct GitOps workflows using ArgoCD or Flux to implement declarative, Git-driven continuous delivery for Kubernetes. Generate Application/Kustomization manifests, configure sync policies, set up multi-environment promotion, and implement RBAC and notification integrations.
Prerequisites
- Kubernetes cluster accessible via
kubectlwith admin permissions - Git repository for storing Kubernetes manifests (separate from application code recommended)
- ArgoCD or Flux installed on the cluster, or Helm charts ready for installation
- Container images built and pushed to a registry accessible from the cluster
- SSH key or access token for Git repository authentication from the cluster
Instructions
- Choose the GitOps tool based on requirements: ArgoCD for UI-driven management, Flux for lightweight Git-native approach
- Design the repository structure:
environments/{dev,staging,prod}/with Kustomize overlays or Helm values per environment - Generate ArgoCD Application or Flux Kustomization manifests pointing to the Git repository path for each environment
- Configure sync policy: enable
automated.selfHealandautomated.prunefor non-production; use manual sync for production - Set up Git repository credentials as a Kubernetes Secret for the GitOps operator
- Implement environment promotion: update the image tag in staging manifests, test, then promote to production via PR
- Configure notifications: Slack/email alerts on sync success, failure, or health degradation via ArgoCD Notifications or Flux Alert Provider
- Add RBAC: restrict who can sync production applications and who can modify GitOps configurations
- Validate the setup: push a manifest change to Git and verify the GitOps operator detects and applies it within the sync interval
Output
- ArgoCD Application or Flux Kustomization manifests per environment
- Git repository structure with Kustomize bases and overlays
- RBAC configuration (ArgoCD AppProject, Kubernetes RBAC)
- Notification configuration (Slack webhooks, email)
- CI pipeline step to update image tags in the GitOps repository after build
Show full SKILL.md (201 more words)Show less
Error Handling
| Error | Cause | Solution |
|---|---|---|
ComparisonError: Failed to load target state | Invalid manifest path or Git ref | Verify path: and targetRevision: in the Application manifest; check repo structure |
Authentication failed for repository | SSH key or token not configured or expired | Create/update the Git credentials Secret; verify deploy key has read access |
Application is OutOfSync but not syncing | Automated sync disabled or sync window closed | Enable automated: in syncPolicy or trigger manual sync with argocd app sync |
Resource already exists and is not managed | Resource created outside of GitOps | Add the argocd.argoproj.io/managed-by annotation or delete the conflicting resource |
Sync failed: health check timeout | Application pods not becoming ready after sync | Check pod logs; verify resource requests fit node capacity; increase health check timeout |
Examples
- "Set up ArgoCD with three Application manifests for dev, staging, and production, each pointing to a different Kustomize overlay in the GitOps repo."
- "Configure Flux with automatic image updates: scan ECR for new tags matching
v*, update the staging manifests, and create a PR for production promotion." - "Create an ArgoCD AppProject that restricts the production application to specific namespaces and requires manual sync with admin-only access."
Resources
- ArgoCD documentation: https://argo-cd.readthedocs.io/en/stable/
- Flux documentation: https://fluxcd.io/flux/
- GitOps principles: https://opengitops.dev/
- Kustomize: https://kustomize.io/
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts, references, assets) in skills/.curated/building-gitops-workflows of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- assets/README.md
- references/README.md
- scripts/README.md
Open the folder on GitHubat commit 80f86df
Compare with similar skills
Building Gitops Workflows next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Building Gitops Workflows this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Implementing Gitopsancoleman/ai-design-components | 526 | — | ~2.9k | Automated safety check: Pass | MIT | |
| GitOps with ArgoCD and Fluxwshobson/agents | 40k | 12 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Argocd GitopsBagelHole/DevOps-Security-Agent-Skills | 1.1k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Argocd Gitopssickn33/agentic-awesome-skills | 47k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Devops Automationrohitg00/awesome-claude-code-toolkit | 2.7k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
GitOps with ArgoCD and Flux
wshobson/agents
Sets up GitOps continuous delivery for Kubernetes with ArgoCD or Flux, covering installation, repository layout, sync policies, progressive delivery and secrets.
Argocd Gitops
BagelHole/DevOps-Security-Agent-Skills
Implement GitOps with ArgoCD for declarative Kubernetes deployments.
Argocd Gitops
sickn33/agentic-awesome-skills
Implement GitOps with ArgoCD for declarative Kubernetes deployments.
Devops Automation
rohitg00/awesome-claude-code-toolkit
CI/CD pipeline design with GitHub Actions, Docker, Kubernetes, Helm, and GitOps patterns
KubeSphere DevOps Overview
kubesphere/kubesphere
Explains the KubeSphere DevOps extension: Jenkins-based CI/CD, ArgoCD GitOps, how DevOps projects map to namespaces, and project naming rules.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Works with
Categories
Questions about Building Gitops Workflows
What does Building Gitops Workflows do?
Execute use when constructing GitOps workflows using ArgoCD or Flux. Building Gitops Workflows is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute use when constructing GitOps workflows using ArgoCD or Flux.
When should I use Building Gitops Workflows?
Building Gitops Workflows fits situations like: constructing GitOps workflows using ArgoCD; with phrases like create GitOps workflow; automate Kubernetes deployments.
How do I install Building Gitops Workflows in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill building-gitops-workflows -a claude-code`. Or copy the skill folder (skills/.curated/building-gitops-workflows in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/building-gitops-workflows in your project. Claude Code loads it when a task matches its description.
How do I install Building Gitops Workflows in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill building-gitops-workflows -a codex`. Or copy the skill folder (skills/.curated/building-gitops-workflows in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/building-gitops-workflows in your project. Codex loads it when a task matches its description.
Can I use Building Gitops Workflows in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill building-gitops-workflows -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/building-gitops-workflows, .gemini/skills/building-gitops-workflows, .github/skills/building-gitops-workflows and .opencode/skills/building-gitops-workflows in your project.
What does Building Gitops Workflows need to run?
Going by SKILL.md and its folder, Building Gitops Workflows needs the command-line tools its instructions call (argocd). Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash(kubectl:*), Bash(git:*). Compatibility (from SKILL.md): Designed for Claude Code.
Does Building Gitops Workflows access the network?
SKILL.md names 4 domains. As links in the text: argo-cd.readthedocs.io, fluxcd.io, opengitops.dev and kustomize.io. This is read from the text; nothing was executed.
Is Building Gitops Workflows safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Building Gitops Workflows use?
Building Gitops Workflows is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Building Gitops Workflows use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17 tokens, read only when the agent opens those files.
What are the alternatives to Building Gitops Workflows?
Skills that share tags, products or a category with Building Gitops Workflows: Implementing Gitops (ancoleman/ai-design-components, 526 stars), GitOps with ArgoCD and Flux (wshobson/agents, 40k stars), Argocd Gitops (BagelHole/DevOps-Security-Agent-Skills, 1.1k stars) and Argocd Gitops (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Building Gitops Workflows?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.