Agent skill

AWS Cloudformation Cloudwatch

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

Provides AWS CloudFormation patterns for CloudWatch monitoring, metrics, alarms, dashboards, logs, and observability.

MITAuto-check: notesDevOps & Cloud

Install AWS Cloudformation Cloudwatch

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

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

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

At a glance

Provides AWS CloudFormation patterns for CloudWatch monitoring, metrics, alarms, dashboards, logs, and observability.

  • Works in 10 steps: Define Alarm Parameters → Create CloudWatch Alarms → Configure Alarm Actions → …
  • Creating CloudWatch metrics
  • SKILL.md covers Overview, When to Use, Instructions and Best Practices, plus 4 more sections
  • Calls aws

What it does

AWS Cloudformation Cloudwatch is an agent skill from giuseppe-trisciuoglio/developer-kit. Provides AWS CloudFormation patterns for CloudWatch monitoring, metrics, alarms, dashboards, logs, and observability. Use when creating CloudWatch metrics, alarms, dashboards, log groups, log subscriptions, anomaly detection, synthesized canaries, Application Signals, and implementing template structure with Parameters, Outputs, Mappings, Conditions, cross-stack references, and CloudWatch best practices for monitoring production infrastructure.

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

It sits in DevOps & Cloud, covering Anomaly detection, Deployment and Observability. 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 CloudWatch metrics
  • Log subscriptions
  • Anomaly detection
  • Synthesized canaries

Example prompts

  • “Use the aws-cloudformation-cloudwatch skill to provide AWS CloudFormation patterns for CloudWatch monitoring, metrics, alarms, dashboards, logs, and…”
  • “/aws-cloudformation-cloudwatch”

Requirements

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

Workflow steps

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

  1. Define Alarm Parameters
  2. Create CloudWatch Alarms
  3. Configure Alarm Actions
  4. Create Dashboards
  5. Set Up Log Groups
  6. Implement Metric Filters
  7. Add Composite Alarms
  8. Configure Log Insights Queries
  9. Validate Template
  10. Deploy and Verify

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

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

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). 804 words, ~3,692 tokens.

Download SKILL.mdSave it as .claude/skills/aws-cloudformation-cloudwatch/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
aws-cloudformation-cloudwatch
description
Provides AWS CloudFormation patterns for CloudWatch monitoring, metrics, alarms, dashboards, logs, and observability. Use when creating CloudWatch metrics, alarms, dashboards, log groups, log subscriptions, anomaly detection, synthesized canaries, Application Signals, and implementing template structure with Parameters, Outputs, Mappings, Conditions, cross-stack references, and CloudWatch best practices for monitoring production infrastructure.
allowed-tools
Read, Write, Bash

AWS CloudFormation CloudWatch Monitoring

Overview

Creates CloudWatch monitoring infrastructure using CloudFormation templates: metrics, alarms, dashboards, log groups, anomaly detection, synthesized canaries, and Application Signals.

When to Use

  • Creating CloudWatch metrics and alarms for production infrastructure
  • Building CloudWatch dashboards for multi-region visualization
  • Implementing log groups with retention, encryption, and metric filters
  • Configuring anomaly detection and composite alarms
  • Setting up cross-stack references with Parameters and Outputs
  • Validating and deploying monitoring stacks with CloudFormation

Instructions

Follow these steps to create CloudWatch monitoring infrastructure with CloudFormation:

1. Define Alarm Parameters

Specify metric namespaces, dimensions, and threshold values:

yaml
Parameters:
  ErrorRateThreshold:
    Type: Number
    Default: 5
    Description: Error rate threshold for alarms (percentage)

  LatencyThreshold:
    Type: Number
    Default: 1000
    Description: Latency threshold in milliseconds

  CpuUtilizationThreshold:
    Type: Number
    Default: 80
    Description: CPU utilization threshold (percentage)

  LogRetentionDays:
    Type: Number
    Default: 30
    AllowedValues:
      - 1
      - 3
      - 7
      - 14
      - 30
      - 60
      - 90
      - 120
      - 365
    Description: Number of days to retain log events
