Agent skill

AWS Cloudformation Task Ecs Deploy Gh

by giuseppe-trisciuoglio in giuseppe-trisciuoglio/developer-kit

Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD.

MITAuto-check: notesDevOps & Cloud

Install AWS Cloudformation Task Ecs Deploy Gh

skills CLI
$ npx skills add giuseppe-trisciuoglio/developer-kit --skill aws-cloudformation-task-ecs-deploy-gh -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install giuseppe-trisciuoglio/developer-kit aws-cloudformation-task-ecs-deploy-gh --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/developer-kit-aws/skills/aws-cloudformation/aws-cloudformation-task-ecs-deploy-gh .claude/skills/aws-cloudformation-task-ecs-deploy-gh && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
aws-cloudformation-task-ecs-deploy-gh
GitHub stars
357
Token cost
~2.8k tokens
SKILL.md length
774 words
Files
8 (incl. references)
Skills in repo
115
Repo updated
First seen
Licence
MIT

At a glance

Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD.

  • Works in 8 steps: Configure AWS Authentication: Set up… → Create IAM Roles: Define roles for… → Set Up ECR Repository: Create repository… → …
  • Building Docker images
  • SKILL.md covers Overview, When to Use, Instructions and Quick Start, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

AWS Cloudformation Task Ecs Deploy Gh is an agent skill from giuseppe-trisciuoglio/developer-kit. Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready container deployment pipelines. Supports ECS deployments with proper security (OIDC or IAM keys), multi-environment support, blue/green deployments, ECR private repositories with image scanning, and…

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/authentication.md`, `references/best-practices.md` and `references/deployment-strategies.md`).

It sits in DevOps & Cloud, covering Deployment, CI/CD and Infrastructure as code. It works with AWS CloudFormation, GitHub Actions, Amazon Web Services and Docker. The repository describes itself as: Modular plugin marketplace for Claude Code and agentic CLIs, with validated, spec-driven skills, agents, commands, and workflows for Java, TypeScript, Python, PHP, AWS, and AI. The licence is MIT.

When your agent uses it

  • Building Docker images
  • Updating ECS task definitions
  • Deploying ECS services
  • Integrating with CloudFormation stacks

Example prompts

  • “Use the aws-cloudformation-task-ecs-deploy-gh skill to provide patterns to deploy ECS tasks and services with GitHub Actions CI/CD”
  • “/aws-cloudformation-task-ecs-deploy-gh”

Requirements

  • Docker
  • Pre-approved tools (allowed-tools): Read, Write, Bash

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Configure AWS Authentication: Set up OIDC provider for GitHub Actions
  2. Create IAM Roles: Define roles for deployment actions
  3. Set Up ECR Repository: Create repository with image scanning
  4. Create ECS Cluster: Define cluster infrastructure
  5. Configure Task Definition: Set up task and container definitions
  6. Set Up ECS Service: Configure service with deployment strategy
  7. Create GitHub Workflow: Define CI/CD pipeline steps
  8. Configure Secrets: Store credentials securely in GitHub Secrets

What it can do on your machine

Read from SKILL.md and the folder at commit fe73fb3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

AWS Cloudformation Task Ecs Deploy Gh loads about 2.8k tokens when it runs, and up to ~40k if it reads all its reference files. Until then it costs about 147 tokens; SKILL.md has 774 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~147
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~40k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from giuseppe-trisciuoglio/developer-kit at commit fe73fb3, republished under its MIT licence (© giuseppe-trisciuoglio). 774 words, ~2,800 tokens.

Download SKILL.mdSave it as .claude/skills/aws-cloudformation-task-ecs-deploy-gh/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
aws-cloudformation-task-ecs-deploy-gh
description
Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready container deployment pipelines. Supports ECS deployments with proper security (OIDC or IAM keys), multi-environment support, blue/green deployments, ECR private repositories with image scanning, and CloudFormation infrastructure updates.
allowed-tools
Read, Write, Bash

AWS CloudFormation Task ECS Deploy with GitHub Actions

Comprehensive skill for deploying ECS containers using GitHub Actions CI/CD pipelines with CloudFormation infrastructure management.

Overview

Deploy containerized applications to Amazon ECS using GitHub Actions workflows. This skill covers the complete deployment pipeline: authentication with AWS (OIDC recommended), building Docker images, pushing to Amazon ECR, updating task definitions, and deploying ECS services. Integrate with CloudFormation for infrastructure-as-code management and implement production-grade deployment strategies.

When to Use

  • Deploying Docker containers to Amazon ECS with GitHub Actions
  • Setting up CI/CD pipelines for ECS using CloudFormation
  • Configuring AWS OIDC authentication for GitHub Actions
  • Building Docker images and pushing to Amazon ECR
  • Updating ECS task definitions dynamically in CI/CD
  • Implementing blue/green or rolling deployments for ECS
  • Managing CloudFormation stacks from GitHub Actions

Instructions

Follow these steps to set up ECS deployment with GitHub Actions:

  1. Configure AWS Authentication: Set up OIDC provider for GitHub Actions
  2. Create IAM Roles: Define roles for deployment actions
  3. Set Up ECR Repository: Create repository with image scanning
  4. Create ECS Cluster: Define cluster infrastructure
  5. Configure Task Definition: Set up task and container definitions
  6. Set Up ECS Service: Configure service with deployment strategy
  7. Create GitHub Workflow: Define CI/CD pipeline steps
  8. Configure Secrets: Store credentials securely in GitHub Secrets

Quick Start

Basic Deployment Workflow
yaml
name: Deploy to ECS
on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    permissions:
      id-token: write
      contents: read
    steps:
      - uses: actions/checkout@v4

      - name: Configure AWS credentials
        uses: aws-actions/configure-aws-credentials@v4
        with:
          role-to-assume: arn:aws:iam::123456789012:role/github-actions-ecs-role
          aws-region: us-east-1

      - name: Login to ECR
        uses: aws-actions/amazon-ecr-login@v2

      - name: Build and push image
        env:
          ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }}
          ECR_REPOSITORY: my-app
          IMAGE_TAG: ${{ github.sha }}
        run: |
          docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG .
          docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG

      - name: Verify image push
        run: |
          docker pull $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG
          echo "Image $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG verified"

      - name: Update task definition
        uses: aws-actions/amazon-ecs-render-task-definition@v1
        id: render-task
        with:
          task-definition: task-definition.json
          container-name: my-app
          image: ${{ steps.login-ecr.outputs.registry }}/my-app:${{ github.sha }}

      - name: Validate task definition
        run: |
          # Validate JSON syntax
          cat ${{ steps.render-task.outputs.task-definition }} | jq empty && echo "Task definition JSON is valid"
          # Verify container image matches expected
          CONTAINER_IMAGE=$(cat ${{ steps.render-task.outputs.task-definition }} | jq -r '.containerDefinitions[0].image')
          EXPECTED_IMAGE="${{ steps.login-ecr.outputs.registry }}/my-app:${{ github.sha }}"
          if [ "$CONTAINER_IMAGE" = "$EXPECTED_IMAGE" ]; then
            echo "Container image matches expected: $CONTAINER_IMAGE"
          else
            echo "ERROR: Container image mismatch. Expected: $EXPECTED_IMAGE, Got: $CONTAINER_IMAGE"
            exit 1
          fi

      - name: Deploy to ECS
        uses: aws-actions/amazon-ecs-deploy-task-definition@v1
        with:
          task-definition: ${{ steps.render-task.outputs.task-definition }}
          service: my-service
          cluster: my-cluster
          wait-for-service-stability: true

See references/workflow-examples.md for complete workflow examples including multi-environment and blue/green deployments.

Examples

Multi-Environment Deployment
yaml
jobs:
  deploy:
    strategy:
      matrix:
        environment: [dev, staging, prod]
    steps:
      - uses: actions/checkout@v4
      - name: Configure AWS credentials
        uses: aws-actions/configure-aws-credentials@v4
        with:
          role-to-assume: arn:aws:iam::${{ matrix.env_account }}:role/github-actions-ecs-role
          aws-region: ${{ matrix.region }}
      - name: Deploy to ${{ matrix.environment }}
        run: |
          ECR_REGISTRY=${{ env.ECR_REGISTRY }}
          docker build -t $ECR_REGISTRY/my-app:${{ github.sha }} .
          docker push $ECR_REGISTRY/my-app:${{ github.sha }}
Blue/Green Deployment with CodeDeploy
yaml
- name: Deploy with CodeDeploy
  run: |
    aws deploy create-deployment \
      --application-name my-app \
      --deployment-group-name ${{ matrix.environment }} \
      --deployment-config-name CodeDeployDefault ECSAllAtOnce \
      --revision "{\"revisionType\":\"AppSpecContent\",\"appSpecContent\":{\"content\":\"$(cat appspec.yml)\",\"filename\":\"appspec.yml\"}}"
    aws deploy wait deployment-successful --deployment-id $(aws deploy list-deployments --application-name my-app --query 'deployments[0]' --output text)

See references/workflow-examples.md for additional patterns including ECR lifecycle policies, task definition templates, and CloudFormation stack updates.

Best Practices

Security
  1. Use OIDC authentication instead of long-lived IAM keys
  2. Implement least privilege IAM roles with specific permissions
  3. Enable ECR image scanning on push
  4. Use AWS Secrets Manager for sensitive data
  5. Encrypt ECR repositories with KMS
  6. VPC endpoints for ECR and ECS without internet gateway
  7. Security groups restrict access to minimum required
Performance
  1. Docker layer caching with GitHub Actions cache
  2. Multi-stage builds to minimize image size
  3. Parallel deployments across multiple environments
  4. Fargate Spot for cost savings on non-critical workloads
  5. CloudWatch Logs with appropriate retention policies
Cost Optimization
  1. ECR lifecycle policies to clean up old images
  2. Fargate Spot instances for development/testing
  3. Right-sized task CPU and memory
  4. Auto-scaling based on metrics
  5. Scheduled scaling for predictable traffic patterns

See references/best-practices.md for detailed security, performance, and cost optimization guidelines.

Common Troubleshooting

Authentication Failures
  • Verify OIDC trust relationship matches GitHub organization/repository
  • Check IAM role has proper permissions for ECR and ECS
  • Ensure GitHub Actions repository has id-token: write permission
Deployment Failures
  • Check CloudWatch Logs for application errors
  • Verify task definition matches service requirements
  • Ensure sufficient CPU/memory in Fargate cluster
  • Review health check configuration
ECR Push Failures
  • Verify repository exists and permissions are correct
  • Check image tag format and registry URL
  • Ensure Docker daemon is running in GitHub Actions runner
  • Verify image size doesn't exceed ECR limits
Show full SKILL.md (294 more words)Show less
CloudFormation Rollback
  • Review stack events in AWS Console
  • Check parameter values match resource constraints
  • Verify IAM role has cloudformation:UpdateStack permission
  • Enable termination protection for production stacks

See references/best-practices.md for complete troubleshooting guide with debug commands.

References

Complete Examples
Configuration
Best Practices
  • references/best-practices.md - Security guidelines, performance optimization, cost optimization, monitoring, and complete troubleshooting guide

Constraints and Warnings

Resource Limits
  • GitHub Actions Limits: Usage limits per account (minutes, storage)
  • Workflow File Size: Cannot exceed 1 MB
  • Job Matrix Limits: Limits on total matrix combinations
  • Artifact Retention: Default 90-day retention
Authentication Constraints
  • OIDC Tokens: Limited lifetime (typically 5 minutes)
  • Role Session Duration: Maximum 12 hours
  • Permission Scope: Least-privilege permissions required
  • Cross-Account Access: Requires appropriate trust relationships
Operational Constraints
  • Deployment Speed: CloudFormation deployments may take time
  • Stack Locking: Cannot update while another deployment is in progress
  • ECR Rate Limits: API rate limits may affect large deployments
  • ECS Service Limits: Limits on tasks per service and services per cluster
Security Constraints
  • Secret Management: Never store secrets in repository or workflow files
  • OIDC Provider: Must be configured in AWS account before first use
  • Repository Access: Workflow secrets are scoped to repository
  • Token Security: Minimum required permissions only (contents: read, id-token: write)
Cost Considerations
  • GitHub Actions: Minutes beyond free tier incur costs
  • ECR Storage: Monthly storage costs for container images
  • ECS/Fargate: Costs for vCPU and memory resources
  • Data Transfer: Costs for data transfer between GitHub and AWS

© giuseppe-trisciuoglio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (references) in plugins/developer-kit-aws/skills/aws-cloudformation/aws-cloudformation-task-ecs-deploy-gh of giuseppe-trisciuoglio/developer-kit.

  • SKILL.md
  • references/authentication.md
  • references/best-practices.md
  • references/deployment-strategies.md
  • references/ecr-and-task-definitions.md
  • references/examples.md
  • references/reference.md
  • references/workflow-examples.md

Open the folder on GitHubat commit fe73fb3

Compare with similar skills

AWS Cloudformation Task Ecs Deploy Gh next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

AWS Cloudformation Task Ecs Deploy Gh compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
AWS Cloudformation Task Ecs Deploy Gh this skillgiuseppe-trisciuoglio/developer-kit357—~2.8kAutomated safety check: NotesMIT
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2606 repos~1.1kAutomated safety check: NotesCustom licence
Devops Deploysickn33/agentic-awesome-skills47k2 repos~1.9kAutomated safety check: PassMIT
Azure Bicep Skilltimothywarner-org/claude-code224—~2.9kAutomated safety check: PassMIT
Devops InfrastructureCloudAI-X/claude-workflow-v21.4k—~2.7kAutomated safety check: NotesMIT
AWS GitHub Oidc Scoped Rolemizchi/skills360—~1.6kAutomated safety check: PassNone

Similar skills

  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    260 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes
  • Devops Deploy

    sickn33/agentic-awesome-skills

    DevOps e deploy de aplicacoes — Docker, CI/CD com GitHub Actions, AWS Lambda, SAM, Terraform, infraestrutura como codigo e monitoramento.

    47k GitHub starsUsed in 2 repos~1.9k tokens
    DevOps & CloudAuto-check passed
  • Azure Bicep Skill

    timothywarner-org/claude-code

    A skill your agent uses when authoring, reviewing, or refactoring Azure Bicep code.

    224 GitHub stars~2.9k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • Devops Infrastructure

    CloudAI-X/claude-workflow-v2

    Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup.

    1.4k GitHub stars~2.7k tokensUpdated 4 days ago
    DevOps & CloudAuto-check: notes
  • OpenTofu/Terraform pattern for GitHub Actions OIDC trust with AWS IAM.

    360 GitHub stars~1.6k tokensUpdated 9 days ago
    DevOps & CloudAuto-check passed
  • Devops Excellence

    majiayu000/spellbook

    DevOps and CI/CD expert. An agent skill from majiayu000/spellbook.

    287 GitHub stars~2.4k tokensUpdated 2 days ago
    DevOps & CloudAuto-check: notes

More from giuseppe-trisciuoglio/developer-kit

All 115 skills in this repo
  • Nestjs Drizzle Crud Generator

    giuseppe-trisciuoglio/developer-kit

    Generates complete CRUD modules for NestJS applications with Drizzle ORM.

    357 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check: notes
  • Spring Boot Actuator

    giuseppe-trisciuoglio/developer-kit

    Provides patterns to configure Spring Boot Actuator for production-grade monitoring, health probes, secured management endpoints, and Micrometer metrics across JVM services.

    357 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check: notes
  • Spring Boot Crud Patterns

    giuseppe-trisciuoglio/developer-kit

    Provides and generates complete CRUD workflows for Spring Boot 3 services.

    357 GitHub stars~2.5k tokensUpdated 1 mo ago
    Auto-check: notes
  • Spring Boot Security JWT

    giuseppe-trisciuoglio/developer-kit

    Provides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based…

    357 GitHub stars~3.9k tokensUpdated 1 mo ago
    Auto-check: notes
  • AWS CLI Beast

    giuseppe-trisciuoglio/developer-kit

    Provides advanced AWS CLI patterns for managing EC2, Lambda, S3, DynamoDB, RDS, VPC, IAM, and CloudWatch.

    357 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check: notes
  • PR Review Comments

    giuseppe-trisciuoglio/developer-kit

    Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line.

    357 GitHub stars~1k tokensUpdated 1 mo ago
    Auto-check: notes

Categories

Questions about AWS Cloudformation Task Ecs Deploy Gh

What does AWS Cloudformation Task Ecs Deploy Gh do?

Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. AWS Cloudformation Task Ecs Deploy Gh is an agent skill from giuseppe-trisciuoglio/developer-kit. Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD.

When should I use AWS Cloudformation Task Ecs Deploy Gh?

AWS Cloudformation Task Ecs Deploy Gh fits situations like: building Docker images; updating ECS task definitions; deploying ECS services; integrating with CloudFormation stacks.

How do I install AWS Cloudformation Task Ecs Deploy Gh in Claude Code?

Run `npx skills add giuseppe-trisciuoglio/developer-kit --skill aws-cloudformation-task-ecs-deploy-gh -a claude-code`. Or copy the skill folder (plugins/developer-kit-aws/skills/aws-cloudformation/aws-cloudformation-task-ecs-deploy-gh in giuseppe-trisciuoglio/developer-kit) into .claude/skills/aws-cloudformation-task-ecs-deploy-gh in your project. Claude Code loads it when a task matches its description.

How do I install AWS Cloudformation Task Ecs Deploy Gh in Codex?

Run `npx skills add giuseppe-trisciuoglio/developer-kit --skill aws-cloudformation-task-ecs-deploy-gh -a codex`. Or copy the skill folder (plugins/developer-kit-aws/skills/aws-cloudformation/aws-cloudformation-task-ecs-deploy-gh in giuseppe-trisciuoglio/developer-kit) into .agents/skills/aws-cloudformation-task-ecs-deploy-gh in your project. Codex loads it when a task matches its description.

Can I use AWS Cloudformation Task Ecs Deploy Gh in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add giuseppe-trisciuoglio/developer-kit --skill aws-cloudformation-task-ecs-deploy-gh -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/aws-cloudformation-task-ecs-deploy-gh, .gemini/skills/aws-cloudformation-task-ecs-deploy-gh, .github/skills/aws-cloudformation-task-ecs-deploy-gh and .opencode/skills/aws-cloudformation-task-ecs-deploy-gh in your project.

What does AWS Cloudformation Task Ecs Deploy Gh need to run?

SKILL.md names no scripts, command-line tools or credentials: AWS Cloudformation Task Ecs Deploy Gh is instructions for the agent only. Our summary lists: Docker. Its frontmatter pre-approves these tools: Read, Write, Bash.

Does AWS Cloudformation Task Ecs Deploy Gh access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is AWS Cloudformation Task Ecs Deploy Gh safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does AWS Cloudformation Task Ecs Deploy Gh use?

AWS Cloudformation Task Ecs Deploy Gh is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does AWS Cloudformation Task Ecs Deploy Gh use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 37k tokens, read only when the agent opens those files.

What are the alternatives to AWS Cloudformation Task Ecs Deploy Gh?

Skills that share tags, products or a category with AWS Cloudformation Task Ecs Deploy Gh: Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars), Devops Deploy (sickn33/agentic-awesome-skills, 47k stars), Azure Bicep Skill (timothywarner-org/claude-code, 224 stars) and Devops Infrastructure (CloudAI-X/claude-workflow-v2, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains AWS Cloudformation Task Ecs Deploy Gh?

giuseppe-trisciuoglio (a GitHub user) maintains it in giuseppe-trisciuoglio/developer-kit, which has 357 GitHub stars. The repository holds 115 skills in this directory. The repository was last updated on September 10, 2026.

Source: giuseppe-trisciuoglio/developer-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.