formae-import

Integrates unmanaged cloud resources into IaC codebases using formae and PKL with simulation-based verification.

5|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/platform-engineering-labs/formae-mcp --skill formae-import
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: formae-import
Source: https://github.com/platform-engineering-labs/formae-mcp/tree/main/skills/formae-import
Command: npx skills add https://github.com/platform-engineering-labs/formae-mcp --skill formae-import

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of bringing unmanaged cloud resources under the control of your Infrastructure-as-Code (IaC) codebase, preventing configuration drift and ensuring consistency.

Core Features & Use Cases

  • Discover and Import: Identifies unmanaged resources in your cloud accounts and integrates them into your existing forma/PKL IaC files.
  • Idiomatic Integration: Ensures imported resources are incorporated correctly into your codebase's structure, naming conventions, and module composition.
  • Safe Reconciliation: Verifies that the import process is side-effect free through simulation before applying changes.
  • Use Case: You've manually created an S3 bucket or a database instance. This Skill helps you seamlessly add it to your Terraform or Pulumi codebase without disrupting existing infrastructure.

Quick Start

Use the formae-import skill to bring the unmanaged S3 bucket named 'my-legacy-bucket' under formae management within the current working directory.

Frequently Asked Questions about formae-import

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import manually created cloud resources into my IaC codebase?

Unmanaged cloud resources are brought under IaC management by integrating them into existing formae and PKL files. The process enforces strict label matching and module composition to ensure idiomatic integration without disrupting existing infrastructure.

What is configuration drift and how do I prevent it when importing cloud resources?

Configuration drift occurs when manually created resources diverge from your IaC state. You prevent drift by reconciling unmanaged assets into your formae codebase, verifying the import is side-effect free through simulation before applying changes.

Does the formae-import process support safe reconciliation without side effects?

Yes, the formae-import process supports safe reconciliation by verifying imports through simulation before applying changes. This ensures the integration of unmanaged cloud resources is side-effect free and prevents disruption to existing infrastructure.

Can I bring an unmanaged S3 bucket under IaC management without disrupting existing infrastructure?

You can bring an unmanaged S3 bucket under IaC management by integrating it into your formae and PKL files. The process uses simulation-based verification to ensure the reconciliation is side-effect free and does not disrupt existing resources.

What are the limitations of importing cloud resources into formae and PKL?

The primary limitation of importing cloud resources into formae is the strict requirement for label matching and module composition. You must adhere to these constraints to ensure safe reconciliation and avoid configuration drift during the import process.