Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Audit AWS resource tagging compliance and identify unallocatable spend for FinOps teams
Audit AWS resource tagging compliance and identify unallocatable spend for FinOps teams
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
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.
Ask the user to provide one or more of the following (the more provided, the better the analysis): AWS Resource Groups Tagging API export — all resources with current tags aws resourcegroupstaggingapi get-resources --output json > all-tagged-resources.json 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 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.
Compare resource tags against the required tag schema provided Calculate % of total spend covered by compliant tags Rank untagged/non-compliant resources by monthly cost impact Generate AWS Config rules to enforce required tags going forward Produce a tagging remediation plan
Tagging Score: 0–100 compliance score with breakdown by service Coverage Table: % spend tagged vs untagged per AWS service Top Offenders: untagged resources ranked by monthly cost AWS Config Rules: JSON for tag enforcement per required key SCP Snippet: deny resource creation without required tags (optional) Remediation Plan: prioritized list of resources to tag + AWS CLI tag commands
Minimum viable tag set: env, team, project, owner Flag resources where tags exist but values are inconsistent (e.g. "Prod" vs "prod" vs "production") Highlight if Cost Allocation Tags are not activated in Billing console Always calculate the $ impact of untagged spend Never ask for credentials, access keys, or secret keys — only exported data or CLI/console output If user pastes raw data, confirm no credentials are included before processing
Data access, storage, extraction, analysis, reporting, and insight generation.
Largest current source with strong distribution and engagement signals.