agentsclimarketplace

Incus tf

Skill fruafr/skills/skills/incus-tf

Agent AI skills developed by frua.fr: incus-doc

Install
npx -y skills add fruafr/skills --skill incus-tf

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Ground AI responses, Terraform project generation, and infrastructure-as-code questions in offline authoritative terraform-incus provider documentation. Must be loaded before generating Terraform configurations for Incus, writing HCL that references incus_* resources/data sources, or answering questions about managing Incus with Terraform. Reduces hallucinations by routing all claims through verified reference files.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

10.8 KB, as published. Nobody here has run it

Skill: incus-tf

  • Purpose: Ground every terraform-incus provider answer, Terraform configuration, and HCL snippet in authoritative offline documentation to eliminate hallucinations.
  • Use when: The user asks to generate Terraform configurations for Incus, asks about incus_* resources or data sources, wants to manage Incus with Terraform, or asks questions about the lxc/incus Terraform provider.
  • Don't use when: The question is purely about Incus CLI commands (use incus-doc skill), general Terraform concepts unrelated to the Incus provider, or non-Incus Terraform providers.
  • Success looks like: Every incus_* resource/data source name, argument, attribute, and configuration option is verified against the skill's reference files before being emitted; no fabricated resource types, arguments, or behaviors.

Inputs

This skill does not require explicit inputs — it activates on context (mentions of terraform-incus, incus_* resources, managing Incus with Terraform). The skill's own reference files serve as the input.

Assumptions:

  • The references/ directory within the skill folder (incus-tf/references/) exists and is up to date.
  • incus-tf/references/docs/index.md contains the authoritative documentation tree with links to all markdown files in incus-tf/references/docs/.
  • incus-tf/references/docs/provider-index.md contains the provider overview including authentication, remote configuration, and environment variables.
  • Resource documentation files are in incus-tf/references/docs/resources/.
  • Data source documentation files are in incus-tf/references/docs/data-sources/.

Output

Format: Grounded answer / Terraform HCL configuration / corrected resource block

Every incus_* resource or data source name, argument, attribute, or configuration option must be traceable to a reference file. If the reference does not contain the claim, the claim must not be emitted.

Reasoning

  1. Understand — Parse the user request; identify all incus_* resources, data sources, arguments, and provider configuration blocks.
  2. Plan — Determine which reference files to consult:
    • Provider configuration (authentication, remotes, environment variables) → incus-tf/references/docs/provider-index.md
    • Resource arguments and attributes → incus-tf/references/docs/resources/<resource>.md
    • Data source arguments and attributes → incus-tf/references/docs/data-sources/<datasource>.md
    • Full documentation tree navigation → incus-tf/references/docs/index.md
  3. Generate — Produce answer with every incus_* element verified.
  4. Verify — Re-read relevant reference lines to confirm every resource type, argument, and attribute exists.

When uncertain: Consult reference files. If not covered, state "Not found in the terraform-incus provider reference documentation."

Decision Rules

IfThen
User asks about provider setup/authOpen incus-tf/references/docs/provider-index.md, answer from it
User asks about an incus_* resourceOpen incus-tf/references/docs/index.md, find resource, open linked incus-tf/references/docs/resources/<resource>.md, answer from it
User asks about an incus_* data sourceOpen incus-tf/references/docs/index.md, find data source, open linked incus-tf/references/docs/data-sources/<datasource>.md, answer from it
User asks to generate Terraform configVerify every resource/data source type and its arguments against its reference file
User asks about provider-supported featuresConsult relevant resource/data source doc and provider-index.md
Not in references"This is not covered in the bundled terraform-incus provider reference documentation."

Documentation Pages

Provider

PageSummary
provider-indexProvider configuration, authentication, remotes, environment variables

Resources

PageSummary
certificateManage Incus client certificates
cluster_groupManage Incus cluster groups
imageManage locally-stored Incus images
instanceManage Incus instances (containers and VMs)
instance_snapshotManage Incus instance snapshots
networkManage Incus networks
network_aclManage Incus network ACLs
network_address_setManage Incus network address sets
network_forwardManage Incus network forwards
network_integrationManage Incus network integrations
network_load_balancerManage Incus network load balancers
network_peerManage Incus network peers
network_zoneManage Incus network zones
network_zone_recordManage Incus network zone records
profileManage Incus profiles
projectManage Incus projects
serverManage Incus server configuration
storage_bucketManage Incus storage buckets
storage_bucket_keyManage Incus storage bucket keys
storage_poolManage Incus storage pools
storage_volumeManage Incus storage volumes

Data Sources

PageSummary
clusterQuery Incus cluster information
imageQuery locally-stored Incus images
instanceQuery Incus instances
networkQuery Incus networks
network_aclQuery Incus network ACLs
network_address_setQuery Incus network address sets
network_forwardQuery Incus network forwards
network_integrationQuery Incus network integrations
network_load_balancerQuery Incus network load balancers
network_peerQuery Incus network peers
network_zoneQuery Incus network zones
profileQuery Incus profiles
projectQuery Incus projects
storage_bucketQuery Incus storage buckets
storage_poolQuery Incus storage pools
storage_volumeQuery Incus storage volumes

Guardrails

Must: Consult references before every incus_* claim · cite reference file path · verify every resource type, argument, and attribute exists before using · open specific doc file for exact resource/data source.

Must not: Invent resource types, arguments, or configuration options · guess HCL syntax for incus resources · output unverified incus_* blocks · reference non-existent documentation paths.

Priority: [1] Exact resource/data source doc text > [2] Provider overview > [3] No answer

Edge Cases

SituationResponse
Missing reference filesRefuse: "terraform-incus provider reference files not found."
Resource exists but argument not in docDon't use the argument
Feature not in docs"Not covered in bundled terraform-incus provider reference documentation."
User asks about incus CLI (not Terraform)"This skill covers the Terraform Incus provider, not the incus CLI. Use the incus-doc skill for CLI questions."
User asks about non-Incus Terraform provider"This skill only covers the lxc/incus Terraform provider."
Complex config with many resourcesVerify each resource type and its arguments independently

Self-Check (run before returning)

  • Correctness — every incus_* resource/data source/argument verified against a reference file
  • Format — output contains reference file paths for traceability
  • Safety — no fabricated Terraform resources or arguments
  • Completeness — all incus Terraform-related parts addressed

If a check fails after 2 attempts: Refuse with "Unable to ground the answer in the terraform-incus provider reference documentation."

Examples

Good: User asks "How do I create an incus container with Terraform?" → Agent opens incus-tf/references/docs/index.md, finds instance resource → incus-tf/references/docs/resources/instance.md, reads arguments (name, image, type), answers with verified HCL.

Bad: User asks "Use incus_init resource" → Agent guesses incus_init is valid, but it doesn't exist in the reference files. Correct: use incus_instance.

Change log

  • v1.0.0 — initial: Ground all terraform-incus provider AI output in bundled offline documentation to eliminate hallucinations.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.