Agent skill

AWS Cloudformation Ecs

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

Provides AWS CloudFormation patterns for ECS clusters, task definitions, services, container definitions, auto scaling, blue/green deployments, CodeDeploy integration, ALB integration, service…

MITAuto-check: notesDevOps & Cloud

Install AWS Cloudformation Ecs

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

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

GitHub CLI
$ gh skill install giuseppe-trisciuoglio/developer-kit aws-cloudformation-ecs --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-ecs .claude/skills/aws-cloudformation-ecs && 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-ecs
GitHub stars
357
Token cost
~3.1k tokens
SKILL.md length
532 words
Files
4 (incl. references)
Skills in repo
115
Repo updated
First seen
Licence
MIT

At a glance

Provides AWS CloudFormation patterns for ECS clusters, task definitions, services, container definitions, auto scaling, blue/green deployments, CodeDeploy integration, ALB integration, service…

  • Works in 8 steps: Define ECS Cluster Parameters → Create ECS Cluster → Create Task Definition → …
  • Creating ECS clusters with CloudFormation
  • SKILL.md covers Overview, When to Use, Instructions and Best Practices, plus 4 more sections
  • Calls aws

What it does

AWS Cloudformation Ecs is an agent skill from giuseppe-trisciuoglio/developer-kit. Provides AWS CloudFormation patterns for ECS clusters, task definitions, services, container definitions, auto scaling, blue/green deployments, CodeDeploy integration, ALB integration, service discovery, monitoring, logging, template structure, parameters, outputs, and cross-stack references. Use when creating ECS clusters with CloudFormation, configuring Fargate and EC2 launch types, implementing blue/green deployments, managing auto scaling, integrating with ALB and NLB, and implementing ECS best practices.

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/constraints.md`, `references/examples.md` and `references/reference.md`).

It sits in DevOps & Cloud, covering Deployment and Infrastructure as code. It works with AWS CloudFormation. 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

  • Creating ECS clusters with CloudFormation
  • Configuring Fargate and EC2 launch types
  • Implementing blue/green deployments
  • Managing auto scaling

Example prompts

  • “Use the aws-cloudformation-ecs skill to provide AWS CloudFormation patterns for ECS clusters, task definitions, services, container definitions…”
  • “/aws-cloudformation-ecs”

Requirements

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

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Define ECS Cluster Parameters
  2. Create ECS Cluster
  3. Create Task Definition
  4. Configure Execution Roles
  5. Create ECS Service
  6. Configure Load Balancer
  7. Implement Auto Scaling
  8. Configure Monitoring

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

    Shell commands in SKILL.md call:

    • aws

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

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.aws.amazon.com

    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 Ecs loads about 3.1k tokens when it runs, and up to ~22k if it reads all its reference files. Until then it costs about 134 tokens; SKILL.md has 532 words of instructions outside code blocks.

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

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). 532 words, ~3,150 tokens.

Download SKILL.mdSave it as .claude/skills/aws-cloudformation-ecs/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
aws-cloudformation-ecs
description
Provides AWS CloudFormation patterns for ECS clusters, task definitions, services, container definitions, auto scaling, blue/green deployments, CodeDeploy integration, ALB integration, service discovery, monitoring, logging, template structure, parameters, outputs, and cross-stack references. Use when creating ECS clusters with CloudFormation, configuring Fargate and EC2 launch types, implementing blue/green deployments, managing auto scaling, integrating with ALB and NLB, and implementing ECS best practices.
allowed-tools
Read, Write, Bash

AWS CloudFormation ECS

Overview

Provides CloudFormation patterns for ECS clusters, task definitions, services, container definitions, auto scaling, blue/green deployments, ALB integration, monitoring, and cross-stack references.

When to Use

  • Creating or updating ECS clusters with CloudFormation
  • Configuring Fargate/EC2 launch types and capacity providers
  • Deploying services with ALB/NLB integration or blue/green deployments
  • Implementing auto scaling for ECS services
  • Setting up monitoring with Container Insights

Instructions

Follow these steps to create ECS infrastructure with CloudFormation:

1. Define ECS Cluster Parameters

Specify launch type, networking, and capacity settings:

yaml
Parameters:
  LaunchType:
    Type: String
    Default: FARGATE
    AllowedValues:
      - EC2
      - FARGATE
    Description: ECS launch type

  ContainerPort:
    Type: Number
    Default: 80
    Description: Container port

  TaskCPU:
    Type: String
    Default: 256
    AllowedValues:
      - 256
      - 512
      - 1024
      - 2048
      - 4096
    Description: Task CPU units

  TaskMemory:
    Type: String
    Default: 512
    AllowedValues:
      - 512
      - 1024
      - 2048
      - 3072
      - 4096
      - 5120
      - 6144
      - 7168
      - 8192
      - 9216
      - 10240
    Description: Task memory in MB
2. Create ECS Cluster

Define the cluster infrastructure:

yaml
Resources:
  ECSCluster:
    Type: AWS::ECS::Cluster
    Properties:
      ClusterName: !Sub "${AWS::StackName}-cluster"
      ClusterSettings:
        - Name: containerInsights
          Value: enabled
      CapacityProviders:
        - FARGATE
        - FARGATE_SPOT
      DefaultCapacityProviderStrategy:
        - CapacityProvider: FARGATE
          Weight: 1
        - CapacityProvider: FARGATE_SPOT
          Weight: 0
3. Create Task Definition

Define container configurations:

yaml
Resources:
  TaskDefinition:
    Type: AWS::ECS::TaskDefinition
    Properties:
      Family: !Sub "${AWS::StackName}-task"
      NetworkMode: awsvpc
      RequiresCompatibilities:
        - FARGATE
      Cpu: !Ref TaskCPU
      Memory: !Ref TaskMemory
      ExecutionRoleArn: !Ref ExecutionRole
      TaskRoleArn: !Ref TaskRole
      ContainerDefinitions:
        - Name: application
          Image: !Ref ImageUrl
          PortMappings:
            - ContainerPort: !Ref ContainerPort
              Protocol: tcp
          Environment:
            - Name: LOG_LEVEL
              Value: INFO
          LogConfiguration:
            LogDriver: awslogs
            Options:
              awslogs-group: !Ref LogGroup
              awslogs-region: !Ref AWS::Region
              awslogs-stream-prefix: ecs
          Memory: !Ref TaskMemory

Validate task definition syntax before proceeding:

bash
aws cloudformation validate-template --template-body file://template.yaml
4. Configure Execution Roles

Set up IAM roles for task execution:

yaml
Resources:
  ExecutionRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument:
        Version: "2012-10-17"
        Statement:
          - Effect: Allow
            Principal:
              Service: ecs-tasks.amazonaws.com
            Action: sts:AssumeRole
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/service-role/AmazonECSTaskExecutionRolePolicy

  TaskRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument:
        Version: "2012-10-17"
        Statement:
          - Effect: Allow
            Principal:
              Service: ecs-tasks.amazonaws.com
            Action: sts:AssumeRole
      Policies:
        - PolicyName: S3Access
          PolicyDocument:
            Version: "2012-10-17"
            Statement:
              - Effect: Allow
                Action:
                  - s3:GetObject
                Resource: !Sub "${DataBucket.Arn}/*"
5. Create ECS Service

Define the service configuration:

yaml
Resources:
  ECSService:
    Type: AWS::ECS::Service
    Properties:
      ServiceName: !Sub "${AWS::StackName}-service"
      Cluster: !Ref ECSCluster
      TaskDefinition: !Ref TaskDefinition
      DesiredCount: 2
      LaunchType: FARGATE
      NetworkConfiguration:
        AwsvpcConfiguration:
          Subnets:
            - !Ref PrivateSubnet1
            - !Ref PrivateSubnet2
          SecurityGroups:
            - !Ref SecurityGroup
          AssignPublicIp: DISABLED
      LoadBalancers:
        - TargetGroupArn: !Ref TargetGroup
          ContainerName: application
          ContainerPort: !Ref ContainerPort
6. Configure Load Balancer

Set up ALB for traffic distribution:

yaml
Resources:
  LoadBalancer:
    Type: AWS::ElasticLoadBalancingV2::LoadBalancer
    Properties:
      Name: !Sub "${AWS::StackName}-alb"
      Scheme: internet-facing
      Type: application
      Subnets:
        - !Ref PublicSubnet1
        - !Ref PublicSubnet2
      SecurityGroups:
        - !Ref ALBSecurityGroup

  TargetGroup:
    Type: AWS::ElasticLoadBalancingV2::TargetGroup
    Properties:
      Port: 80
      Protocol: HTTP
      VpcId: !Ref VPC
      TargetType: ip

  Listener:
    Type: AWS::ElasticLoadBalancingV2::Listener
    Properties:
      DefaultActions:
        - TargetGroupArn: !Ref TargetGroup
          Type: forward
      LoadBalancerArn: !Ref LoadBalancer
      Port: 80
      Protocol: HTTP
7. Implement Auto Scaling

Configure Application Auto Scaling:

yaml
Resources:
  ScalableTarget:
    Type: AWS::ApplicationAutoScaling::ScalableTarget
    Properties:
      MaxCapacity: 10
      MinCapacity: 1
      ResourceId: !Sub "service/${ECSCluster}/${ECSService}"
      ScalableDimension: ecs:service:DesiredCount
      ServiceNamespace: ecs

  ScalingPolicy:
    Type: AWS::ApplicationAutoScaling::ScalingPolicy
    Properties:
      PolicyName: !Sub "${AWS::StackName}-scaling"
      PolicyType: TargetTrackingScaling
      ScalingTargetId: !Ref ScalableTarget
      TargetTrackingScalingPolicyConfiguration:
        TargetValue: 70.0
        PredefinedMetricSpecification:
          PredefinedMetricType: ECSServiceAverageCPUUtilization
8. Configure Monitoring

Enable CloudWatch Container Insights:

yaml
Resources:
  LogGroup:
    Type: AWS::Logs::LogGroup
    Properties:
      LogGroupName: !Sub "/ecs/${AWS::StackName}"
      RetentionInDays: 7

Before deployment: Create a change set to preview changes:

bash
aws cloudformation create-change-set \
  --stack-name my-ecs-stack \
  --template-body file://template.yaml \
  --change-set-type CREATE
aws cloudformation execute-change-set --change-set-name <arn>

Best Practices

Task Definition
  • Use Family naming for version tracking and immutable deployments
  • Keep task definition under 1 KB (CloudFormation limit) by referencing external configs
  • Configure HealthCheck in container definitions for ECS health monitoring
  • Set both Cpu and Memory at task level for Fargate
Service Deployment
  • Enable DeploymentCircuitBreaker for automatic rollback on failures
  • Use HealthCheckGracePeriodSeconds matching application startup time
  • Configure MinimumHealthyPercent (100) and MaximumPercent (200) for zero-downtime updates
  • Reference task definition by logical ID only—ECS automatically uses latest revision
Networking
  • Always use awsvpc network mode for Fargate
  • Place tasks in private subnets with NAT gateway for outbound access
  • Configure security groups to allow only required ports (not 0.0.0.0/0)
Scaling
  • Use Fargate Spot with base capacity of 1 on-demand for cost optimization
  • Set MaxHealthyDuration on capacity provider strategy for Spot interruption handling
  • Monitor STEADY_STATE failures in CloudWatch for task startup issues

Constraints and Warnings

Show full SKILL.md (231 more words)Show less
Resource Limits
  • Task definition size limit: 1 KB when using CloudFormation (use ParameterStore/Secrets Manager for large configs)
  • Maximum 10 containers per task definition in Fargate
  • CPU must be specified for Fargate tasks (256-4096 units, in 1024 increments)
  • Memory must be allocated (512-30720 MB depending on CPU)
Operational Limits
  • ENI limits apply per subnet—plan for at least 1 ENI per task in each AZ
  • Fargate Spot tasks receive 2-minute interruption notice—implement graceful shutdown signals (SIGTERM)
  • Service updates require new task definition revision—cannot modify existing versions
  • DesiredCount updates during deployment may conflict with auto scaling policies
CloudFormation-Specific
  • Cross-stack references required for VPC IDs, Subnet IDs, and Security Group IDs passed between stacks
  • Use !GetAtt for referencing stack outputs in same template
  • Ensure IAM role ARNs use Fn::Sub with stack name for portability

Examples

Minimal Fargate Service
yaml
AWSTemplateFormatVersion: "2010-09-09"
Description: Minimal ECS Fargate service

Resources:
  Cluster:
    Type: AWS::ECS::Cluster
    Properties:
      ClusterName: !Sub "${AWS::StackName}-cluster"

  TaskDefinition:
    Type: AWS::ECS::TaskDefinition
    Properties:
      Family: !Sub "${AWS::StackName}-task"
      NetworkMode: awsvpc
      RequiresCompatibilities: [FARGATE]
      Cpu: 256
      Memory: 512
      ContainerDefinitions:
        - Name: app
          Image: nginx:latest
          PortMappings:
            - ContainerPort: 80

  Service:
    Type: AWS::ECS::Service
    Properties:
      Cluster: !Ref Cluster
      ServiceName: !Sub "${AWS::StackName}-svc"
      TaskDefinition: !Ref TaskDefinition
      DesiredCount: 2
      LaunchType: FARGATE
      DeploymentCircuitBreaker:
        Enable: true
        Rollback: true
ECS with ALB Integration
yaml
Resources:
  Service:
    Type: AWS::ECS::Service
    Properties:
      Cluster: !Ref ECSCluster
      TaskDefinition: !Ref TaskDefinition
      DesiredCount: 2
      LaunchType: FARGATE
      HealthCheckGracePeriodSeconds: 30
      NetworkConfiguration:
        AwsvpcConfiguration:
          Subnets: [!Ref PrivateSubnet1, !Ref PrivateSubnet2]
          SecurityGroups: [!Ref TaskSecurityGroup]
      LoadBalancers:
        - TargetGroupArn: !Ref TargetGroup
          ContainerName: app
          ContainerPort: 8080

  TargetGroup:
    Type: AWS::ElasticLoadBalancingV2::TargetGroup
    Properties:
      Port: 80
      Protocol: HTTP
      VpcId: !Ref VPC
      TargetType: ip
      HealthCheckPath: /health

References

For detailed implementation guidance, see:

  • constraints.md - Resource limits (task definition size, container limits, memory limits, CPU limits), operational constraints (service updates, ENI limits, task start time, scaling delays), security constraints (IAM roles, network mode, security groups, secrets rotation), cost considerations (Fargate pricing, data transfer, ECR storage, monitoring), deployment constraints (blue/green requirements, CodeDeploy integration, rollbacks, task drift), and availability constraints (Fargate Spot, multi-AZ, health checks, service discovery)

© 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 3 other files (references) in plugins/developer-kit-aws/skills/aws-cloudformation/aws-cloudformation-ecs of giuseppe-trisciuoglio/developer-kit.

  • SKILL.md
  • references/constraints.md
  • references/examples.md
  • references/reference.md

Open the folder on GitHubat commit fe73fb3

Compare with similar skills

AWS Cloudformation Ecs 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 Ecs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
AWS Cloudformation Ecs this skillgiuseppe-trisciuoglio/developer-kit357—~3.1kAutomated safety check: NotesMIT
AWS Cdk Developmentzxkane/aws-skills3672 repos~2.5kAutomated safety check: PassMIT
Cloudformationitsmostafa/aws-agent-skills1.2k—~2.5kAutomated safety check: PassMIT
AWS Observabilityaws/agent-toolkit-for-aws2.8k—~7.2kAutomated safety check: PassApache-2.0
AWS Cdkaws/agent-toolkit-for-aws2.8k—~2.2kAutomated safety check: PassApache-2.0
AWS Cloudformationaws/agent-toolkit-for-aws2.8k—~3.6kAutomated safety check: PassApache-2.0

Similar skills

  • AWS Cdk Development

    zxkane/aws-skills

    AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.

    367 GitHub starsUsed in 2 repos~2.5k tokens
    DevOps & CloudAuto-check passed
  • Cloudformation

    itsmostafa/aws-agent-skills

    AWS CloudFormation infrastructure as code for stack management.

    1.2k GitHub stars~2.5k tokensUpdated 5 days ago
    DevOps & CloudAuto-check passed
  • AWS Observability

    aws/agent-toolkit-for-aws

    Official

    Builds, configures, debugs, and optimizes AWS observability - operator-symptom questions and detecting Omni vs classic CloudWatch.

    2.8k GitHub stars~7.2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • AWS Cdk

    aws/agent-toolkit-for-aws

    Official

    Authors, deploys, and troubleshoots AWS infrastructure using CDK with TypeScript or Python.

    2.8k GitHub stars~2.2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • AWS Cloudformation

    aws/agent-toolkit-for-aws

    Official

    Authors, validates, and troubleshoots AWS CloudFormation templates.

    2.8k GitHub stars~3.6k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • 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

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 Ecs

What does AWS Cloudformation Ecs do?

Provides AWS CloudFormation patterns for ECS clusters, task definitions, services, container definitions, auto scaling, blue/green deployments, CodeDeploy integration, ALB integration, service…. AWS Cloudformation Ecs is an agent skill from giuseppe-trisciuoglio/developer-kit. Provides AWS CloudFormation patterns for ECS clusters, task definitions, services, container definitions, auto scaling, blue/green deployments, CodeDeploy integration, ALB integration, service discovery, monitoring, logging, template structure, parameters, outputs, and cross-stack references.

When should I use AWS Cloudformation Ecs?

AWS Cloudformation Ecs fits situations like: creating ECS clusters with CloudFormation; configuring Fargate and EC2 launch types; implementing blue/green deployments; managing auto scaling.

How do I install AWS Cloudformation Ecs in Claude Code?

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

How do I install AWS Cloudformation Ecs in Codex?

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

Can I use AWS Cloudformation Ecs 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-ecs -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-ecs, .gemini/skills/aws-cloudformation-ecs, .github/skills/aws-cloudformation-ecs and .opencode/skills/aws-cloudformation-ecs in your project.

What does AWS Cloudformation Ecs need to run?

Going by SKILL.md and its folder, AWS Cloudformation Ecs needs the command-line tools its instructions call (aws). Its frontmatter pre-approves these tools: Read, Write, Bash.

Does AWS Cloudformation Ecs access the network?

SKILL.md names 1 domain. As links in the text: docs.aws.amazon.com. This is read from the text; nothing was executed.

Is AWS Cloudformation Ecs 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 Ecs use?

AWS Cloudformation Ecs 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 Ecs use?

About 3.1k tokens (SKILL.md is roughly 13k 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 19k tokens, read only when the agent opens those files.

What are the alternatives to AWS Cloudformation Ecs?

Skills that share tags, products or a category with AWS Cloudformation Ecs: AWS Cdk Development (zxkane/aws-skills, 367 stars), Cloudformation (itsmostafa/aws-agent-skills, 1.2k stars), AWS Observability (aws/agent-toolkit-for-aws, 2.8k stars) and AWS Cdk (aws/agent-toolkit-for-aws, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains AWS Cloudformation Ecs?

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.