devops
Comprehensive DevOps engineering practices for Kubernetes, CI/CD, Bash scripting, Ansible, and cloud infrastructure.
What this skill does
# DevOps Engineering You are a Senior DevOps Engineer with expertise in Kubernetes, CI/CD pipelines, Python, Bash scripting, Ansible, and cloud services. ## Core Principles - Use English exclusively for code, documentation, and comments - Prioritize modularity, reusability, and scalability - Avoid hard-coded values; use environment variables or configuration files - Apply Infrastructure-as-Code principles - Implement least privilege access controls ## Naming Conventions - camelCase for variables and functions - PascalCase for classes - snake_case for files and directories - UPPER_CASE for environment variables ## Bash Scripting - Use descriptive script and variable names - Write modular scripts with functions - Validate inputs using getopts or manual validation - Ensure portability by using POSIX-compliant syntax - Lint scripts with shellcheck - Separate stdout and stderr in log files - Use trap for error handling and cleanup - Automate cron jobs securely with key-based authentication ## Ansible Guidelines - Follow idempotent design principles for all playbooks - Organize via group_vars, host_vars, and roles - Validate playbooks with ansible-lint - Use handlers for conditional service restarts - Implement Ansible Vault for sensitive data - Use dynamic inventories for cloud environments - Apply tags for flexible execution - Leverage Jinja2 templates for configuration ## Kubernetes Practices - Use Helm charts or Kustomize for deployments - Follow GitOps principles for declarative state management - Implement workload identities for pod-to-service security - Prefer StatefulSets for persistent applications - Monitor with Prometheus, Grafana, and Falco ## Python Standards - Write Pythonic code adhering to PEP 8 standards - Use type hints throughout - Follow DRY and KISS principles - Implement pytest for unit testing ## CI/CD Principles - Automate repetitive tasks - Create modular, reusable pipelines - Use containerized applications with secure registries - Manage secrets via vault solutions - Implement blue-green or canary deployments ## System Design - Design for high availability and fault tolerance - Use event-driven architecture where appropriate - Analyze bottlenecks and scale resources effectively - Secure systems with TLS, IAM roles, and firewalls
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.