1.4K skills · sorted by relevance
Create and refine draw.io diagrams by editing XML files, adjusting labels, arrows, and spacing, and using AWS icons. Export transparent PNG images for slides, with guidance for readable Japanese text and consistent layouts.
Investigate cloud configuration weaknesses across AWS, GCP, and Azure, including public storage, exposed services, and leaked credentials. Find candidates in public information and JavaScript, then verify data access and permissions to establish practical impact.
Operate a live AWS workload with AWS DevOps Agent — incident investigation, root-cause analysis, and release-readiness review — for startups with no dedicated DevOps or SRE engineer. Use when a live AWS workload is misbehaving (production is down, 5xx errors, latency spike, timeouts, it broke after the last deploy, an alarm fired, a pasted CloudWatch alarm or stack trace, find the root cause, write a postmortem, no one on call), for pre-merge review (is this PR safe to ship, blast radius), or to set up, pause, stop, or check the cost of AWS DevOps Agent. Detects existing setup first and never re-onboards. Asks one explicit Yes/No covering cost (two-month trial, Activate credits) and account access before any setup; code egress stays off unless asked. Do not use for: new architecture (architect-for-startups), scaffolding (start-building-for-startups), migrations (gcp-to-aws, azure-to-aws, heroku-to-aws, llm-to-bedrock), or general Activate and credits questions (knowledge-base-for-startups).
The English summary is being prepared. Showing the original description.
Discover the user's local AWS context (active profile, region, account ID, caller identity) at the start of any AWS task. Use this skill before any other AWS work — deploying to SageMaker, creating resources, calling AWS APIs, or anything that touches an AWS account. Use it especially when the user has not specified a region or profile explicitly, when they say things like "use my AWS account", "deploy to AWS", "use my profile", or when about to make any AWS CLI or SDK call. Never guess the region or account ID — always use this skill to read it from the local configuration first.
The English summary is being prepared. Showing the original description.
Operate the ClawSweeper maintenance bot for OpenClaw issues and pull requests, which are proposed code changes. Read findings, create repair jobs, monitor GitHub Actions, and manage automatic fixes or merges subject to authorization and validation checks.
Deploy and operate AI agents with AWS Bedrock AgentCore. Choose services for hosting agents, connecting external APIs, managing credentials and conversation state, monitoring activity, and assessing agent quality through automated evaluations.
Build and deploy AWS Lambda functions without managing servers. Guidance covers APIs, scheduled jobs, event triggers, permissions, shared dependencies, and performance tuning, with code and command examples for deployment and troubleshooting.
Assess an AWS resource using CloudWatch logs and metrics, the measurements that describe its behavior. Investigate failures and performance issues, classify their severity, and produce a remediation report with staged actions, CLI commands, and monitoring recommendations.
Set up decoy credentials, storage, and secrets across AWS, Azure, and GCP to detect suspicious access. Connect audit logs to security alerts, verify detection, and document permissions, resource inventories, and maintenance plans.
Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.
Monitor daily AWS spending by service and account, compare it with historical baselines, and send Slack alerts with cost differences and likely causes. Known planned increases are excluded, and cloud resources remain unchanged.
Assess what exposed credentials can access in AWS, GCP, and Azure. Map permissions, test paths to higher privileges, and document demonstrated impact using benign test objects within an explicitly authorized assessment scope.
Interactive discovery + implementation workflow that gathers requirements through picker-based questions (intent, scope, constraints, preferences), scans the codebase for what it can already infer, then writes an AWS architectural scaffold and implementation directly into the project. Use when the user wants to build a new app, scaffold a project, or expand/refactor an existing one on AWS — anything that calls for a structured discovery flow followed by code changes, not a one-off lookup. Do not use for: factual lookups about AWS Activate / programs / credits, requests for a single copy-paste prompt, non-AWS architectural work, architecture advice/recommendations without code changes (see architect-for-startups), a new idea centered on an AI agent — runtime selection, agentic architecture, or an agent POC (see agent-advisor), or migrating an existing GCP/Azure/Heroku workload or an LLM SDK rewrite (see gcp-to-aws / azure-to-aws / heroku-to-aws / llm-to-bedrock).
The English summary is being prepared. Showing the original description.
Migrate workloads from Heroku to AWS. Triggers on: migrate from Heroku, Heroku to AWS, move off Heroku, migrate Heroku Postgres to RDS, migrate Heroku Redis to ElastiCache, migrate Heroku Kafka to MSK, migrate dynos to Elastic Beanstalk, migrate dynos to Fargate, migrate Heroku Private Space, Heroku to ECS, leave Heroku, what-if workshop, compare migration scenarios, workshop mode. Runs a 6-phase process: discover Heroku resources live via the authenticated Heroku CLI (read-only, consent-gated) and/or from Terraform, Procfile/app.json, and billing exports, then clarify, design, estimate costs, generate artifacts, and collect feedback. Clarify must finish before Design, Estimate, or Generate. An optional post-Estimate what-if workshop reprices region/HA/compute/Graviton scenarios. Do not use for: GCP migrations (see gcp-to-aws), Azure migrations (see azure-to-aws), AWS-to-Heroku reverse migration, general AWS architecture advice without migration intent, or Heroku-to-Heroku refactoring.
The English summary is being prepared. Showing the original description.
Guides building full-stack applications with AWS Blocks — an Infrastructure-from-Code framework. Applies when creating APIs, selecting Building Blocks (KVStore, DistributedTable, Database, AuthBasic, AuthCognito, Realtime, AsyncJob, FileBucket, etc.), running local development, or deploying AWS Blocks applications. Also covers AWS Blocks topics with validated, version-specific patterns that prevent common mistakes. Triggers when user mentions AWS Blocks; project has aws-blocks/ directory; code imports @aws-blocks packages.
The English summary is being prepared. Showing the original description.
SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework. Use when writing or editing sst.config.ts, building infra/ modules (sst.aws.Function/Bucket/Dynamo/Cron/Service/Router, sst.Secret, sst.Linkable, raw aws.* Pulumi resources), wiring resource links, scoping IAM, or running sst deploy/dev/diff/remove. Essential when the user mentions SST, sst.config.ts, $config, $transform, $interpolate, sst.aws.*, sst.Secret, Pulumi/Ion, "sst deploy", a failed SST deploy (ConflictException on a resource-type change, "Identifier '__filename' has already been declared", MalformedPolicyDocument on an Output<T>), or wants to scaffold/troubleshoot AWS infrastructure with SST. Also use when a request to "deploy my AWS stack" or "add a Lambda/bucket/table" is made in a repo that already contains an sst.config.ts (using $config) or an sst dependency. Do NOT use when the task is primarily AWS CDK, Terraform, raw CloudFormation, or SAM with no SST present — those have their own tooling.
The English summary is being prepared. Showing the original description.
Guide HyperFrames video projects from setup through layout checks, editable previews, and video output. Covers command-line workflows, environment troubleshooting, and distributed rendering on AWS Lambda, which splits video rendering work across cloud functions.
Identify unused AWS resources, estimate potential savings, and prepare cleanup scripts with preview steps. Covers storage retention policies and scheduled cleanup so teams can review dependencies before removing resources and track the resulting savings.
Deploy container applications on AWS using ECS and Fargate, which runs containers without managing servers. Covers image publishing, task configuration, load balancing, automatic scaling, deployment updates, and troubleshooting failed or unhealthy containers.
Provision and manage Amazon RDS relational databases on AWS. Follow guidance for backups, recovery, security, monitoring, multi-zone redundancy, and read replicas—database copies that handle read traffic—with AWS CLI commands and a Terraform configuration example.
Audit AWS, Azure, and GCP configurations against CIS Benchmarks, security configuration guidelines. Use automated scan results to identify failed checks, prioritize fixes, report compliance by area, and establish ongoing monitoring for configuration changes.
Analyze access logs from AWS S3, GCS, and Azure Blob Storage to spot unusual downloads, unfamiliar IP addresses, and request spikes. Compare activity with normal patterns and prioritize findings for suspected data theft investigations.
Build AWS applications with managed services that reduce server administration. Follow patterns for Lambda functions, HTTP APIs, database access, and queued background processing, with guidance on deployment and delays when functions first start.
Guide server-side Zoom integrations using Zoom Rivet SDK in JavaScript or TypeScript. Consult patterns for authentication, incoming event notifications, typed API calls, multiple modules, and webhook processing on AWS Lambda.