Official agent skill

Service Quota Check

by aws in aws/tools-for-devops-agent

Use this skill during any incident investigation, capacity planning, or operational troubleshooting when the issue may be caused by hitting AWS service limits.

OfficialApache-2.0Auto-check passedDevOps & Cloud

Install Service Quota Check

skills CLI
$ npx skills add aws/tools-for-devops-agent --skill service-quota-check -a claude-code

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

GitHub CLI
$ gh skill install aws/tools-for-devops-agent service-quota-check --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/aws/tools-for-devops-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/service-quota-check .claude/skills/service-quota-check && 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
service-quota-check
GitHub stars
103
Token cost
~3.4k tokens
SKILL.md length
1,217 words
Files
7 (incl. references)
Skills in repo
31
Repo updated
First seen
Licence
Apache-2.0

At a glance

Use this skill during any incident investigation, capacity planning, or operational troubleshooting when the issue may be caused by hitting AWS service limits.

  • Works in 6 steps: Identify the Service and Quota Context → Retrieve Quota Value and Utilization → Calculate Utilization and Assess Risk → …
  • Tasks that involve Site reliability engineering
  • SKILL.md covers When to Use This Skill, Prerequisites, Step 1: Identify the Service… and Step 2: Retrieve Quota Value…, plus 8 more sections
  • Calls aws

What it does

Service Quota Check is an agent skill from aws/tools-for-devops-agent, published by the product's own GitHub organization. Use this skill during any incident investigation, capacity planning, or operational troubleshooting when the issue may be caused by hitting AWS service limits. Activate when you observe throttling errors (ThrottlingException, TooManyRequestsException, LimitExceededException), resource creation failures, capacity-related alarms, or when a recommendation involves provisioning new AWS resources.

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `.skilleval.yaml`, `CHANGELOG.md` and `README.md`).

It sits in DevOps & Cloud, covering Site reliability engineering. It works with Amazon Web Services. The repository describes itself as: Open-source tools for AWS DevOps Agent - extend DevOps Agent with ready-to-use skills, custom agents, and other tools, for incident response, root cause analysis, and operational…. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Site reliability engineering

Example prompts

  • “/service-quota-check”

Workflow steps

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

  1. Identify the Service and Quota Context
  2. Retrieve Quota Value and Utilization
  3. Calculate Utilization and Assess Risk
  4. Request Quota Increase
  5. Check for Pending Requests
  6. Post-Increase Verification

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    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):

    • console.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

Service Quota Check loads about 3.4k tokens when it runs, and up to ~4.6k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 1,217 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 aws/tools-for-devops-agent at commit ddda70b, republished under its Apache-2.0 licence (© aws). 1,217 words, ~3,401 tokens.

Download SKILL.mdSave it as .claude/skills/service-quota-check/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
service-quota-check
description
Use this skill during any incident investigation, capacity planning, or operational troubleshooting when the issue may be caused by hitting AWS service limits. Activate when you observe throttling errors (ThrottlingException, TooManyRequestsException, LimitExceededException), resource creation failures, capacity-related alarms, or when a recommendation involves provisioning new AWS resources.
metadata.author
yuriypr
metadata.version
1.0.0
metadata.aws-devops-agent-skills.agent-t
Chat tasks, Incident RCA
metadata.aws-devops-agent-skills.aws-ser
AWS Service Quotas, Amazon CloudWatch
metadata.aws-devops-agent-skills.technic
Operations, Capacity Planning

Service Quota Check

Use this skill to check AWS service quota utilization during investigations and before provisioning new resources. It determines whether a quota is nearing its limit (85%+ utilization) and takes action: requesting a quota increase via the Service Quotas API when possible, or recommending a support case when programmatic increases are not supported.

When to Use This Skill

  • An error message indicates throttling or limit exceeded (e.g., ThrottlingException, TooManyRequestsException, LimitExceededException, ResourceLimitExceeded).
  • A resource creation or scaling operation fails with capacity errors.
  • An investigation recommendation involves provisioning additional AWS resources (e.g., adding EC2 instances, creating VPCs, adding NAT Gateways, launching RDS instances).
  • Capacity planning or pre-launch readiness checks.
  • Proactive monitoring of quota utilization across services.

