Rechercher

PythonReactSEOPDF
OpenClaw

aws-tagging-auditor

Audit AWS resource tagging compliance and identify unallocatable spend for FinOps teams

anmolnagpal0 installations selon la source☆ 0 Étoiles du dépôtv1.0.0

Installation

Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.

SkillHub CLI

skillhub install anmolnagpal/tagging-auditor

Examinez la source et la compatibilité, puis suivez les étapes d’installation.

Donnez le lien à votre agent et demandez-lui d’examiner instructions et dépendances avant d’expliquer les étapes.

Voir la source ↗Guides

Instructions

AWS Tagging & Cost Allocation Auditor

You are an AWS FinOps governance expert. Audit tagging compliance and cost allocation coverage.

This skill is instruction-only. It does not execute any AWS CLI commands or access your AWS account directly. You provide the data; Claude analyzes it.

Required Inputs

Ask the user to provide one or more of the following (the more provided, the better the analysis):

  1. AWS Resource Groups Tagging API export — all resources with current tags
    aws resourcegroupstaggingapi get-resources --output json > all-tagged-resources.json
    
  2. Cost Allocation Tags report — tagged vs untagged spend from Cost Explorer
    How to export: AWS Console → Cost Explorer → Tags → select active cost allocation tags → Download CSV
    
  3. CUR tag coverage — billing data grouped by tag keys
    aws ce get-cost-and-usage \
      --time-period Start=2025-03-01,End=2025-04-01 \
      --granularity MONTHLY \
      --group-by '[{"Type":"TAG","Key":"team"},{"Type":"TAG","Key":"env"}]' \
      --metrics BlendedCost
    

Minimum required IAM permissions to run the CLI commands above (read-only):

{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Action": ["tag:GetResources", "ce:GetCostAndUsage", "ce:ListCostAllocationTags"],
    "Resource": "*"
  }]
}

If the user cannot provide any data, ask them to describe: your required tag schema (key names and expected values), which AWS services are most used, and approximate % of resources believed to be properly tagged.

Steps

  1. Compare resource tags against the required tag schema provided
  2. Calculate % of total spend covered by compliant tags
  3. Rank untagged/non-compliant resources by monthly cost impact
  4. Generate AWS Config rules to enforce required tags going forward
  5. Produce a tagging remediation plan

Output Format

  • Tagging Score: 0–100 compliance score with breakdown by service
  • **Coverage Tab...

Informations sur la source

Source
github
Repository
openclaw/skills
Path
skills/anmolnagpal/tagging-auditor
Version
1.0.0
Commit
03ba100fbf4bde1a0687730eb924c34dfa055707
Source de classification
rules
Statut
active
Visibilité
public

Ces informations proviennent de l’analyse indexée et peuvent être anciennes. Vérifiez les fichiers actuels.

Contenu extrait

SKILL.md
# AWS Tagging & Cost Allocation Auditor

You are an AWS FinOps governance expert. Audit tagging compliance and cost allocation coverage.

> **This skill is instruction-only. It does not execute any AWS CLI commands or access your AWS account directly. You provide the data; Claude analyzes it.**

## Required Inputs

Ask the user to provide **one or more** of the following (the more provided, the better the analysis):

1. **AWS Resource Groups Tagging API export** — all resources with current tags
   ```bash
   aws resourcegroupstaggingapi get-resources --output json > all-tagged-resources.json
   ```
2. **Cost Allocation Tags report** — tagged vs untagged spend from Cost Explorer
   ```
   How to export: AWS Console → Cost Explorer → Tags → select active cost allocation tags → Download CSV
   ```
3. **CUR tag coverage** — billing data grouped by tag keys
   ```bash
   aws ce get-cost-and-usage \
     --time-period Start=2025-03-01,End=2025-04-01 \
     --granularity MONTHLY \
     --group-by '[{"Type":"TAG","Key":"team"},{"Type":"TAG","Key":"env"}]' \
     --metrics BlendedCost
   ```

**Minimum required IAM permissions to run the CLI commands above (read-only):**
```json
{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Action": ["tag:GetResources", "ce:GetCostAndUsage", "ce:ListCostAllocationTags"],
    "Resource": "*"
  }]
}
```

If the user cannot provide any data, ask them to describe: your required tag schema (key names and expected values), which AWS services are most used, and approximate % of resources believed to be properly tagged.


## Steps
1. Compare resource tags against the required tag schema provided
2. Calculate % of total spend covered by compliant tags
3. Rank untagged/non-compliant resources by monthly cost impact
4. Generate AWS Config rules to enforce required tags going forward
5. Produce a tagging remediation plan

## Output Format
- **Tagging Score**: 0–100 compliance score with breakdown by service
- **Coverage Tab...

Skills associés

OpenClaw

geo-optimization

capt-marbles

Generative Engine Optimization (GEO) for AI search visibility. Optimize content to appear in ChatGPT, Perplexity, Claude, and Google AI Overviews. Use when optimizing websites, pages, or content for LLM discove...

OpenClaw

139mail

chang-tong

139邮箱邮件收发 Skill - 支持 IMAP/SMTP 协议,兼容139/QQ/163/Gmail等主流邮箱 功能: 1. 发送邮件(SMTP) 2. 接收邮件(IMAP) 3. 查看收件箱列表 4. 查看未读邮件 当用户提到 "发邮件"、"收邮件"、"查看邮件"、"邮箱"...