aws

Inspect AWS environments, services, and logs with read-only CLI commands.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/flesler/dotfiles --skill aws-flesler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws
Source: https://github.com/flesler/dotfiles/tree/main/home/.cursor/skills/aws
Command: npx skills add https://github.com/flesler/dotfiles --skill aws-flesler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a safe, read-only interface to AWS resources, enabling status checks, log access, and resource discovery without risk of making changes.

Core Features & Use Cases

  • Read-only AWS CLI commands for inspecting environments, services, and logs.
  • Profile-aware operation using AWS_PROFILE with optional on-demand inference for dynamic context.
  • Use Case: Troubleshooting outages by quickly listing instances, checking statuses, and retrieving logs without modifying resources.

Quick Start

Check the status of AWS resources in the current profile without making changes.

Frequently Asked Questions about aws

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check AWS resource status and logs without making changes?

You can check AWS resource status and logs safely using read-only AWS CLI commands. This Skill provides non-destructive workflows to inspect environments, services, and retrieve logs without modifying resources.

How does read-only AWS CLI access work for troubleshooting infrastructure?

Read-only AWS CLI access works by executing status checks and log retrieval commands against your environments. It targets resource discovery and log access across accounts without the risk of making changes.

Can I inspect resources across multiple AWS accounts using AWS_PROFILE?

Yes, you can inspect resources across multiple AWS accounts using the AWS_PROFILE environment variable. This Skill supports profile-aware operation with optional on-demand inference for dynamic context.

What is the best way to retrieve CloudWatch logs safely via AWS CLI?

The best way to retrieve CloudWatch logs safely is using a read-only Skill that limits AWS CLI commands to inspection and log access. It ensures non-destructive workflows while querying logs.

What output formats are supported when inspecting AWS infrastructure via CLI?

AWS CLI outputs are supported in table, text, and json formats when inspecting AWS infrastructure. This allows flexible parsing and reading of resource statuses and log data.

Why should I use a read-only approach for AWS debugging and log access?

You should use a read-only approach for AWS debugging to ensure safe, non-destructive workflows. It prevents accidental modifications to infrastructure while allowing full resource discovery and log retrieval.