Prerequisites

  • The agent must have permissions to call Service Quotas APIs:
    • servicequotas:ListServices
    • servicequotas:ListServiceQuotas
    • servicequotas:GetServiceQuota
    • servicequotas:RequestServiceQuotaIncrease
    • servicequotas:ListRequestedServiceQuotaChangeHistory
    • servicequotas:CreateSupportCase
  • For utilization data via CloudWatch, the agent needs:
    • cloudwatch:GetMetricData
    • cloudwatch:GetMetricStatistics
  • Service Quotas is a regional service. Quotas must be checked in the region where resources are deployed.

Step 1: Identify the Service and Quota Context

Determine which service and quota to check based on the investigation context:

  1. From error messages — extract the service name and specific limit mentioned.
  2. From recommendations — if the recommendation is to provision resources, identify the service (e.g., EC2, VPC, RDS, Lambda, ELB) and the resource type.
  3. From alarms — if a CloudWatch alarm indicates capacity pressure, identify the underlying service.
Common service codes
AWS ServiceService Code
Amazon EC2ec2
Amazon VPCvpc
Elastic Load Balancingelasticloadbalancing
Amazon RDSrds
AWS Lambdalambda
Amazon ECSecs
Amazon EKSeks
Amazon S3s3
Amazon DynamoDBdynamodb
AWS Fargatefargate
Amazon CloudWatchmonitoring
AWS CloudFormationcloudformation
Amazon SQSsqs
Amazon SNSsns
Amazon ElastiCacheelasticache
Amazon OpenSearch Servicees
Auto Scalingautoscaling

If you do not know the service code, use:

bash
aws service-quotas list-services \
  --query "Services[?contains(ServiceName, '<keyword>')]" \
  --region <region>

Step 2: Retrieve Quota Value and Utilization

Get the applied quota value
bash
aws service-quotas get-service-quota \
  --service-code <service-code> \
  --quota-code <quota-code> \
  --region <region>

The response includes:

  • Value — the current quota limit (applied value, or default if no increase was granted)
  • Adjustable — whether the quota can be increased
  • UsageMetric — CloudWatch metric to check current utilization (if available)
If you do not know the quota code

List all quotas for the service:

bash
aws service-quotas list-service-quotas \
  --service-code <service-code> \
  --region <region>

Filter by quota name keyword:

bash
aws service-quotas list-service-quotas \
  --service-code <service-code> \
  --region <region> \
  --query "Quotas[?contains(QuotaName, '<keyword>')]"
Get current utilization via CloudWatch

If the UsageMetric field is present in the quota response, query CloudWatch for actual usage:

bash
aws cloudwatch get-metric-statistics \
  --namespace "<MetricNamespace>" \
  --metric-name "<MetricName>" \
  --dimensions <MetricDimensions> \
  --start-time "<15-minutes-ago-ISO8601>" \
  --end-time "<now-ISO8601>" \
  --period 300 \
  --statistics <MetricStatisticRecommendation> \
  --region <region>

The UsageMetric object from the quota response provides all the parameters:

  • MetricNamespace — typically AWS/Usage
  • MetricName — typically ResourceCount
  • MetricDimensions — service-specific dimensions (e.g., Class, Resource, Service, Type)
  • MetricStatisticRecommendation — either Maximum or Sum
Alternative: count resources directly

If no UsageMetric is available, count resources using the service's Describe/List APIs:

ServiceCommand to count resources
EC2 instancesaws ec2 describe-instances --query "Reservations[].Instances[] | length(@)"
VPCsaws ec2 describe-vpcs --query "Vpcs | length(@)"
NAT Gatewaysaws ec2 describe-nat-gateways --filter Name=state,Values=available --query "NatGateways | length(@)"
EIPsaws ec2 describe-addresses --query "Addresses | length(@)"
RDS instancesaws rds describe-db-instances --query "DBInstances | length(@)"
Lambda functionsaws lambda list-functions --query "Functions | length(@)"
ECS servicesaws ecs list-services --cluster <cluster> --query "serviceArns | length(@)"
ALBsaws elbv2 describe-load-balancers --query "LoadBalancers | length(@)"