2. Create CloudWatch Alarms

Set up alarms for CPU, memory, disk, and custom metrics:

yaml
Resources:
  HighCpuAlarm:
    Type: AWS::CloudWatch::Alarm
    Properties:
      AlarmName: !Sub "${AWS::StackName}-high-cpu"
      AlarmDescription: Trigger when CPU utilization exceeds threshold
      MetricName: CPUUtilization
      Namespace: AWS/EC2
      Dimensions:
        - Name: InstanceId
          Value: !Ref InstanceId
      Statistic: Average
      Period: 60
      EvaluationPeriods: 3
      Threshold: !Ref CpuUtilizationThreshold
      ComparisonOperator: GreaterThanThreshold
      AlarmActions:
        - !Ref AlarmTopic

  ErrorRateAlarm:
    Type: AWS::CloudWatch::Alarm
    Properties:
      AlarmName: !Sub "${AWS::StackName}-error-rate"
      MetricName: ErrorRate
      Namespace: !Ref CustomNamespace
      Dimensions:
        - Name: Service
          Value: !Ref ServiceName
      Statistic: Average
      Period: 60
      EvaluationPeriods: 5
      Threshold: !Ref ErrorRateThreshold
      ComparisonOperator: GreaterThanThreshold
3. Configure Alarm Actions

Define SNS topics for notification delivery:

yaml
Resources:
  AlarmNotificationTopic:
    Type: AWS::SNS::Topic
    Properties:
      DisplayName: !Sub "${AWS::StackName}-alarms"
      TopicName: !Sub "${AWS::StackName}-alarms"

  AlarmTopicPolicy:
    Type: AWS::SNS::TopicPolicy
    Properties:
      PolicyDocument:
        Statement:
          - Effect: Allow
            Principal:
              Service: cloudwatch.amazonaws.com
            Action: sns:Publish
            Resource: !Ref AlarmNotificationTopic
      Topics:
        - !Ref AlarmNotificationTopic
4. Create Dashboards

Build visualization widgets for metrics across resources:

yaml
Resources:
  MonitoringDashboard:
    Type: AWS::CloudWatch::Dashboard
    Properties:
      DashboardName: !Sub "${AWS::StackName}-dashboard"
      DashboardBody: !Sub |
        {
          "widgets": [
            {
              "type": "metric",
              "x": 0,
              "y": 0,
              "width": 12,
              "height": 6,
              "properties": {
                "title": "CPU Utilization",
                "metrics": [["AWS/EC2", "CPUUtilization", "InstanceId", "${InstanceId}"]],
                "period": 300,
                "stat": "Average",
                "region": "${AWS::Region}"
              }
            }
          ]
        }
5. Set Up Log Groups

Configure retention policies and encryption settings:

yaml
Resources:
  ApplicationLogGroup:
    Type: AWS::Logs::LogGroup
    Properties:
      LogGroupName: !Sub "/aws/applications/${Environment}/${ApplicationName}"
      RetentionInDays: !Ref LogRetentionDays
      KmsKeyId: !Ref LogEncryptionKey
6. Implement Metric Filters

Create metrics from log data:

yaml
Resources:
  ErrorMetricFilter:
    Type: AWS::Logs::MetricFilter
    Properties:
      LogGroupName: !Ref ApplicationLogGroup
      FilterPattern: '[level="ERROR", msg]'
      MetricTransformations:
        - MetricValue: "1"
          MetricNamespace: !Sub "${AWS::StackName}/Application"
          MetricName: ErrorCount
7. Add Composite Alarms

Build multi-condition alarm logic:

