aws-cost-explorer
This skill should be used when users need to query AWS cost and usage details for a specific date. It supports querying costs at service level (e.g., EC2, S3, RDS) and drilling down to usage type level (e.g., instance types, storage classes, data transfer). Triggers on requests mentioning AWS costs, billing, spending, cost breakdown, or fee analysis.
What this skill does
# AWS Cost Explorer Query AWS costs and usage details with flexible granularity - from service-level overview to detailed usage type breakdown. ## Capabilities - Query daily AWS costs by service (e.g., EC2, S3, OpenSearch, DocumentDB) - Drill down to usage type details for specific services (e.g., instance types, storage, data transfer) - Filter results by minimum cost threshold - Support both relative dates (days ago) and absolute dates (YYYY-MM-DD) - Output in human-readable table or JSON format ## Usage ### Quick Commands To query costs, use the bundled script at `scripts/cost_query.py`: ```bash # Query costs from 2 days ago (default) by service python3 <skill-path>/scripts/cost_query.py # Query yesterday's costs, show items > $5 python3 <skill-path>/scripts/cost_query.py --days-ago 1 --min-cost 5 # Query specific date python3 <skill-path>/scripts/cost_query.py --date 2026-01-15 # Query specific service's usage breakdown python3 <skill-path>/scripts/cost_query.py --service "Amazon OpenSearch Service" --min-cost 1 # Query all services with usage type details python3 <skill-path>/scripts/cost_query.py --detailed --min-cost 5 # Output as JSON python3 <skill-path>/scripts/cost_query.py --json --min-cost 5 ``` ### Script Options | Option | Short | Description | |--------|-------|-------------| | `--days-ago` | `-d` | Query N days ago (default: 2, i.e., day before yesterday) | | `--date` | | Query specific date (YYYY-MM-DD format) | | `--min-cost` | `-m` | Minimum cost threshold to display (default: 0) | | `--service` | `-s` | Query usage type breakdown for a specific service | | `--detailed` | | Show all services with usage type breakdown | | `--json` | `-j` | Output in JSON format | ## Common Service Names When using `--service`, use the exact AWS service names: | Common Name | AWS Service Name | |-------------|------------------| | OpenSearch | `Amazon OpenSearch Service` | | DocumentDB/MongoDB | `Amazon DocumentDB (with MongoDB compatibility)` | | EC2 Compute | `Amazon Elastic Compute Cloud - Compute` | | EC2 Other (EBS, NAT) | `EC2 - Other` | | EFS | `Amazon Elastic File System` | | S3 | `Amazon Simple Storage Service` | | RDS | `Amazon Relational Database Service` | | EKS | `Amazon Elastic Container Service for Kubernetes` | | VPC | `Amazon Virtual Private Cloud` | | Bedrock | `Amazon Bedrock` | | Lambda | `AWS Lambda` | | CloudWatch | `AmazonCloudWatch` | ## Understanding Usage Types Common usage type patterns: | Pattern | Meaning | |---------|---------| | `BoxUsage:*` | EC2 instance hours (e.g., `BoxUsage:m7i.large`) | | `ESInstance:*` | OpenSearch instance hours | | `EBS:VolumeUsage.*` | EBS storage (e.g., `EBS:VolumeUsage.gp3`) | | `TimedStorage-ByteHrs` | S3/EFS storage capacity | | `DataTransfer-*` | Data transfer costs | | `NatGateway-*` | NAT Gateway costs | | `VpcEndpoint-*` | VPC Endpoint costs | | `*-input-tokens` / `*-output-tokens` | Bedrock token usage | | `Elastic*Usage` | DocumentDB Elastic costs | ## Prerequisites - AWS CLI configured with appropriate credentials - IAM permissions for `ce:GetCostAndUsage` ## Example Workflow 1. First, get service-level overview: ```bash python3 <skill-path>/scripts/cost_query.py --min-cost 5 ``` 2. Identify high-cost services, then drill down: ```bash python3 <skill-path>/scripts/cost_query.py --service "Amazon OpenSearch Service" --min-cost 1 ``` 3. For comprehensive analysis, use detailed mode: ```bash python3 <skill-path>/scripts/cost_query.py --detailed --min-cost 5 ```
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.