aws-openai-workflow

Redirect legacy AWS workflow aliases to the active maintained implementation.

2|Updated Mar 29, 2026

Search Tags:#workflow #aws #cloud #infrastructure #legacy

Ready to run

npx skills add https://github.com/NagyVikt/codex-plugins --skill aws-openai-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aws-openai-workflow
Source: https://github.com/NagyVikt/codex-plugins/tree/main/plugins/aws/skills/aws-openai-workflow
Command: npx skills add https://github.com/NagyVikt/codex-plugins --skill aws-openai-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill serves as a redirection point to ensure users access the most current and supported AWS workflow guidance, preventing the use of deprecated or outdated operational patterns.

Core Features & Use Cases

Workflow Redirection: Automatically guides users to the active, maintained AWS workflow implementation.
Standardization: Ensures that all AWS-related tasks follow the latest best practices defined in the repository.
Use Case: If you are attempting to run an AWS-related task, this skill directs you to the correct path to ensure your infrastructure operations are secure and up-to-date.

Quick Start

Please execute the aws-workflow skill instead to initiate your cloud infrastructure tasks.

Frequently Asked Questions about aws-openai-workflow

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

FAQPage Schema

Why does my AWS workflow execution redirect to a different skill?▼

Your AWS workflow execution redirects because this is a legacy alias pointing to the active, maintained AWS workflow implementation to ensure secure, up-to-date cloud infrastructure operations.

How do I update deprecated AWS workflow aliases to current repository standards?▼

To update deprecated AWS workflow aliases to current repository standards, use this redirection mechanism to transition from deprecated skill names to the maintained operational workflows.

Can I still run cloud infrastructure tasks using old AWS workflow aliases?▼

You cannot directly run cloud infrastructure tasks using old aliases; this skill simply points you to the correct path to ensure consistent execution of the current AWS workflow implementation.

What is the best way to transition from a legacy AWS workflow to a supported path?▼

The best way to transition from a legacy AWS workflow to a supported path is executing the primary aws-workflow skill, which this alias directs you to for current best practices.

Do I need this legacy alias if I already use the primary AWS workflow implementation?▼

You do not need this legacy alias if you already use the primary AWS workflow implementation, as it exists solely to facilitate the transition for users referencing deprecated skill names.