Step 3: Calculate Utilization and Assess Risk

Calculate utilization percentage
utilization_pct = (current_usage / quota_value) × 100
Risk assessment thresholds
UtilizationRisk LevelAction
< 70%LowNo action needed. Report current state.
70% – 84%MediumFlag as approaching limit. Monitor closely.
85% – 94%HighRecommend quota increase. Proceed to Step 4.
95% – 100%CriticalUrgent quota increase required. Proceed to Step 4.
= 100%ExhaustedQuota is blocking operations. Immediate action required.
Present findings

Always show the user a summary table:

┌─────────────────────────────────────────────────────────────────────┐
│ Service Quota Check                                                  │
├─────────────────────────┬───────────┬─────────┬─────────┬───────────┤
│ Quota Name              │ Limit     │ Used    │ % Used  │ Status    │
├─────────────────────────┼───────────┼─────────┼─────────┼───────────┤
│ Running On-Demand (std) │ 1920 vCPU │ 1740    │ 90.6%   │ ⚠️ HIGH   │
│ VPCs per Region         │ 5         │ 5       │ 100%    │ 🚫 FULL   │
│ NAT Gateways per AZ    │ 5         │ 3       │ 60%     │ ✅ OK     │
└─────────────────────────┴───────────┴─────────┴─────────┴───────────┘

Step 4: Request Quota Increase

When utilization is at 85% or higher, proceed based on whether the quota is adjustable.

Decision Tree
Is utilization >= 85%?
├── NO → Report findings, no action needed
└── YES → Check "Adjustable" field
    ├── Adjustable = true → Proceed to quota increase request
    │   ├── Ask user to confirm the increase
    │   ├── User confirms → Submit request via API (Step 4a)
    │   └── User declines → Report findings only
    └── Adjustable = false → Recommend support case (Step 4b)
Step 4a: Submit Quota Increase Request via API

Before requesting, determine the desired new value. Use this formula:

desired_value = current_quota × 1.5   (50% increase over current limit)

If the quota is already exhausted (100% utilization), recommend:

desired_value = current_quota × 2.0   (double the current limit)

Present the recommendation to the user:

"The quota [QuotaName] is at [X]% utilization ([current_usage]/[quota_value]). I recommend increasing it to [desired_value]. Shall I submit the quota increase request?"

If the user confirms, submit the request:

bash
aws service-quotas request-service-quota-increase \
  --service-code <service-code> \
  --quota-code <quota-code> \
  --desired-value <desired-value> \
  --region <region>

After submitting, check the response:

  • Status: PENDING — request submitted successfully. Inform the user that AWS will review the request (typically processed within minutes for auto-approved quotas, or up to a few days for manual review).
  • Status: CASE_OPENED — a support case was automatically created.

Report the request ID and status:

"Quota increase request submitted successfully.

  • Request ID: [Id]
  • Status: [Status]
  • Desired value: [DesiredValue]

You can check the status with: aws service-quotas get-requested-service-quota-change --request-id <Id>"

Show full SKILL.md (490 more words)Show less
Step 4b: Recommend Support Case (non-adjustable quotas)

If the quota cannot be increased via the API (Adjustable: false), inform the user:

"The quota [QuotaName] cannot be increased programmatically via the Service Quotas API. To request an increase, you need to open an AWS Support case.

Would you like me to:

  1. Open a support case via the Service Quotas API (requires an existing pending quota increase request)
  2. Provide instructions to open a support case manually via the AWS Console"

If there is an existing pending request, use:

bash
aws service-quotas create-support-case \
  --request-id <request-id> \
  --region <region>

Otherwise, provide manual instructions:

"To request this quota increase:

  1. Go to the AWS Support Center: https://console.aws.amazon.com/support/
  2. Create a new case → Service limit increase
  3. Select service: [ServiceName]
  4. Select quota: [QuotaName]
  5. Specify the new desired value: [desired_value]
  6. Provide business justification for the increase"

Step 5: Check for Pending Requests

Before submitting a new request, check if there is already a pending increase request:

bash
aws service-quotas list-requested-service-quota-change-history-by-quota \
  --service-code <service-code> \
  --quota-code <quota-code> \
  --region <region> \
  --query "RequestedQuotas[?Status=='PENDING']"