yaml
Resources:
  SystemHealthComposite:
    Type: AWS::CloudWatch::CompositeAlarm
    Properties:
      AlarmName: !Sub "${AWS::StackName}-system-health"
      AlarmRule: !Or
        - !Ref HighCpuAlarm
        - !Ref ErrorRateAlarm
      AlarmActions:
        - !Ref AlarmTopic
8. Configure Log Insights Queries

Create saved queries for log analysis:

yaml
Resources:
  ErrorAnalysisQuery:
    Type: AWS::Logs::QueryDefinition
    Properties:
      Name: !Sub "${AWS::StackName}-errors"
      LogGroupNames:
        - !Ref ApplicationLogGroup
      QueryString: |
        fields @timestamp, @message
        | filter @message like /ERROR/
        | sort @timestamp desc
        | limit 100
9. Validate Template

Before deploying, validate the CloudFormation template:

bash
aws cloudformation validate-template --template-body file://template.yaml

For parameterized templates, test with sample values:

bash
aws cloudformation validate-template \
  --template-body file://monitoring.yaml \
  --capabilities CAPABILITY_IAM
10. Deploy and Verify

Deploy the stack and verify resources:

bash
# Deploy stack
aws cloudformation create-stack \
  --stack-name my-monitoring-stack \
  --template-body file://monitoring.yaml \
  --parameters file://parameters.json \
  --capabilities CAPABILITY_IAM

# Wait for completion
aws cloudformation wait stack-create-complete \
  --stack-name my-monitoring-stack

# Verify alarms are in OK state
aws cloudwatch describe-alarms --stack-name my-monitoring-stack

# Check dashboard accessibility
aws cloudwatch get-dashboard --dashboard-name my-monitoring-stack-dashboard

Test alarm actions before production:

bash
# Set alarm to testing state
aws cloudwatch set-alarm-state \
  --alarm-name my-alarm \
  --state-value ALARM \
  --state-reason "Testing alarm action"

Best Practices

  • Use composite alarms to reduce noise and avoid false positives
  • Set meaningful thresholds based on baseline metrics
  • Configure appropriate evaluation periods (3-5 datapoints)
  • Enable anomaly detection for metrics with variable patterns
  • Use metric math for derived metrics (error rates, latency percentiles)
  • Set appropriate log retention based on compliance needs
  • Encrypt log groups with sensitive data using KMS
  • Test alarm actions with set-alarm-state before production

Examples

Example 1: Complete Monitoring Stack
yaml
AWSTemplateFormatVersion: '2010-09-09'
Description: Complete CloudWatch monitoring setup

Parameters:
  Environment:
    Type: String
    Default: prod
    AllowedValues: [dev, staging, prod]

Resources:
  # SNS Topic for notifications
  AlarmTopic:
    Type: AWS::SNS::Topic
    Properties:
      DisplayName: !Sub "${Environment}-alarms"

  # Alarm for high CPU
  CpuAlarm:
    Type: AWS::CloudWatch::Alarm
    Properties:
      AlarmName: !Sub "${AWS::StackName}-cpu-high"
      MetricName: CPUUtilization
      Namespace: AWS/EC2
      Statistic: Average
      Period: 300
      EvaluationPeriods: 2
      Threshold: 80
      ComparisonOperator: GreaterThanThreshold
      AlarmActions:
        - !Ref AlarmTopic

  # Dashboard
  Dashboard:
    Type: AWS::CloudWatch::Dashboard
    Properties:
      DashboardName: !Ref AWS::StackName
      DashboardBody: !Sub |
        {
          "widgets": [{
            "type": "metric",
            "properties": {
              "metrics": [["AWS/EC2", "CPUUtilization"]],
              "period": 300,
              "stat": "Average"
            }
          }]
        }
