Hashicorp just launched Terraform Skills These skills let AI assistants do more than just generate random HCL. They encode real Terraform knowledge and best practices, so agents can behave much closer to how an experienced Terraform engineer would. What you can do with them: Terraform code generation - Generate Terraform HCL that follows HashiCorp’s style conventions - Write and run .tftest.hcl tests - Build modules aligned with Azure Verified Modules (AVM) requirements Terraform module generation - Refactor large, monolithic Terraform configs into reusable modules - Manage multi-region and multi-environment setups using Terraform Stacks Terraform provider development - Scaffold a new Terraform provider - Implement resources, data sources, and lifecycle actions - Run and debug provider acceptance tests Why this matters:This moves Terraform closer to agentic workflows where AI is not just suggesting code, but actually understanding structure, correctness, and workflows. It lowers the friction for building and maintaining modules and providers, and it’s a strong signal of where IaC + AI is heading. If you’re thinking about AI-native DevOps, AgenticOps, or smarter IaC tooling, this is worth paying attention to. Check out the repo here : https://github.com/hashicorp/agent-skills.git comment below what questions do you have or what is it that you would like to learn about these skills.

I just built a Telegram bot which connects with my kubernetes cluster and helps me manage this from telegram. While building this, I realized, Clawdbot is super powerful. However you need to add safe execution layer to it else it can get out of control. Thats why I have created a safe execution engine along with a set of skills which can help you convert Clawdbot into your personal devops concierge. Comment if you want to build your own Devops Agents and talk to it from WhatsApp/Telegram. Skills with Devops Execution Engine : https://github.com/agenticdevops/devops-execution-engine

This community exists for one reason: To build AI-native devops systems — not just talk about AI in Ops. If you’re here expecting: - generic DevOps tips - prompt collections - “AI will replace engineers” takes - surface-level tool demos This is probably not the right place. What AgenticOps Builders Is About AgenticOps is not a buzzword. It’s the practice of designing systems where: - AI Agents improve Ops Productivity - Agentic Skills help translate Expert Knowledge into a Systemic Runbooks - AI agents observe production systems - reason across signals (metrics, logs, traces, changes) - propose or execute actions safely - operate with humans in the loop - and learn from every incident, change, and failure We focus on real DevOps/SRE/Platform Engineering problems: - Building Agentic Automation for DevOps - Codifying Expert Knowledge and make it accessible via Agents - Platform Operations with AI - Kubernetes, Cloud, IaC, CI/CD, Troubleshooting - Incident detection & triage - Root cause analysis - Remediation & rollback - Change intelligence - Observability-driven decisions - Reducing toil without losing control This is Ops-first, not ML-first. What This Community Is NOT Let’s be explicit: - ❌ Not a generic AI or ChatGPT group - ❌ Not an MLOps or model-training forum - ❌ Not a place for theory without application - ❌ Not a passive content feed If something doesn’t help an Ops team detect, decide, or act better in production, it’s out of scope. How This Community Works This is a builders community. That means: - Systems > snippets - Architectures > prompts - Tradeoffs > hype - Learning by building > learning by watching You don’t need to be an expert. You do need to be curious, honest, and willing to think in systems. How to Get the Most Value (Start Here) 👇 Introduce yourself in the comments and answer these 3 questions: 1. What do you currently work on? (DevOps, SRE, Platform, Infra, etc.) 2. What is one Ops problem you wish AI could solve better today? 3. Are you here to learn, build, or lead?