agentleFS
nctiggynctiggy/claude-skills/skills/spectrocloud-terraform/SKILL.md

spectrocloud-terraform

Skill1 starsChanged 4 months agoNo licenceView on GitHub

The spectrocloud/spectrocloud Terraform provider -- provider block and auth, which resource maps to which Palette object, pinning the provider version against the Palette release train, importing existing clusters/profiles into state, what the provider cannot do (the API has to take over), and the failure modes that actually bite (version-mutation gotcha, scope race condition, orphaned profiles). Use when Craig says: write this as Terraform, give me the HCL for this cluster/profile, import this into state, pin the provider version, why did terraform silently overwrite the profile, why do I get perpetual diffs, terraform shows an id but the API returns null, should this be Terraform or the API. Pair with spectrocloud-common for auth/project lookup, spectrocloud-clusters and spectrocloud-cluster-profiles for the resources being declared, and spectrocloud-troubleshooting when an apply produced a cluster that will not come up.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.