Tagging Auditor

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

This skill is instruction-only and coherent for tagging audits, but before using it: 1) Run the suggested AWS CLI/console exports locally under a least-privilege, read-only role (the policy shown is appropriate). 2) Carefully review any JSON/CSV you plan to paste into the chat — never include access keys, secret keys, or other credentials. 3) If you prefer, upload exports to a private location and share only the minimized data necessary for analysis (resource IDs, tags, and cost figures) rather than full raw files. 4) If you are unsure whether an export contains sensitive info, open it in a local editor and redact anything sensitive before sharing. Following these steps keeps your account credentials and high-sensitivity details safe while still allowing the skill to analyze tagging and spend coverage.

Type: OpenClaw Skill Name: tagging-auditor Version: 1.0.0 The skill bundle is benign. The `SKILL.md` explicitly states that it is 'instruction-only' and 'does not execute any AWS CLI commands or access your AWS account directly.' It also instructs the agent to 'Never ask for credentials, access keys, or secret keys.' While the agent has `bash` capabilities, these strong guardrails prevent its misuse for unauthorized AWS access or data exfiltration. The purpose of auditing AWS tagging compliance based on user-provided data is clearly aligned with the instructions, and there is no evidence of malicious intent or prompt injection attempts.