argocd
Deploy Kubernetes apps declaratively with Argo CD applications and projects. Use when tasks mention argocd, Argo CD, argocd app sync, Application CRD, AppProject, or GitOps with Argo CD.
What this skill does
# Argo CD Use this skill to manage GitOps deployments with Argo CD declaratively and safely. ## Quick Start 1. Run `argocd app list` to see all applications and their sync status. 2. Run `argocd app diff <name>` before any sync to preview what will change. 3. Use `argocd app sync <name>` to trigger a deployment. 4. Check `argocd app get <name>` for health and sync state after deploying. ## Intent Router - `resources/install-and-setup.md` — install argocd CLI, login, env vars, initial setup - `resources/command-cookbook.md` — argocd app list/get/create/sync/diff/history/rollback commands - `resources/application-management.md` — Application CRD, sync policies, waves, hooks, health status - `resources/rbac-and-projects.md` — AppProject CRD, RBAC policies, SSO, multi-tenancy ## Workflow ### Deploy an Application ```bash # Preview changes before syncing argocd app diff my-app # Sync a specific application argocd app sync my-app # Sync only specific resources argocd app sync my-app --resource apps:Deployment:my-deployment ``` ### Create an Application ```bash argocd app create my-app \ --repo https://github.com/org/repo \ --path k8s/overlays/production \ --dest-server https://kubernetes.default.svc \ --dest-namespace production \ --sync-policy automated ``` ### Monitor Health ```bash argocd app get my-app argocd app history my-app argocd app rollback my-app 3 ``` ## Safety Guardrails - Always run `argocd app diff <name>` before `argocd app sync` to preview what will change in production. - Use `--dry-run` when creating or modifying Applications to validate configuration before committing. - Set `syncPolicy.automated.prune: false` initially; enable pruning only after verifying the resource list is correct. - Never share the `argocd-initial-admin-secret` — rotate the admin password immediately after first login. - Use AppProject `sourceRepos` and `destinations` to restrict what repositories and clusters each team can deploy to. - Use `argocd app sync --resource <group:kind:name>` to sync specific resources rather than triggering a full sync unnecessarily. - Store repository credentials as Kubernetes secrets, not as plain-text in Application manifests. ## Related Skills kubectl, helm
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.