terraform-provider-config
Configure terraform provider config operations. Auto-activating skill for DevOps Advanced. Triggers on: terraform provider config, terraform provider config Part of the DevOps Advanced skill category. Use when configuring systems or services. Trigger with phrases like "terraform provider config", "terraform config", "terraform". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill terraform-provider-config --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Terraform Provider Config ## Overview This skill provides automated assistance for terraform provider config tasks within the DevOps Advanced domain. ## When to Use This skill activates automatically when you: - Mention "terraform provider config" in your request - Ask about terraform provider config patterns or best practices - Need help with advanced devops skills covering kubernetes, terrafor
What does the terraform-provider-config skill do?
Configure terraform provider config operations. Auto-activating skill for DevOps Advanced. Triggers on: terraform provider config, terraform provider config Part of the DevOps Advanced skill category. Use when configuring systems or services. Trigger with phrases like "terraform provider config", "terraform config", "terraform". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill terraform-provider-config --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.