If a pending request exists:

  • Report the existing request details (ID, desired value, date submitted)
  • Do NOT submit a duplicate request
  • Offer to create a support case to expedite the existing request if needed

Step 6: Post-Increase Verification

After a quota increase is approved, verify the new limit:

bash
aws service-quotas get-service-quota \
  --service-code <service-code> \
  --quota-code <quota-code> \
  --region <region>

Confirm the Value field reflects the new limit.


Multi-Quota Check (Bulk Assessment)

When a recommendation involves provisioning multiple resource types, or for proactive capacity planning, check all relevant quotas for the service:

bash
aws service-quotas list-service-quotas \
  --service-code <service-code> \
  --region <region>

For each quota that has a UsageMetric, calculate utilization. Report any quotas at 70%+ utilization as part of a comprehensive capacity report.


Common Quota Codes Reference

See references/common-quota-codes.md for a table of frequently checked quota codes by service.


Error Handling

ErrorCauseResolution
NoSuchResourceExceptionQuota code does not exist for the serviceUse list-service-quotas to find the correct code
TooManyRequestsExceptionService Quotas API is throttlingWait and retry with exponential backoff
ResourceAlreadyExistsExceptionA pending request already existsCheck existing requests (Step 5)
QuotaExceededExceptionThe desired value exceeds the maximum allowedReduce the desired value or open a support case
AccessDeniedExceptionMissing IAM permissionsCheck that the agent has servicequotas:* permissions
DependencyAccessDeniedExceptionMissing permissions on the target serviceVerify IAM policies for the target service

Tips

  • Check the region: Service quotas are regional. Always query in the region where resources are deployed, unless the quota is global (check GlobalQuota: true).
  • Applied vs. default: get-service-quota returns the applied value (which may differ from the default if a previous increase was granted). Use get-aws-default-service-quota to see the original default.
  • Auto-approved vs. manual: Many quotas (especially EC2 vCPU limits) are auto-approved within minutes. Others require manual AWS review. The API does not indicate which type a quota is in advance — submit the request and monitor the status.
  • Resource-level quotas: Some quotas (e.g., OpenSearch instances per domain) are resource-level. Use --context-id with the resource ARN for these.
  • Rate-based quotas: Some quotas measure requests per second (e.g., API call rates). These require different monitoring approaches (CloudWatch metrics rather than resource counts).

© aws, Apache-2.0. 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 skills/service-quota-check of aws/tools-for-devops-agent.

  • SKILL.md
  • .skilleval.yaml
  • CHANGELOG.md
  • README.md
  • evals/eval_queries.json
  • evals/evals.json
  • references/common-quota-codes.md

Open the folder on GitHubat commit ddda70b

Compare with similar skills

Service Quota Check 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.

Service Quota Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Service Quota Check this skillaws/tools-for-devops-agent103—~3.4kAutomated safety check: PassApache-2.0
Resilience Hub Getting Startedaws/agent-toolkit-for-aws2.8k—~968Automated safety check: PassApache-2.0
Cloud Cost Optimizationwshobson/agents40k14 repos~1.7kAutomated safety check: PassMIT
Review Docshashicorp/terraform-provider-aws11k—~1.3kAutomated safety check: PassMPL-2.0
AWS Cdk Developmentzxkane/aws-skills3672 repos~2.5kAutomated safety check: PassMIT
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2606 repos~1.1kAutomated safety check: NotesCustom licence

Similar skills

  • Resilience Hub Getting Started

    aws/agent-toolkit-for-aws

    Official

    Sets up AWS Resilience Hub v2 from scratch: creates resilience policies with SLO targets, registers systems and user journeys, onboards services with input sources, and runs a first failure mode…

    2.8k GitHub stars~968 tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.

    40k GitHub starsUsed in 14 repos~1.7k tokens
    DevOps & CloudAuto-check passed
  • Review Docs

    hashicorp/terraform-provider-aws

    Official

    Review a Terraform AWS Provider PR's end-user documentation (website/docs//.markdown): whether docs are needed, description openings, argument/attribute style, section structure, tags wording, code…

    11k GitHub stars~1.3k tokensUpdated yesterday
    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
  • 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
  • Terravision Cloud Diagrams

    patrickchugh/terravision

    Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.

    1.6k GitHub stars~5.6k tokensUpdated 4 days ago
    DevOps & CloudAuto-check: notes