Example 2: Log-Based Metrics with Filters
yaml
Resources:
  AppLogGroup:
    Type: AWS::Logs::LogGroup
    Properties:
      LogGroupName: !Sub "/app/${Environment}"
      RetentionInDays: 30

  ErrorMetricFilter:
    Type: AWS::Logs::MetricFilter
    Properties:
      LogGroupName: !Ref AppLogGroup
      FilterPattern: '"ERROR"'
      MetricTransformations:
        - MetricValue: "1"
          MetricNamespace: !Sub "${AWS::StackName}/App"
          MetricName: ErrorCount

  ErrorAlarm:
    Type: AWS::CloudWatch::Alarm
    Properties:
      AlarmName: !Sub "${AWS::StackName}-errors"
      MetricName: ErrorCount
      MetricNamespace: !Sub "${AWS::StackName}/App"
      Statistic: Sum
      Period: 300
      EvaluationPeriods: 1
      Threshold: 1
      ComparisonOperator: GreaterThanOrEqualToThreshold

Constraints and Warnings

Resource Limits
  • Maximum 5000 alarms per account
  • Maximum 50 metric filters per log group
  • Dashboard body limited to 512KB
  • Maximum 200 metrics per alarm expression
Security Considerations
  • Enable encryption on log groups containing sensitive data
  • Use IAM policies to restrict alarm action permissions
  • Avoid hardcoding thresholds in templates; use Parameters
  • Protect SNS topics with encryption and access policies
Operational Warnings
  • High-resolution alarms (10s/30s) incur higher costs
  • Missing data treatment affects alarm state; configure explicitly
  • Composite alarms can mask individual alarm states
  • Metric filters are immutable after creation; recreate to change
Cost Optimization
  • Use standard resolution (5-minute period) unless necessary
  • Set appropriate retention periods (shorter = cheaper)
  • Delete unused dashboards and custom metrics
  • Monitor CloudWatch charges with budgets and alerts
Monitoring Strategy
  • Use composite alarms to reduce alarm noise
  • Configure appropriate evaluation periods to avoid false positives
  • Set up anomaly detection for metrics with variable patterns
  • Use metric math for derived metrics (error rates, averages)
  • Implement high-resolution alarms for critical metrics
  • Create separate dashboards for different audiences (ops, dev, management)
Log Management
  • Use appropriate retention periods based on compliance requirements
  • Encrypt log groups containing sensitive data
  • Implement metric filters for critical log patterns
  • Set up cross-account log aggregation for centralized analysis
  • Use CloudWatch Logs Insights for troubleshooting
  • Configure log subscriptions to Lambda/Kinesis for real-time processing
Show full SKILL.md (313 more words)Show less
Alarm Configuration
  • Set meaningful thresholds based on baseline metrics
  • Use datapoints-to-alarm for reliability
  • Configure OK actions to reset notifications
  • Treat missing data appropriately (breaching, not breaching, ignore)
  • Test alarm actions regularly
  • Document alarm runbooks and escalation procedures
Template Structure
  • Use AWS-specific parameter types for resources
  • Implement parameter constraints for validation
  • Use Conditions for environment-specific configuration
  • Leverage Mappings for region-specific settings
  • Apply Metadata for parameter grouping
  • Use nested stacks for large monitoring setups
Dashboard Design
  • Organize dashboards by service or application tier
  • Use consistent widget layouts and sizing
  • Include text widgets for context and documentation
  • Set appropriate time ranges for data visualization
  • Use variables for dynamic dashboard filtering
  • Limit metrics per dashboard to avoid performance issues

References

