aws-tagging-auditor

What This Skill Does

The AWS Tagging & Cost Allocation Auditor is a specialized governance tool designed to bring clarity and control to your cloud financial operations (FinOps). Many organizations struggle with 'cloud sprawl'—where infrastructure costs balloon due to lack of visibility. This skill acts as an expert consultant that parses your exported AWS billing and resource data to audit tagging compliance. It identifies exactly which resources are contributing to unallocatable spend, ranks them by cost impact, and generates actionable remediation plans including precise AWS CLI commands to fix tagging gaps.

Installation

To integrate this skill into your environment, run the following command via your terminal or management interface: clawhub install openclaw/skills/skills/anmolnagpal/tagging-auditor

Use Cases

1. Monthly FinOps Audits: Regularly process Cost Explorer exports to ensure new resources follow the organization's tag schema (e.g., env, team, project, owner).
2. Cost Allocation Cleanup: Pinpoint resources that lack specific cost allocation tags, preventing them from appearing in billing reports.
3. Compliance Enforcement: Generate standardized AWS Config rules and Service Control Policies (SCPs) to proactively block the creation of non-compliant resources.
4. Data Normalization: Detect inconsistent naming conventions (e.g., 'Production' vs 'prod') that skew financial reporting.

Example Prompts

1. "I've uploaded my Cost Explorer CSV export. Please calculate the current tagging compliance score and identify the top 5 services that are driving the most untagged spend."
2. "Here is my all-tagged-resources.json file. Based on a required schema of 'team', 'env', and 'owner', generate a bash script to tag the missing resources for me."
3. "Our tagging strategy is inconsistent. Can you provide an SCP snippet that denies the creation of any EC2 instances or RDS databases if they don't have the 'project' tag attached?"

Tips & Limitations

• Data Privacy: This skill never requests your AWS credentials. It is strictly instruction-based; you provide the data, and it analyzes it. Always scrub sensitive identifiers from logs before sharing.
• Depth of Analysis: The accuracy of the analysis is directly proportional to the data provided. Providing both resource metadata and cost usage data yields the most accurate dollar-value impact analysis.
• Configuration: Always ensure your active cost allocation tags are toggled 'On' in the AWS Billing console, as this skill cannot retroactively enable features in your account.