irule-xc

Translate F5 BIG-IP iRules into Terraform HCL and JSON API configurations.

59|6|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/bitwisecook/tcl-lsp --skill irule-xc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: irule-xc
Source: https://github.com/bitwisecook/tcl-lsp/tree/main/ai/claude/skills/irule-xc
Command: npx skills add https://github.com/bitwisecook/tcl-lsp --skill irule-xc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires uv, python-json-logger, pygls, f5-sdk, volterra-sdk, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of translating F5 BIG-IP iRules into F5 Distributed Cloud (XC) configurations, reducing manual effort and potential errors.

Core Features & Use Cases

  • Automated Translation: Converts iRules into equivalent Terraform HCL and JSON API configurations for F5 XC.
  • Coverage Analysis: Provides a percentage of translated iRule constructs and highlights untranslatable parts.
  • Guidance for Alternatives: Suggests F5 XC native constructs for untranslatable iRule logic.
  • Use Case: A network engineer needs to migrate existing iRule logic from on-premises BIG-IP to the cloud. This Skill can quickly generate a baseline XC configuration, flagging areas that require manual review and adjustment.

Quick Start

Use the irule-xc skill to translate the iRule configuration found in the file 'my_irule.tcl'.

Frequently Asked Questions about irule-xc

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

FAQPage Schema
How do I translate F5 BIG-IP iRules to F5 XC configurations?

Translating F5 BIG-IP iRules to F5 XC involves automating conversion into Terraform HCL and JSON API configurations. The process analyzes translation coverage, identifies untranslatable constructs, and suggests XC alternatives for routing and security logic.

What is the best way to migrate iRule logic to F5 Distributed Cloud?

Migrating iRule logic to F5 Distributed Cloud is best handled by generating a baseline XC configuration from existing iRules. This flags untranslatable constructs for manual review and suggests XC native alternatives for accurate cloud migration.

Can I convert TCL iRule syntax to Terraform HCL for F5 XC?

Yes, converting TCL iRule syntax to Terraform HCL for F5 XC is supported. The translation generates Terraform HCL alongside JSON API outputs, providing coverage analysis and highlighting parts requiring manual adjustment.

Does F5 XC support all iRule constructs during cloud migration?

F5 XC does not support all iRule constructs during cloud migration. The translation provides coverage analysis by percentage, identifies untranslatable parts, and suggests F5 XC native constructs for routing, policy, and security logic.

Why does my iRule translation to F5 XC flag untranslatable constructs?

iRule translation to F5 XC flags untranslatable constructs because static translation cannot map all syntax to XC equivalents. It highlights these areas for manual review and suggests XC native alternatives for the missing logic.