cost-spike-triage

Triage a sudden AWS cost increase or bill spike to find the root cause — which service, usage type, region, and (where available) which account or resource drove the change between two periods. Use when the user says their AWS bill went up, costs spiked, there's a cost anomaly, spend is higher than expected, or asks why this month costs more than last month. Produces a ranked breakdown of the delta with the most likely driver and next steps.

Ir para a instalação

Repositório: aws-samples/sample-notiops
Última atividade na origem: 4 de agosto de 2026 às 14:38
Idioma detectado do SKILL.md: inglês
Estrelas: 6
Forks: 2

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/aws-samples/sample-notiops --skill cost-spike-triage

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

2 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

inspection-cost-idle

Interpret pre-computed low-utilisation and structural inspection findings for RDS, Aurora, and ElastiCache (Redis, Valkey, Memcached) as a cost-optimisation review. Use when a task description contains the marker NOTIOPS_INSPECTION together with hit_reason idle or structural. The deterministic rules already decided which resources look under-used, what they cost and what the savings estimate is; your job is to decide why usage is low — genuinely unused, standby or reader role, periodic batch, warmed cache, stopped instance — and the next safe action: verify_owner, delete, downsize, or leave_alone. Read the resource's role from attrs.resource_role, never from lag metrics or names. Produces one compact section per finding_id.

2026-09-04

inspection-high-load

Interpret pre-computed high-load and chronic-high inspection findings for RDS, Aurora, and ElastiCache (Redis, Valkey, Memcached). Use when a task description contains the marker NOTIOPS_INSPECTION together with hit_reason threshold_high or chronic_high. The deterministic rules already decided which resources breached which thresholds and at what severity; your job is to explain why — real degradation versus expected behaviour, correlated evidence, change attribution, blast radius at the limit, and one remediation action with its downtime cost. Read the resource's role from attrs.resource_role, never from lag metrics or names. Produces one compact section per finding_id.

2026-09-04

aws-health-events

Check AWS Health for service events, scheduled changes, and account notifications that may explain or correlate with an operational issue — filtered by service, time window, region, and status. Use when investigating service degradation, elevated error rates, latency spikes, connection failures, throttling, or capacity issues to determine whether an AWS-side event is a root cause or contributing factor, or when the user asks for an AWS Health summary/report over a time period. Read-only: it only describes Health events and their affected entities. Requires a Business / Enterprise / Enterprise On-Ramp support plan and queries the us-east-1 Health endpoint; data covers the last 90 days.

2026-08-04

Ver todas deste repositório

name	cost-spike-triage
name-en	Cost Spike Triage
name-zh	成本突增排查
description-en	Triage a sudden AWS bill spike to find the root cause — which service, usage type, region, and account/resource drove the change between two periods. Produces a ranked delta breakdown with the likely driver and next steps.
description-zh	排查 AWS 账单突然上涨的根因——定位是哪个服务、用量类型、区域，以及（可获取时）哪个账号或资源导致了两个周期之间的变化。产出按影响排序的差异明细、最可能的诱因与下一步建议。
description	Triage a sudden AWS cost increase or bill spike to find the root cause — which service, usage type, region, and (where available) which account or resource drove the change between two periods. Use when the user says their AWS bill went up, costs spiked, there's a cost anomaly, spend is higher than expected, or asks why this month costs more than last month. Produces a ranked breakdown of the delta with the most likely driver and next steps.