Stop permissions and credential errors from killing cloud assessments
Prowler scans fail or produce noisy logs because of missing read-only permissions, expired session tokens, or credentials not mounted into containers. This recipe standardizes authentication, documents required policies, and provides a repeatable triage flow for AccessDenied and InvalidClientTokenId.
Create a skill called "Prowler AWS Scan Doctor". Inputs I will provide: - How I'm authenticating (profile keys / SSO / assume role) - Any error logs (AccessDenied, InvalidClientTokenId, NoCredentialsError) - Targeted AWS services (if the engagement is scoped) Task: 1) Produce a minimal, scoped Prowler command that should work with my auth method. 2) If errors occur, classify them into: credential invalid/expired, missing allow, explicit deny (SCP/boundary), or container credential visibility. 3) Provide next-step commands to prove which case it is (aws sts get-caller-identity, policy simulator pointers, etc.). 4) Output should include a "run manifest" template for my engagement notes.
Common symptoms:
`aws configure list`
`aws sts get-caller-identity`
`prowler aws --services iam,s3,ec2 --output-formats json csv`
`docker run --rm -it -v "$HOME/.aws:/root/.aws:ro" prowler/prowler aws --output-formats json`
Preflight connectivity, reduce false positives, handle AV flags
PingCastle AD assessments commonly fail or mislead due to DNS/DC discovery issues, missing SMB connectivity for GPO retrieval, absent ADWS (slow scans), and AV/EDR false positives. This runbook makes those failure modes explicit and gives a repeatable preflight-to-report workflow.
Find the $15K/month in orphaned resources nobody knows about
Hunts through your cloud accounts for wasted spend — orphaned EBS volumes, idle load balancers, oversized instances, forgotten snapshots, unused Elastic IPs. Generates a cleanup report with estimated savings and the commands to fix each one.
A playbook for "stops at the same frame" and "freeze mid-render" failures
Renders freeze at a consistent percentage or frame — often caused by a bad clip, a heavy effect, a Fusion comp issue, or "stop render on error" settings. This recipe classifies the failure pattern and gives you a structured triage plan instead of blind re-exports.
Fix a common Premiere playback-lag issue caused by audio input device settings
Severe playback lag and stutter in Premiere Pro that looks like a codec performance problem but is actually caused by audio hardware input settings. This recipe provides a quick decision tree to test and fix the issue — often resolved in under a minute by switching the default input to "No Input."