xc-console

Automate F5 XC console browser operations with deterministic selectors and metadata.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/robinmordasiewicz/f5xc-console --skill xc-console
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xc-console
Source: https://github.com/robinmordasiewicz/f5xc-console/tree/main/skills/xc-console
Command: npx skills add https://github.com/robinmordasiewicz/f5xc-console --skill xc-console

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the F5 XC console using browser automation to reliably navigate, fill forms, and monitor the GUI, eliminating repetitive manual work.

Core Features & Use Cases

  • Deterministic navigation: Uses stable selectors and pre-crawled metadata to perform repeatable tasks.
  • Multi-provider authentication: Handles Azure SSO, Google, Okta, SAML, and native login flows with VPN awareness.
  • Workflow integration: Produces console-navigation-metadata.json and supports CLI validation for cross-tool consistency, enabling end-to-end automation of common WAAP, DNS, and Cloud Site tasks.

Quick Start

Instruct the agent to open the F5 XC console and, for example, list workspaces or navigate to the WAAP workspace to begin automated tasks.

Frequently Asked Questions about xc-console

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

FAQPage Schema
How do I automate F5 XC console operations like navigating and filling forms?

Automate F5 XC console operations by using browser automation to navigate pages, fill forms, and verify UI state deterministically. Stable selectors and pre-crawled metadata ensure repeatable execution of WAAP, DNS, and Cloud Site tasks.

Does browser automation for F5 XC support multi-provider authentication like Azure SSO and Okta?

Browser automation for F5 XC supports multi-provider authentication across Azure SSO, Google, Okta, SAML, and native login flows. It includes VPN awareness to handle identity provider redirects during automated console access.

What is deterministic navigation in console automation and why is it needed?

Deterministic navigation uses stable selectors and pre-crawled console metadata to perform repeatable browser tasks. It is needed to eliminate fragile element lookups, ensuring reliable form filling and UI state verification across F5 XC workflows.

Can I integrate F5 XC console metadata into CLI validation and tooling workflows?

You can integrate F5 XC console metadata into tooling workflows by generating structured outputs like console-navigation-metadata.json. CLI validation hooks and YAML frontmatter metadata ensure cross-tool consistency for end-to-end automation.

What are the limitations of browser automation for F5 XC console tasks?

Browser automation for F5 XC relies on pre-crawled metadata and stable selectors, meaning dynamic UI changes may require re-crawling. Authentication flows also depend on VPN awareness and valid identity provider configurations for successful execution.