Update Provider Deps
mondoohq/mql
Upgrade an mql provider's vendored SDKs (all providers or a named subset), audit the new versions for breaking changes and fix call sites while keeping shipped MQL fields backwards-compatible, check…
Parse a 'new resource request' GitHub issue and extract the resource type, slug, and naming constraints to produce a draft resourceDefinition.json entry.
Install Issue To Resource Spec
$ npx skills add aztfmod/terraform-provider-azurecaf --skill issue-to-resource-spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aztfmod/terraform-provider-azurecaf issue-to-resource-spec --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aztfmod/terraform-provider-azurecaf.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/issue-to-resource-spec .claude/skills/issue-to-resource-spec && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "issue-to-resource-spec" agent skill from https://github.com/aztfmod/terraform-provider-azurecaf/tree/main/.github/skills/issue-to-resource-spec into .claude/skills/issue-to-resource-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-to-resource-spec", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aztfmod/terraform-provider-azurecaf/tree/main/.github/skills/issue-to-resource-specType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aztfmod/terraform-provider-azurecaf --skill issue-to-resource-spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aztfmod/terraform-provider-azurecaf issue-to-resource-spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aztfmod/terraform-provider-azurecaf.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/issue-to-resource-spec .agents/skills/issue-to-resource-spec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issue-to-resource-spec" agent skill from https://github.com/aztfmod/terraform-provider-azurecaf/tree/main/.github/skills/issue-to-resource-spec into .agents/skills/issue-to-resource-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-to-resource-spec", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aztfmod/terraform-provider-azurecaf --skill issue-to-resource-spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aztfmod/terraform-provider-azurecaf issue-to-resource-spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aztfmod/terraform-provider-azurecaf.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/issue-to-resource-spec .cursor/skills/issue-to-resource-spec && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "issue-to-resource-spec" agent skill from https://github.com/aztfmod/terraform-provider-azurecaf/tree/main/.github/skills/issue-to-resource-spec into .cursor/skills/issue-to-resource-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-to-resource-spec", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aztfmod/terraform-provider-azurecaf.git --path .github/skills/issue-to-resource-spec--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aztfmod/terraform-provider-azurecaf --skill issue-to-resource-spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aztfmod/terraform-provider-azurecaf issue-to-resource-spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aztfmod/terraform-provider-azurecaf.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/issue-to-resource-spec .gemini/skills/issue-to-resource-spec && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "issue-to-resource-spec" agent skill from https://github.com/aztfmod/terraform-provider-azurecaf/tree/main/.github/skills/issue-to-resource-spec into .gemini/skills/issue-to-resource-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-to-resource-spec", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aztfmod/terraform-provider-azurecaf issue-to-resource-specInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aztfmod/terraform-provider-azurecaf --skill issue-to-resource-spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aztfmod/terraform-provider-azurecaf.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/issue-to-resource-spec .github/skills/issue-to-resource-spec && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "issue-to-resource-spec" agent skill from https://github.com/aztfmod/terraform-provider-azurecaf/tree/main/.github/skills/issue-to-resource-spec into .github/skills/issue-to-resource-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-to-resource-spec", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aztfmod/terraform-provider-azurecaf --skill issue-to-resource-spec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aztfmod/terraform-provider-azurecaf issue-to-resource-spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aztfmod/terraform-provider-azurecaf.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/issue-to-resource-spec .opencode/skills/issue-to-resource-spec && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "issue-to-resource-spec" agent skill from https://github.com/aztfmod/terraform-provider-azurecaf/tree/main/.github/skills/issue-to-resource-spec into .opencode/skills/issue-to-resource-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-to-resource-spec", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
issue-to-resource-spec- GitHub stars
- 188
- Token cost
- ~452 tokens
- SKILL.md length
- 123 words
- Files
- 1
- Skills in repo
- 22
- Repo updated
- First seen
- Licence
- MIT
At a glance
Parse a 'new resource request' GitHub issue and extract the resource type, slug, and naming constraints to produce a draft resourceDefinition.json entry.
- Works in 4 steps: Parse the issue → Research constraints → Draft JSON entry → …
- : issue labeled feature
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- New resource request
What it does
Issue To Resource Spec is an agent skill from aztfmod/terraform-provider-azurecaf. Parse a 'new resource request' GitHub issue and extract the resource type, slug, and naming constraints to produce a draft resourceDefinition.json entry. Triggers on: issue labeled 'feature' or 'new-resource', new resource request.
Its SKILL.md is about 450 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud. It works with GitHub and Microsoft Azure. The repository describes itself as: Terraform provider for the Terraform platform engineering for Azure. The licence is MIT.
When your agent uses it
- : issue labeled feature
- New resource request
Example prompts
- “new resource request”
- “feature”
- “new-resource”
- “/issue-to-resource-spec”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit ac74615. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Issue To Resource Spec loads about 452 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 123 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aztfmod/terraform-provider-azurecaf at commit ac74615, republished under its MIT licence (© aztfmod). 123 words, ~452 tokens.
Download SKILL.mdSave it as
.claude/skills/issue-to-resource-spec/SKILL.md (or your agent's skills folder).- name
- issue-to-resource-spec
- description
- Parse a 'new resource request' GitHub issue and extract the resource type, slug, and naming constraints to produce a draft resourceDefinition.json entry. Triggers on: issue labeled 'feature' or 'new-resource', new resource request.
Issue to Resource Spec
Procedure
1. Parse the issue
Extract from the issue title and body:
- Resource type: The Terraform resource name (e.g.,
azurerm_container_app) - Slug hint: Any suggested CAF abbreviation
- Constraints hint: Any mentioned length/scope/character rules
- Azure service: The Azure service name for research
2. Research constraints
If the issue does not provide complete naming constraints, use the azure-naming-research skill procedure:
- Look up CAF abbreviation on the Microsoft Docs page
- Look up Azure naming rules
- Derive field values (regex, dashes, lowercase, scope)
3. Draft JSON entry
Using the researched values, format a complete JSON entry following the resource-definition-json skill's Format rules:
{
"name": "<resource_name>",
"min_length": <number>,
"max_length": <number>,
"validation_regex": "\"^<pattern>$\"",
"scope": "<scope>",
"slug": "<caf_abbreviation>",
"dashes": <true|false>,
"lowercase": <true|false>,
"regex": "\"[^<allowed_chars>]\"",
"official": {
"slug": "<caf_abbreviation>",
"resource": "<Official resource display name>",
"resource_provider_namespace": "<Microsoft.Provider/resourceType>"
}
}4. Output
Present the draft entry and a summary:
Resource: <resource_name>
Slug: <slug>
Length: <min>-<max>
Scope: <scope>
Status: Ready for implementationThis output can be used directly by the caf.add-resource agent.
© aztfmod, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/issue-to-resource-spec of aztfmod/terraform-provider-azurecaf.
Open the folder on GitHubat commit ac74615
Compare with similar skills
Issue To Resource Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Issue To Resource Spec this skillaztfmod/terraform-provider-azurecaf | 188 | — | ~452 | Automated safety check: Pass | MIT | |
| Update Provider Depsmondoohq/mql | 412 | — | ~4.5k | Automated safety check: Pass | Custom licence | |
| Sdaf Orientation And SurfaceAzure/sap-automation | 145 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Avm Tf ClassificationsAzure/terraform-azurerm-avm-ptn-alz | 135 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Azv Bicep Diagram SyncAzure/AZVerify | 101 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Azv Bicep Policy CheckAzure/AZVerify | 101 | — | ~4.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
Sdaf Orientation And Surface
Azure/sap-automation
Orient a newcomer to the SAP Deployment Automation Framework (SDAF): explain the spine (control plane → workload zone → SAP system → software → install → operate/remove), summarise the three…
- Official
Avm Tf Classifications
Azure/terraform-azurerm-avm-ptn-alz
A skill your agent uses whenever a contributor is deciding what KIND of Azure Verified Module to build in Terraform — resource module, pattern module, or utility module — or is naming a module /…
- Official
Azv Bicep Diagram Sync
Azure/AZVerify
Compare Bicep templates against a Draw.io Azure architecture diagram to detect resource-level divergence.
- Official
Azv Bicep Policy Check
Azure/AZVerify
Check a Bicep template against the Azure Policy assignments in the target Azure environment to determine whether the resources would be compliant before deployment.
Deploy QA
hmislk/hmis
Sync development into QA/testing environment branches (QA1-QA4, local RH staging) via PR + merge on GitHub.
More from aztfmod/terraform-provider-azurecaf
All 22 skills in this repoAzure Caf Sync
aztfmod/terraform-provider-azurecaf
Fetch the latest CAF abbreviations page from Microsoft Learn and compare against resourceDefinition.json official.slug values.
Changelog Update
aztfmod/terraform-provider-azurecaf
Update CHANGELOG.md with a new entry under the correct section.
Docs Resource Sync
aztfmod/terraform-provider-azurecaf
Ensure documentation files under docs/resources/ and docs/data-sources/ reflect current resource types with accurate examples.
Naming Rules Drift Check
aztfmod/terraform-provider-azurecaf
Re-fetch Azure naming rules for a set of resources and compare against current regex/length/scope values in resourceDefinition.json.
Resource Bulk Import
aztfmod/terraform-provider-azurecaf
Accept a list of Azure resource types, batch-research each via azure-naming-research conventions, generate JSON entries, and insert all into resourceDefinition.json.
Resource Definition JSON
aztfmod/terraform-provider-azurecaf
Manage resource entries in resourceDefinition.json for the terraform-provider-azurecaf naming provider.
Related
Works with
Categories
Questions about Issue To Resource Spec
What does Issue To Resource Spec do?
Parse a 'new resource request' GitHub issue and extract the resource type, slug, and naming constraints to produce a draft resourceDefinition.json entry. Issue To Resource Spec is an agent skill from aztfmod/terraform-provider-azurecaf.json entry.
When should I use Issue To Resource Spec?
Issue To Resource Spec fits situations like: : issue labeled feature; new resource request.
How do I install Issue To Resource Spec in Claude Code?
Run `npx skills add aztfmod/terraform-provider-azurecaf --skill issue-to-resource-spec -a claude-code`. Or copy the skill folder (.github/skills/issue-to-resource-spec in aztfmod/terraform-provider-azurecaf) into .claude/skills/issue-to-resource-spec in your project. Claude Code loads it when a task matches its description.
How do I install Issue To Resource Spec in Codex?
Run `npx skills add aztfmod/terraform-provider-azurecaf --skill issue-to-resource-spec -a codex`. Or copy the skill folder (.github/skills/issue-to-resource-spec in aztfmod/terraform-provider-azurecaf) into .agents/skills/issue-to-resource-spec in your project. Codex loads it when a task matches its description.
Can I use Issue To Resource Spec in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aztfmod/terraform-provider-azurecaf --skill issue-to-resource-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-to-resource-spec, .gemini/skills/issue-to-resource-spec, .github/skills/issue-to-resource-spec and .opencode/skills/issue-to-resource-spec in your project.
What does Issue To Resource Spec need to run?
SKILL.md names no scripts, command-line tools or credentials: Issue To Resource Spec is instructions for the agent only.
Does Issue To Resource Spec access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Issue To Resource Spec safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Issue To Resource Spec use?
Issue To Resource Spec is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Issue To Resource Spec use?
About 452 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Issue To Resource Spec?
Skills that share tags, products or a category with Issue To Resource Spec: Update Provider Deps (mondoohq/mql, 412 stars), Sdaf Orientation And Surface (Azure/sap-automation, 145 stars), Avm Tf Classifications (Azure/terraform-azurerm-avm-ptn-alz, 135 stars) and Azv Bicep Diagram Sync (Azure/AZVerify, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Issue To Resource Spec?
aztfmod (a GitHub organization) maintains it in aztfmod/terraform-provider-azurecaf, which has 188 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on September 21, 2026.
Source: aztfmod/terraform-provider-azurecaf on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.