For detailed implementation guidance, see:

  • alarms.md - CloudWatch metrics and alarms including base metric alarms, latency alarms, API Gateway errors, EC2 instance alarms, Lambda function alarms, composite alarms, anomaly detection, metric math, alarm actions (SNS, Auto Scaling, EC2), missing data treatment, custom metrics, metric filters, and high-resolution alarms

  • dashboards.md - CloudWatch dashboards including base template, service-specific dashboards, widget types (metric, log, text, single value, alarm status), multi-region dashboards, stacked metrics, anomaly detection widgets, math expressions, layout patterns (grid, row, column), dynamic variables, cross-account sharing, and dashboard automation

  • logs.md - CloudWatch logs including log group configurations, metric filters, subscription filters (Lambda, Kinesis Firehose), cross-account log aggregation, log insights queries, resource policies, export and archive tasks, CloudWatch agent configuration, log encryption with KMS, lifecycle management, centralized logging, and search patterns

  • constraints.md - Resource limits (5000 alarms max, 500 dashboards max), operational constraints (metric resolution, evaluation periods, dashboard widgets, cross-account), security constraints (log data access, encryption, metric filters, alarm actions), cost considerations (detailed monitoring, custom metrics, log retention, dashboard queries), and data constraints (metric age, log ingestion, filter limits)

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

  • SKILL.md
  • references/alarms.md
  • references/constraints.md
  • references/dashboards.md
  • references/examples.md
  • references/logs.md
  • references/reference.md

Open the folder on GitHubat commit fe73fb3

Compare with similar skills

AWS Cloudformation Cloudwatch 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 Cloudwatch compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
AWS Cloudformation Cloudwatch this skillgiuseppe-trisciuoglio/developer-kit357—~3.7kAutomated safety check: NotesMIT
AWS Observabilityaws/agent-toolkit-for-aws2.8k—~7.2kAutomated safety check: PassApache-2.0
Kubeshark Installerkubeshark/kubeshark12k—~3.6kAutomated safety check: NotesApache-2.0
KubeSphere ServiceMesh Managerkubesphere/kubesphere17k—~2.4kAutomated safety check: PassCustom licence
AWS Cdk Developmentzxkane/aws-skills3672 repos~2.5kAutomated safety check: PassMIT
Google Agents CLI Observabilitypifferologo/cloud-agents-cli1291 repos~2.5kAutomated safety check: PassApache-2.0

Similar skills

  • 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
  • Kubeshark Installer

    kubeshark/kubeshark

    Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.

    12k GitHub stars~3.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • KubeSphere ServiceMesh Manager

    kubesphere/kubesphere

    Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.

    17k GitHub stars~2.4k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • 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
  • Google Agents CLI Observability

    pifferologo/cloud-agents-cli

    This skill should be used when the user wants to "set up tracing", "monitor my ADK agent", "configure logging", "add observability", "debug production traffic", or needs guidance on monitoring…

    129 GitHub starsUsed in 1 repo~2.5k tokens
    DevOps & CloudAuto-check passed
  • Deploy Observability

    aliyun/alibabacloud-observability-mcp-server

    Deploy, start, and update the Alibaba Cloud Observability MCP Server (阿里云可观测 MCP Server).

    166 GitHub stars~2.6k tokensUpdated 2 mo 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

Questions about AWS Cloudformation Cloudwatch

What does AWS Cloudformation Cloudwatch do?

Provides AWS CloudFormation patterns for CloudWatch monitoring, metrics, alarms, dashboards, logs, and observability. AWS Cloudformation Cloudwatch is an agent skill from giuseppe-trisciuoglio/developer-kit. Provides AWS CloudFormation patterns for CloudWatch monitoring, metrics, alarms, dashboards, logs, and observability.

When should I use AWS Cloudformation Cloudwatch?

AWS Cloudformation Cloudwatch fits situations like: creating CloudWatch metrics; log subscriptions; anomaly detection; synthesized canaries.

How do I install AWS Cloudformation Cloudwatch in Claude Code?

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

How do I install AWS Cloudformation Cloudwatch in Codex?

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

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

What does AWS Cloudformation Cloudwatch need to run?

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

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

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

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

What are the alternatives to AWS Cloudformation Cloudwatch?

Skills that share tags, products or a category with AWS Cloudformation Cloudwatch: AWS Observability (aws/agent-toolkit-for-aws, 2.8k stars), Kubeshark Installer (kubeshark/kubeshark, 12k stars), KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars) and AWS Cdk Development (zxkane/aws-skills, 367 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains AWS Cloudformation Cloudwatch?

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.