More from aws/tools-for-devops-agent

All 31 skills in this repo
  • Aiml GPU Training Cluster Investigation

    aws/tools-for-devops-agent

    Official

    A skill your agent uses for GPU training or inference clusters on SageMaker HyperPod (Slurm or EKS), ParallelCluster, or self-managed EC2/EKS GPU instances.

    103 GitHub stars~5.4k tokensUpdated yesterday
    Auto-check passed
  • AWS Health Events

    aws/tools-for-devops-agent

    Official

    ALWAYS use this skill in the beginning of any incident investigation, root cause analysis, or operational troubleshooting.

    103 GitHub stars~4.6k tokensUpdated yesterday
    Auto-check passed
  • Database Migration Service Expertise

    aws/tools-for-devops-agent

    Official

    AWS Database Migration Service (DMS) operational review and troubleshooting skill.

    103 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Ecs Operation Review

    aws/tools-for-devops-agent

    Official

    Performs a comprehensive Amazon ECS operations review across the 6 review pillars (Resiliency & HA, Observability, Security, Operations, Performance, Additional Analysis) using read-only AWS APIs…

    103 GitHub stars~4.8k tokensUpdated yesterday
    Auto-check passed
  • Rds Operation Review

    aws/tools-for-devops-agent

    Official

    Comprehensive Amazon RDS and Aurora operational review aligned with the AWS Well-Architected Framework and RDS/Aurora best practices.

    103 GitHub stars~4.8k tokensUpdated yesterday
    Auto-check passed
  • Sagemaker AI Ops Review

    aws/tools-for-devops-agent

    Official

    Amazon SageMaker AI Operational Review. An agent skill from aws/tools-for-devops-agent.

    103 GitHub stars~3.9k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Service Quota Check

What does Service Quota Check do?

Use this skill during any incident investigation, capacity planning, or operational troubleshooting when the issue may be caused by hitting AWS service limits. Service Quota Check is an agent skill from aws/tools-for-devops-agent, published by the product's own GitHub organization. Use this skill during any incident investigation, capacity planning, or operational troubleshooting when the issue may be caused by hitting AWS service limits.

When should I use Service Quota Check?

Service Quota Check fits situations like: tasks that involve Site reliability engineering.

How do I install Service Quota Check in Claude Code?

Run `npx skills add aws/tools-for-devops-agent --skill service-quota-check -a claude-code`. Or copy the skill folder (skills/service-quota-check in aws/tools-for-devops-agent) into .claude/skills/service-quota-check in your project. Claude Code loads it when a task matches its description.

How do I install Service Quota Check in Codex?

Run `npx skills add aws/tools-for-devops-agent --skill service-quota-check -a codex`. Or copy the skill folder (skills/service-quota-check in aws/tools-for-devops-agent) into .agents/skills/service-quota-check in your project. Codex loads it when a task matches its description.

Can I use Service Quota Check 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 aws/tools-for-devops-agent --skill service-quota-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/service-quota-check, .gemini/skills/service-quota-check, .github/skills/service-quota-check and .opencode/skills/service-quota-check in your project.

What does Service Quota Check need to run?

Going by SKILL.md and its folder, Service Quota Check needs the command-line tools its instructions call (aws).

Does Service Quota Check access the network?

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

Is Service Quota Check safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Service Quota Check use?

Service Quota Check is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Service Quota Check use?

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

What are the alternatives to Service Quota Check?

Skills that share tags, products or a category with Service Quota Check: Resilience Hub Getting Started (aws/agent-toolkit-for-aws, 2.8k stars), Cloud Cost Optimization (wshobson/agents, 40k stars), Review Docs (hashicorp/terraform-provider-aws, 11k 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 Service Quota Check?

aws (a GitHub organization, an official publisher) maintains it in aws/tools-for-devops-agent, which has 103 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 9, 2026.

Source: aws/tools-for-devops-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.