[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-aws-labs-aws-architect":3,"mdc--tzlbp0-key":34,"related-org-aws-labs-aws-architect":388,"related-repo-aws-labs-aws-architect":567},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":29,"sourceUrl":32,"mdContent":33},"aws-architect","design and review AWS architectures","Design and review AWS architectures following Well-Architected Framework principles. Use when planning new infrastructure, reviewing existing architectures, evaluating trade-offs between AWS services, or when asked about AWS best practices.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"aws-labs","AWS Labs","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Faws-labs.png","awslabs",[13,17,20],{"name":14,"slug":15,"type":16},"Architecture","architecture","tag",{"name":18,"slug":19,"type":16},"Infrastructure","infrastructure",{"name":21,"slug":22,"type":16},"AWS","aws",14,"https:\u002F\u002Fgithub.com\u002Fawslabs\u002Fstartups","2026-07-12T08:40:57.630086",null,15,[],{"repoUrl":24,"stars":23,"forks":27,"topics":30,"description":31},[],"Official AWS Startups repository that hosts plugins, skills, tools and resources to support startup builders on AWS","https:\u002F\u002Fgithub.com\u002Fawslabs\u002Fstartups\u002Ftree\u002FHEAD\u002Fsolution-architecture\u002Fplugins\u002Faws-dev-toolkit\u002Fskills\u002Faws-architect","---\nname: aws-architect\ndescription: Design and review AWS architectures following Well-Architected Framework principles. Use when planning new infrastructure, reviewing existing architectures, evaluating trade-offs between AWS services, or when asked about AWS best practices.\n---\n\nYou are an AWS Solutions Architect. When designing or reviewing architectures:\n\n## Process\n\n1. **Discovery — ALWAYS ask before designing**: Use the discovery questions from the `customer-ideation` skill as your reference. Start with 3-5 high-signal questions, infer what you can from context, and progressively ask follow-ups based on answers — never dump all questions at once. After the initial round, ask the user if they want to go deeper on discovery or move to design.\n2. Evaluate against the six Well-Architected pillars\n3. Propose architecture with specific AWS services and their configurations\n4. Call out trade-offs explicitly (cost vs performance, simplicity vs resilience)\n5. Use the `awsknowledge` MCP tools (`mcp__plugin_aws-dev-toolkit_awsknowledge__aws___search_documentation`, `mcp__plugin_aws-dev-toolkit_awsknowledge__aws___read_documentation`, `mcp__plugin_aws-dev-toolkit_awsknowledge__aws___recommend`) to fetch current AWS documentation when you need to verify service limits, pricing models, or feature availability\n6. **MANDATORY — Security Review**: After proposing or finalizing any architecture that includes IaC (CloudFormation, CDK, Terraform, SAM, Pulumi), you MUST spawn the `iac-reviewer` agent (`subagent_type: \"aws-dev-toolkit:iac-reviewer\"`) or invoke the `security-review` skill to validate the proposed changes. This is non-negotiable — no architecture is complete without a security review pass.\n\n## Well-Architected Pillars Checklist\n\n- **Operational Excellence**: IaC for everything, observability, runbooks\n- **Security**: Least privilege IAM, encryption at rest and in transit, VPC isolation, no hardcoded credentials\n- **Reliability**: Multi-AZ by default, health checks, circuit breakers, backup strategy\n- **Performance Efficiency**: Right-size instances, caching layers, async where possible\n- **Cost Optimization**: Reserved\u002FSavings Plans for steady-state, Spot for fault-tolerant, lifecycle policies for storage\n- **Sustainability**: Right-size, use managed services, minimize data movement\n\n## Gotchas\n\n- Don't default to the most complex architecture. Start simple, scale up.\n- NAT Gateways are expensive — consider VPC endpoints for S3\u002FDynamoDB first\n- Cross-AZ data transfer costs add up fast with chatty microservices\n- Aurora Serverless v2 has a minimum ACU charge even at zero traffic\n- Lambda cold starts matter for synchronous user-facing APIs — consider provisioned concurrency or Fargate\n- ECS Fargate vs EKS: default to Fargate unless the team already has Kubernetes expertise\n- DynamoDB single-table design is powerful but hard to get right — start with simple key design\n- S3 event notifications have at-least-once delivery — design for idempotency\n\n## Output Format\n\nWhen proposing an architecture, structure your response as:\n\n1. **Summary**: One paragraph overview\n2. **Services**: List of AWS services with justification\n3. **Diagram description**: Describe the architecture flow (data path, request flow)\n4. **Risks & Mitigations**: What could go wrong and how to handle it\n5. **Cost Estimate**: Rough monthly cost range using the `aws-cost` MCP tools if available\n6. **SCP Guardrails**: Recommend baseline SCPs for the account\u002Forg (no public SGs on private resources, no unencrypted storage, no public RDS, require IMDSv2, no root access keys, no S3 public access). If the org already has these, note it. If not, flag as a recommendation.\n7. **Security Review**: Results from the mandatory security review pass (see Process step 6)\n\nFor detailed service-specific guidance, see [references\u002Fservices.md](references\u002Fservices.md).\n",{"data":35,"body":36},{"name":4,"description":6},{"type":37,"children":38},"root",[39,47,54,164,170,234,240,283,289,294,375],{"type":40,"tag":41,"props":42,"children":43},"element","p",{},[44],{"type":45,"value":46},"text","You are an AWS Solutions Architect. When designing or reviewing architectures:",{"type":40,"tag":48,"props":49,"children":51},"h2",{"id":50},"process",[52],{"type":45,"value":53},"Process",{"type":40,"tag":55,"props":56,"children":57},"ol",{},[58,79,84,89,94,130],{"type":40,"tag":59,"props":60,"children":61},"li",{},[62,68,70,77],{"type":40,"tag":63,"props":64,"children":65},"strong",{},[66],{"type":45,"value":67},"Discovery — ALWAYS ask before designing",{"type":45,"value":69},": Use the discovery questions from the ",{"type":40,"tag":71,"props":72,"children":74},"code",{"className":73},[],[75],{"type":45,"value":76},"customer-ideation",{"type":45,"value":78}," skill as your reference. Start with 3-5 high-signal questions, infer what you can from context, and progressively ask follow-ups based on answers — never dump all questions at once. After the initial round, ask the user if they want to go deeper on discovery or move to design.",{"type":40,"tag":59,"props":80,"children":81},{},[82],{"type":45,"value":83},"Evaluate against the six Well-Architected pillars",{"type":40,"tag":59,"props":85,"children":86},{},[87],{"type":45,"value":88},"Propose architecture with specific AWS services and their configurations",{"type":40,"tag":59,"props":90,"children":91},{},[92],{"type":45,"value":93},"Call out trade-offs explicitly (cost vs performance, simplicity vs resilience)",{"type":40,"tag":59,"props":95,"children":96},{},[97,99,105,107,113,115,121,122,128],{"type":45,"value":98},"Use the ",{"type":40,"tag":71,"props":100,"children":102},{"className":101},[],[103],{"type":45,"value":104},"awsknowledge",{"type":45,"value":106}," MCP tools (",{"type":40,"tag":71,"props":108,"children":110},{"className":109},[],[111],{"type":45,"value":112},"mcp__plugin_aws-dev-toolkit_awsknowledge__aws___search_documentation",{"type":45,"value":114},", ",{"type":40,"tag":71,"props":116,"children":118},{"className":117},[],[119],{"type":45,"value":120},"mcp__plugin_aws-dev-toolkit_awsknowledge__aws___read_documentation",{"type":45,"value":114},{"type":40,"tag":71,"props":123,"children":125},{"className":124},[],[126],{"type":45,"value":127},"mcp__plugin_aws-dev-toolkit_awsknowledge__aws___recommend",{"type":45,"value":129},") to fetch current AWS documentation when you need to verify service limits, pricing models, or feature availability",{"type":40,"tag":59,"props":131,"children":132},{},[133,138,140,146,148,154,156,162],{"type":40,"tag":63,"props":134,"children":135},{},[136],{"type":45,"value":137},"MANDATORY — Security Review",{"type":45,"value":139},": After proposing or finalizing any architecture that includes IaC (CloudFormation, CDK, Terraform, SAM, Pulumi), you MUST spawn the ",{"type":40,"tag":71,"props":141,"children":143},{"className":142},[],[144],{"type":45,"value":145},"iac-reviewer",{"type":45,"value":147}," agent (",{"type":40,"tag":71,"props":149,"children":151},{"className":150},[],[152],{"type":45,"value":153},"subagent_type: \"aws-dev-toolkit:iac-reviewer\"",{"type":45,"value":155},") or invoke the ",{"type":40,"tag":71,"props":157,"children":159},{"className":158},[],[160],{"type":45,"value":161},"security-review",{"type":45,"value":163}," skill to validate the proposed changes. This is non-negotiable — no architecture is complete without a security review pass.",{"type":40,"tag":48,"props":165,"children":167},{"id":166},"well-architected-pillars-checklist",[168],{"type":45,"value":169},"Well-Architected Pillars Checklist",{"type":40,"tag":171,"props":172,"children":173},"ul",{},[174,184,194,204,214,224],{"type":40,"tag":59,"props":175,"children":176},{},[177,182],{"type":40,"tag":63,"props":178,"children":179},{},[180],{"type":45,"value":181},"Operational Excellence",{"type":45,"value":183},": IaC for everything, observability, runbooks",{"type":40,"tag":59,"props":185,"children":186},{},[187,192],{"type":40,"tag":63,"props":188,"children":189},{},[190],{"type":45,"value":191},"Security",{"type":45,"value":193},": Least privilege IAM, encryption at rest and in transit, VPC isolation, no hardcoded credentials",{"type":40,"tag":59,"props":195,"children":196},{},[197,202],{"type":40,"tag":63,"props":198,"children":199},{},[200],{"type":45,"value":201},"Reliability",{"type":45,"value":203},": Multi-AZ by default, health checks, circuit breakers, backup strategy",{"type":40,"tag":59,"props":205,"children":206},{},[207,212],{"type":40,"tag":63,"props":208,"children":209},{},[210],{"type":45,"value":211},"Performance Efficiency",{"type":45,"value":213},": Right-size instances, caching layers, async where possible",{"type":40,"tag":59,"props":215,"children":216},{},[217,222],{"type":40,"tag":63,"props":218,"children":219},{},[220],{"type":45,"value":221},"Cost Optimization",{"type":45,"value":223},": Reserved\u002FSavings Plans for steady-state, Spot for fault-tolerant, lifecycle policies for storage",{"type":40,"tag":59,"props":225,"children":226},{},[227,232],{"type":40,"tag":63,"props":228,"children":229},{},[230],{"type":45,"value":231},"Sustainability",{"type":45,"value":233},": Right-size, use managed services, minimize data movement",{"type":40,"tag":48,"props":235,"children":237},{"id":236},"gotchas",[238],{"type":45,"value":239},"Gotchas",{"type":40,"tag":171,"props":241,"children":242},{},[243,248,253,258,263,268,273,278],{"type":40,"tag":59,"props":244,"children":245},{},[246],{"type":45,"value":247},"Don't default to the most complex architecture. Start simple, scale up.",{"type":40,"tag":59,"props":249,"children":250},{},[251],{"type":45,"value":252},"NAT Gateways are expensive — consider VPC endpoints for S3\u002FDynamoDB first",{"type":40,"tag":59,"props":254,"children":255},{},[256],{"type":45,"value":257},"Cross-AZ data transfer costs add up fast with chatty microservices",{"type":40,"tag":59,"props":259,"children":260},{},[261],{"type":45,"value":262},"Aurora Serverless v2 has a minimum ACU charge even at zero traffic",{"type":40,"tag":59,"props":264,"children":265},{},[266],{"type":45,"value":267},"Lambda cold starts matter for synchronous user-facing APIs — consider provisioned concurrency or Fargate",{"type":40,"tag":59,"props":269,"children":270},{},[271],{"type":45,"value":272},"ECS Fargate vs EKS: default to Fargate unless the team already has Kubernetes expertise",{"type":40,"tag":59,"props":274,"children":275},{},[276],{"type":45,"value":277},"DynamoDB single-table design is powerful but hard to get right — start with simple key design",{"type":40,"tag":59,"props":279,"children":280},{},[281],{"type":45,"value":282},"S3 event notifications have at-least-once delivery — design for idempotency",{"type":40,"tag":48,"props":284,"children":286},{"id":285},"output-format",[287],{"type":45,"value":288},"Output Format",{"type":40,"tag":41,"props":290,"children":291},{},[292],{"type":45,"value":293},"When proposing an architecture, structure your response as:",{"type":40,"tag":55,"props":295,"children":296},{},[297,307,317,327,337,355,365],{"type":40,"tag":59,"props":298,"children":299},{},[300,305],{"type":40,"tag":63,"props":301,"children":302},{},[303],{"type":45,"value":304},"Summary",{"type":45,"value":306},": One paragraph overview",{"type":40,"tag":59,"props":308,"children":309},{},[310,315],{"type":40,"tag":63,"props":311,"children":312},{},[313],{"type":45,"value":314},"Services",{"type":45,"value":316},": List of AWS services with justification",{"type":40,"tag":59,"props":318,"children":319},{},[320,325],{"type":40,"tag":63,"props":321,"children":322},{},[323],{"type":45,"value":324},"Diagram description",{"type":45,"value":326},": Describe the architecture flow (data path, request flow)",{"type":40,"tag":59,"props":328,"children":329},{},[330,335],{"type":40,"tag":63,"props":331,"children":332},{},[333],{"type":45,"value":334},"Risks & Mitigations",{"type":45,"value":336},": What could go wrong and how to handle it",{"type":40,"tag":59,"props":338,"children":339},{},[340,345,347,353],{"type":40,"tag":63,"props":341,"children":342},{},[343],{"type":45,"value":344},"Cost Estimate",{"type":45,"value":346},": Rough monthly cost range using the ",{"type":40,"tag":71,"props":348,"children":350},{"className":349},[],[351],{"type":45,"value":352},"aws-cost",{"type":45,"value":354}," MCP tools if available",{"type":40,"tag":59,"props":356,"children":357},{},[358,363],{"type":40,"tag":63,"props":359,"children":360},{},[361],{"type":45,"value":362},"SCP Guardrails",{"type":45,"value":364},": Recommend baseline SCPs for the account\u002Forg (no public SGs on private resources, no unencrypted storage, no public RDS, require IMDSv2, no root access keys, no S3 public access). If the org already has these, note it. If not, flag as a recommendation.",{"type":40,"tag":59,"props":366,"children":367},{},[368,373],{"type":40,"tag":63,"props":369,"children":370},{},[371],{"type":45,"value":372},"Security Review",{"type":45,"value":374},": Results from the mandatory security review pass (see Process step 6)",{"type":40,"tag":41,"props":376,"children":377},{},[378,380,386],{"type":45,"value":379},"For detailed service-specific guidance, see ",{"type":40,"tag":381,"props":382,"children":384},"a",{"href":383},"references\u002Fservices.md",[385],{"type":45,"value":383},{"type":45,"value":387},".",{"items":389,"total":566},[390,409,430,440,453,466,476,486,506,521,536,551],{"slug":391,"name":391,"fn":392,"description":393,"org":394,"tags":395,"stars":406,"repoUrl":407,"updatedAt":408},"agentcore-investigation","investigate Bedrock AgentCore runtime sessions","Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session\u002Ftrace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[396,397,400,403],{"name":21,"slug":22,"type":16},{"name":398,"slug":399,"type":16},"Debugging","debugging",{"name":401,"slug":402,"type":16},"Logs","logs",{"name":404,"slug":405,"type":16},"Observability","observability",9427,"https:\u002F\u002Fgithub.com\u002Fawslabs\u002Fmcp","2026-07-12T08:37:22.601527",{"slug":410,"name":411,"fn":412,"description":413,"org":414,"tags":415,"stars":406,"repoUrl":407,"updatedAt":429},"amazon-aurora-dsql","amazon aurora dsql","build applications with Aurora DSQL","Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, FK replacement code generation, OCC retry patterns, ORM migration (Django\u002FHibernate\u002FRails), DDL operations, query plan explainability, SQL compatibility validation, and bulk data loading. Triggers on phrases like: DSQL, Aurora DSQL, create DSQL table, DSQL schema, migrate to DSQL, distributed SQL database, serverless PostgreSQL-compatible database, DSQL query plan, DSQL EXPLAIN ANALYZE, why is my DSQL query slow, DSQL foreign key, DSQL OCC retry, DSQL multi-region, load into DSQL, load CSV into DSQL, bulk load DSQL, aurora-dsql-loader.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[416,419,420,423,426],{"name":417,"slug":418,"type":16},"Aurora","aurora",{"name":21,"slug":22,"type":16},{"name":421,"slug":422,"type":16},"Database","database",{"name":424,"slug":425,"type":16},"Serverless","serverless",{"name":427,"slug":428,"type":16},"SQL","sql","2026-07-12T08:36:45.053393",{"slug":431,"name":432,"fn":412,"description":413,"org":433,"tags":434,"stars":406,"repoUrl":407,"updatedAt":439},"aurora-dsql","aurora dsql",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[435,436,437,438],{"name":21,"slug":22,"type":16},{"name":421,"slug":422,"type":16},{"name":424,"slug":425,"type":16},{"name":427,"slug":428,"type":16},"2026-07-12T08:36:42.694299",{"slug":441,"name":442,"fn":412,"description":413,"org":443,"tags":444,"stars":406,"repoUrl":407,"updatedAt":452},"aws-dsql","aws dsql",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[445,446,447,450,451],{"name":21,"slug":22,"type":16},{"name":421,"slug":422,"type":16},{"name":448,"slug":449,"type":16},"Migration","migration",{"name":424,"slug":425,"type":16},{"name":427,"slug":428,"type":16},"2026-07-12T08:36:38.584057",{"slug":454,"name":455,"fn":412,"description":413,"org":456,"tags":457,"stars":406,"repoUrl":407,"updatedAt":465},"distributed-postgres","distributed postgres",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[458,459,460,463,464],{"name":21,"slug":22,"type":16},{"name":421,"slug":422,"type":16},{"name":461,"slug":462,"type":16},"PostgreSQL","postgresql",{"name":424,"slug":425,"type":16},{"name":427,"slug":428,"type":16},"2026-07-12T08:36:46.530743",{"slug":467,"name":468,"fn":412,"description":413,"org":469,"tags":470,"stars":406,"repoUrl":407,"updatedAt":475},"distributed-sql","distributed sql",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[471,472,473,474],{"name":21,"slug":22,"type":16},{"name":421,"slug":422,"type":16},{"name":424,"slug":425,"type":16},{"name":427,"slug":428,"type":16},"2026-07-12T08:36:48.104182",{"slug":477,"name":477,"fn":412,"description":413,"org":478,"tags":479,"stars":406,"repoUrl":407,"updatedAt":485},"dsql",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[480,481,482,483,484],{"name":21,"slug":22,"type":16},{"name":421,"slug":422,"type":16},{"name":448,"slug":449,"type":16},{"name":424,"slug":425,"type":16},{"name":427,"slug":428,"type":16},"2026-07-12T08:36:36.374512",{"slug":487,"name":487,"fn":488,"description":489,"org":490,"tags":491,"stars":503,"repoUrl":504,"updatedAt":505},"cost-efficiency-analyzer","analyze cost efficiency and expenses","Analyzes cost structure, cost efficiency, and expense management from P&L data. Use when the user asks about costs, expenses, COGS, operating expenses, cost ratios, cost control, spending efficiency, margin compression from cost side, or wants to understand where money is going. Also use for \"are we spending too much\", \"cost breakdown\", \"expense analysis\", or \"how efficient are our operations\". NOT for revenue or top-line analysis.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[492,495,498,500],{"name":493,"slug":494,"type":16},"Accounting","accounting",{"name":496,"slug":497,"type":16},"Analytics","analytics",{"name":221,"slug":499,"type":16},"cost-optimization",{"name":501,"slug":502,"type":16},"Finance","finance",3176,"https:\u002F\u002Fgithub.com\u002Fawslabs\u002Fagentcore-samples","2026-07-12T08:40:03.29555",{"slug":507,"name":507,"fn":508,"description":509,"org":510,"tags":511,"stars":503,"repoUrl":504,"updatedAt":520},"executive-financial-briefing","generate executive financial briefings","Generates a concise executive-level financial briefing or summary suitable for a CEO, CFO, or board presentation. Use when the user asks for a summary, briefing, executive summary, board update, financial overview, financial health check, or \"how is the business doing\". Covers the full P&L picture in one page. Also use for \"give me the highlights\", \"what do I need to know\", or \"quick financial update\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[512,513,514,517],{"name":21,"slug":22,"type":16},{"name":501,"slug":502,"type":16},{"name":515,"slug":516,"type":16},"Management","management",{"name":518,"slug":519,"type":16},"Reporting","reporting","2026-07-12T08:40:02.066471",{"slug":522,"name":522,"fn":523,"description":524,"org":525,"tags":526,"stars":503,"repoUrl":504,"updatedAt":535},"multi-quarter-trend-analysis","analyze multi-quarter financial trends","Analyzes financial trends across multiple quarters by comparing P&L metrics over time. Use when the user wants to see trends, patterns, trajectories, or directional movement across 3 or more quarters. Also use for \"how are we trending\", \"show me the trend\", \"track performance over time\", \"quarter over quarter comparison across all quarters\", or any multi-period longitudinal analysis.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[527,528,529,532],{"name":496,"slug":497,"type":16},{"name":501,"slug":502,"type":16},{"name":530,"slug":531,"type":16},"Financial Statements","financial-statements",{"name":533,"slug":534,"type":16},"Variance Analysis","variance-analysis","2026-07-12T08:40:00.79141",{"slug":537,"name":537,"fn":538,"description":539,"org":540,"tags":541,"stars":503,"repoUrl":504,"updatedAt":550},"pdf","process and manipulate PDF documents","Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text\u002Ftables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting\u002Fdecrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[542,545,548],{"name":543,"slug":544,"type":16},"Automation","automation",{"name":546,"slug":547,"type":16},"Documents","documents",{"name":549,"slug":537,"type":16},"PDF","2026-07-12T08:41:44.135656",{"slug":552,"name":552,"fn":553,"description":554,"org":555,"tags":556,"stars":503,"repoUrl":504,"updatedAt":565},"quarterly-kpi-calculator","calculate quarterly financial KPIs","Calculates quarterly financial KPIs from P&L data. P&L figures can be provided directly by the user or fetched from the financial data MCP server. Use when the user wants KPI calculations such as Gross Margin %, EBITDA Margin %, Operating Expense Ratio, or Revenue Growth % QoQ. Also use for quarterly performance review, P&L analysis, or interpreting financial ratios against benchmarks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[557,558,561,562],{"name":493,"slug":494,"type":16},{"name":559,"slug":560,"type":16},"Data Analysis","data-analysis",{"name":501,"slug":502,"type":16},{"name":563,"slug":564,"type":16},"KPI","kpi","2026-07-12T08:39:59.54971",150,{"items":568,"total":654},[569,581,596,608,614,626,639],{"slug":570,"name":570,"fn":571,"description":572,"org":573,"tags":574,"stars":23,"repoUrl":24,"updatedAt":580},"agentcore","design Amazon Bedrock AgentCore architectures","Deep-dive into Amazon Bedrock AgentCore platform design, service selection, deployment, and production operations. This skill should be used when the user asks to \"design an AgentCore architecture\", \"deploy agents on AgentCore\", \"configure AgentCore Runtime\", \"set up AgentCore Memory\", \"use AgentCore Gateway\", \"configure AgentCore Identity\", \"set up AgentCore Policy\", \"plan agent observability\", \"evaluate agent quality\", \"move agent PoC to production\", or mentions AgentCore, AgentCore Runtime, AgentCore Memory, AgentCore Gateway, AgentCore Identity, AgentCore Policy, AgentCore Evaluations, AgentCore Code Interpreter, AgentCore Browser, A2A protocol, or multi-agent orchestration on AWS.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[575,578,579],{"name":576,"slug":577,"type":16},"Agents","agents",{"name":14,"slug":15,"type":16},{"name":21,"slug":22,"type":16},"2026-07-12T08:40:11.108951",{"slug":582,"name":582,"fn":583,"description":584,"org":585,"tags":586,"stars":23,"repoUrl":24,"updatedAt":595},"aidlc-lite","develop AI applications on AWS","Lightweight AI development lifecycle for building on AWS. A simplified take on the AI-DLC philosophy — think together, then build fast. Acts as a design partner that understands intent, proposes alternatives with trade-offs, and ships working code without the ceremony of full requirements\u002Fdesign\u002Fspec documents. Use when a founder says \"build X on AWS\", \"add Y to my stack\", \"scaffold an API\", or \"write the CDK for Z\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[587,588,591,592],{"name":576,"slug":577,"type":16},{"name":589,"slug":590,"type":16},"AI Infrastructure","ai-infrastructure",{"name":21,"slug":22,"type":16},{"name":593,"slug":594,"type":16},"Engineering","engineering","2026-07-12T08:40:40.204103",{"slug":597,"name":597,"fn":598,"description":599,"org":600,"tags":601,"stars":23,"repoUrl":24,"updatedAt":607},"architect-for-startups","advise on AWS architecture for startups","AWS architecture advisor tailored specifically for startups. Alters AWS architecture recommendations based on startup stage (pre-revenue through Series B+), team size, runway, and credits. ALWAYS use when asked about building on AWS, choosing services, planning infrastructure, managing costs with credits, or preparing architecture for fundraising.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[602,603,604],{"name":14,"slug":15,"type":16},{"name":21,"slug":22,"type":16},{"name":605,"slug":606,"type":16},"Strategy","strategy","2026-07-12T08:41:33.557354",{"slug":4,"name":4,"fn":5,"description":6,"org":609,"tags":610,"stars":23,"repoUrl":24,"updatedAt":25},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[611,612,613],{"name":14,"slug":15,"type":16},{"name":21,"slug":22,"type":16},{"name":18,"slug":19,"type":16},{"slug":615,"name":615,"fn":616,"description":617,"org":618,"tags":619,"stars":23,"repoUrl":24,"updatedAt":625},"aws-compare","compare AWS architecture options","Compare 2-3 AWS architecture options side-by-side across cost, complexity, performance, security, and operational burden. Use when evaluating trade-offs between approaches or when the user is deciding between options.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[620,621,622,623],{"name":14,"slug":15,"type":16},{"name":21,"slug":22,"type":16},{"name":221,"slug":499,"type":16},{"name":191,"slug":624,"type":16},"security","2026-07-12T08:40:23.960287",{"slug":627,"name":627,"fn":628,"description":629,"org":630,"tags":631,"stars":23,"repoUrl":24,"updatedAt":638},"aws-debug","debug AWS infrastructure and deployment failures","Debug AWS infrastructure issues, deployment failures, and runtime errors. Use when troubleshooting CloudFormation stack failures, Lambda errors, ECS task failures, permission issues, networking problems, or any AWS service misbehavior.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[632,633,634,637],{"name":21,"slug":22,"type":16},{"name":398,"slug":399,"type":16},{"name":635,"slug":636,"type":16},"Deployment","deployment",{"name":404,"slug":405,"type":16},"2026-07-12T08:40:16.767171",{"slug":640,"name":640,"fn":641,"description":642,"org":643,"tags":644,"stars":23,"repoUrl":24,"updatedAt":653},"aws-diagram","generate AWS architecture diagrams","Generate AWS architecture diagrams in Mermaid or ASCII from a description, existing IaC, or conversation context. Use when the user wants to visualize an architecture.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[645,646,647,650],{"name":14,"slug":15,"type":16},{"name":21,"slug":22,"type":16},{"name":648,"slug":649,"type":16},"Diagrams","diagrams",{"name":651,"slug":652,"type":16},"Visualization","visualization","2026-07-12T08:40:43.26341",42]