look-up-schema
Skill1 starsChanged 26 days agoApache-2.0View on GitHub
Look up the exact schema of a Terraform provider, resource or data source: which attributes exist, which are required, optional, computed, sensitive or deprecated, and which nested blocks exist. Use before writing or editing a resource block, and whenever you are unsure of an argument name, type or nesting. Do not guess attribute names from memory.
In this repository8 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- check-moduleSkill
- explain-planSkill
- fix-review-findingsSkill
- onboard-toolchainSkill
- review-moduleSkill
- trace-change-impactSkill
- writing-terraformSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Read the schema from the module's own locked provider instead of recalling it.
≈ “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.
Files
Look up a schema
Read the schema from the module's own locked provider instead of recalling it.
Call provider_schema with:
path: the module directory, relative to the project root.type: a resource or data source type such asaws_instance, or the provider's local name such asawswhenkindisprovider.kind:resource,data_sourceorprovider.block: optional dotted path such asebs_block_deviceora.b, to read a nested block or nested attribute instead of the top level.
The provider comes from the module's required_providers, or is hashicorp/<prefix> when undeclared. The module must be initialized with a .terraform.lock.hcl entry for the provider; if the call fails for that reason, say so and ask the user to run terraform init instead of guessing.
The result gives the locked provider version beside the configuration's version constraint, the level's attributes (type, required, optional, computed, sensitive, deprecated, description) and one summary per nested block (nesting mode, min and max items, attribute and block counts). Read the top level first, then call again with block for each nested block you need.
Report the locked version with what you found, since schemas change between versions. Treat a deprecated attribute as a warning to the user, not something to use.
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
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.

