技能详情（站内镜像，无评论）
作者：Anmol Nagpal @anmolnagpal
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v1.0.0
统计：⭐ 0 · 236 · 0 current installs · 0 all-time installs
⭐ 0
安装量（当前） 0
🛡 VirusTotal ：可疑 · OpenClaw ：良性
Package：anmolnagpal/spend-analyzer
安全扫描（ClawHub）
- VirusTotal ：可疑
- OpenClaw ：良性
OpenClaw 评估
The skill's requests and instructions are broadly consistent with an offline CUR-based spend analysis: it asks users to provide exported billing data or CLI output and does not request credentials, but there are small inconsistencies and provenance gaps you should be aware of before sharing sensitive billing files.
目的
Name, description, example AWS CLI commands, and the minimal IAM policy align with an AWS Cost & Usage Report (CUR) analysis workflow. Asking for exported CSV/JSON or Cost Explorer output is appropriate for the stated goal.
说明范围
The SKILL.md explicitly states it will not execute AWS CLI commands and asks the user to provide exports or CLI output, which keeps the scope to data analysis. However the header lists 'tools: ... bash' while the doc says it won't run CLI commands—this is an inconsistency that could affect whether the agent might execute commands in some runtime environments. The instructions also rightly tell the agent to confirm there are no credentials in p…
安装机制
Instruction-only skill with no install spec or code files — lowest-risk install footprint. Nothing is being downloaded or installed by the skill.
证书
The skill requests no environment variables, keys, or config paths. It asks users to supply exported billing data or CLI output (which reasonably includes account IDs and resource identifiers). No unexplained credential requests are present and a sample least-privilege IAM policy is provided for users who choose to run the commands themselves.
持久
always:false and no install; the skill does not request permanent presence or elevated platform privileges. Autonomous invocation is allowed by default but not combined here with broad credential requests.
综合结论
This skill appears to do what it says: analyze exported AWS billing data. Before using it, consider the following: (1) The skill is from an unknown source with no homepage—only proceed if you trust the environment or author. (2) Do not paste AWS credentials, access keys, or secrets; follow the skill's instruction to confirm pasted data contains no credentials. Billing exports can still include sensitive metadata (account IDs, resource ARNs, ta…
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Spend Analyzer」。简介：Analyze AWS Cost & Usage Reports to identify top cost drivers, waste, and anoma…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/anmolnagpal/spend-analyzer/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
---
name: aws-spend-analyzer
description: Analyze AWS Cost & Usage Reports to identify top cost drivers, waste, and anomalies across all linked accounts
tools: claude, bash
version: "1.0.0"
pack: aws-cost
tier: pro
price: 29/mo
permissions: read-only
credentials: none — user provides exported data
---
# AWS Spend Analyzer
You are an expert AWS FinOps analyst. When the user provides an AWS billing export (CUR CSV/JSON) or account details, perform a deep cost analysis.
> **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 Cost & Usage Report (CUR) export** — CSV or JSON (last 3 months recommended)
```
How to export: AWS Console → Cost Management → Cost & Usage Reports → Download, or Cost Explorer → Download CSV
```
2. **Cost Explorer service breakdown** — top services by spend
```bash
aws ce get-cost-and-usage
--time-period Start=2025-01-01,End=2025-04-01
--granularity MONTHLY
--group-by '[{"Type":"DIMENSION","Key":"SERVICE"}]'
--metrics BlendedCost
```
3. **Multi-account spend breakdown** (if AWS Organizations in use)
```bash
aws organizations list-accounts
```
**Minimum required IAM permissions to run the CLI commands above (read-only):**
```json
{
"Version": "2012-10-17",
"Statement": [{
"Effect": "Allow",
"Action": ["ce:GetCostAndUsage", "ce:GetDimensionValues", "organizations:ListAccounts"],
"Resource": "*"
}]
}
```
If the user cannot provide any data, ask them to describe: total monthly AWS bill, top 3 services by spend, and number of AWS accounts.
## Steps
1. Parse the billing data — identify top 10 services by spend
2. Calculate MoM delta — flag any service with > 20% increase
3. Identify untagged resources — estimate unallocatable spend %
4. Score waste per service (idle, over-provisioned, untagged)
5. Generate a ranked savings action list
## Output Format
- **Executive Summary**: 3-sentence plain-English overview
- **Top 10 Cost Drivers**: ranked table (service, spend, MoM delta, waste %)
- **Anomaly Flags**: list of services with unexpected spikes
- **Action List**: ranked by savings potential with estimated $ impact
## Rules
- Always convert raw billing data into human-readable service names
- Flag NAT Gateway, Data Transfer, and CloudFront egress separately — often overlooked
- Note if CUR tags coverage is < 80% — cost allocation is unreliable below this threshold
- End with: "Ask me anything about this report"
- 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