environment-management

Audits Airflow environments and generates standardized onboarding and offboarding scripts for users and groups.

Updated May 14, 2026
One-click install
npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill environment-management-focus-gts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: environment-management
Source: https://github.com/Focus-GTS/eds-content-ops-skills/tree/main/skills/environment-management
Command: npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill environment-management-focus-gts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork in managing AEM Edge Delivery Services (EDS) environments by giving you a clear, repeatable workflow for preview/live URLs and Admin API automation, plus push invalidation setup and health monitoring.

Core Features & Use Cases

  • Environment audit & URL mapping: Documents preview and live URL patterns per branch, including Admin API endpoints and custom domain routing.
  • Branch-based multi-environment strategy: Establishes safe workflows for dev/staging/production using Git branches and branch protection guidance.
  • Admin API automation: Generates shell and Node.js scripts to preview pages, publish pages, check status, and invalidate caches.
  • Push invalidation configuration: Guides setup in tools.aem.live and describes fallback behavior when it is not available.
  • Scheduled environment health checks: Creates scripts and a GitHub Actions workflow to verify reachability, freshness, code sync, content source connectivity, domain routing, and SSL expiry.

Quick Start

Use the environment-management skill to audit your project’s current preview/live setup and generate an operations runbook plus Admin API automation scripts for your configured branches.

Frequently Asked Questions about environment-management

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

FAQPage Schema
How do I automate AEM Edge Delivery Services preview and publish workflows?

Automate AEM Edge Delivery Services preview and publish workflows by generating Admin API shell or Node.js scripts to promote pages, check status, and invalidate caches across configured Git branches.

What is the best way to set up cache invalidation for AEM EDS?

Set up cache invalidation for AEM EDS by configuring push invalidation via tools.aem.live, generating Admin API scripts for manual invalidation, and defining fallback behavior when push invalidation is unavailable.

How do I manage multiple AEM environments using Git branches?

Manage multiple AEM environments by establishing a branch-based strategy that maps preview and live URLs to dev, staging, and production Git branches, including branch protection guidance and environment documentation.

Can I schedule automated health checks for my AEM Edge Delivery Services environments?

Schedule automated health checks for AEM Edge Delivery Services environments by deploying generated scripts and a GitHub Actions workflow to verify reachability, content freshness, code sync, domain routing, and SSL expiry.

Do I need an Admin API to publish AEM EDS pages from the command line?

Yes, publishing AEM EDS pages from the command line requires Admin API operations to trigger previews, promote pages to live, and verify status, all of which can be generated as deterministic automation scripts.

Why does my AEM EDS cache not update after publishing content?

AEM EDS cache may not update after publishing if push invalidation is not configured in tools.aem.live or failed silently, requiring manual cache invalidation via generated Admin API scripts as a fallback mechanism.