[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMD3FTRCJSCFBKPDB259RT":3,"skill-same:01M7EMD3FTRCJSCFBKPDB259RT":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EMD3FTRCJSCFBKPDB259RT","bedrock-guide",null,"Build on AWS with Amazon Bedrock — managed foundation models, agents, knowledge bases, and guardrails.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-bedrock-guide\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bedrock-guide\ndescription: Build on AWS with Amazon Bedrock — managed foundation models, agents, knowledge bases, and guardrails.\ncategory: ai-research\n---\n\n## Overview\n\nAmazon Bedrock is AWS's managed service for foundation models: access models\nfrom multiple providers (Anthropic, Meta, Mistral, Amazon's own, and others)\nthrough a unified AWS API, with managed capabilities for agents, knowledge\nbases (RAG), and guardrails — all inside your AWS account with IAM, VPC,\nCloudWatch, and regional controls. The pitch is enterprise GenAI on AWS terms:\nyour data stays in your account boundary, access is IAM-governed, and billing\nflows through AWS.\n\nFor AWS-centric organizations, Bedrock is usually the default starting point —\nnot necessarily because it's the best model API, but because it inherits your\nexisting security, compliance, networking, and procurement posture. The models\nare good; the enterprise integration is the point.\n\nThe mental model: Bedrock brings foundation models into the AWS control plane.\nEvaluate it as AWS infrastructure with model capabilities, not as a model lab\nwith AWS hosting.\n\n## When to use\n\n- AWS-centric organizations building GenAI features (leverage existing IAM,\n  VPC, compliance).\n- Applications needing data to stay within your AWS account\u002Fregion boundary.\n- Managed RAG via Knowledge Bases (OpenSearch\u002FAurora-backed retrieval without\n  building it).\n- Managed agents with action groups for AWS-integrated tool use.\n- Guardrails for content filtering and PII redaction as a managed layer.\n- Procurement through AWS (enterprise agreements, private pricing).\n\n## Core concepts\n\n- **Foundation models on Bedrock**: multiple providers' models behind one API\n  (Converse API for chat). Model access must be enabled per region — check\n  availability in your operating regions first.\n- **Cross-region inference**: some models support routing across regions for\n  throughput. Understand the data-residency implications for your compliance\n  requirements.\n- **Knowledge Bases**: managed RAG — connect S3\u002Fdata sources, Bedrock handles\n  chunking, embeddings, and retrieval against OpenSearch Serverless or Aurora.\n  The fastest compliant RAG on AWS.\n- **Agents for Bedrock**: managed agent orchestration with action groups (Lambda\n  or OpenAPI-defined tools). Useful when your tools are already AWS-native.\n- **Guardrails**: managed content filters, denied topics, PII redaction, and\n  grounding checks. A policy layer independent of the model — configure per\n  use case.\n- **IAM and VPC**: model invocation governed by IAM policies; VPC endpoints\n  keep traffic off the public internet. This is the enterprise control story —\n  use it fully.\n- **Provisioned Throughput**: reserved model capacity for latency\u002Fthroughput\n  guarantees. For production SLOs beyond on-demand variability.\n- **Model evaluation**: managed eval jobs (automatic metrics + human workflows)\n  for comparing models and prompts on your data.\n\n## Practical workflow\n\n1. **Confirm regional availability.** Check model availability in your required\n   regions — Bedrock's catalog varies by region, and compliance may pin you to\n   specific ones.\n2. **Set up IAM properly.** Least-privilege policies for model invocation,\n   scoped per application. Use VPC endpoints where network isolation matters.\n3. **Benchmark candidate models.** Same eval set across Bedrock's model options\n   via the Converse API. Include Amazon's own models — they're often\n   cost-competitive.\n4. **Build RAG with Knowledge Bases.** For document-grounded apps: connect data\n   sources, configure chunking, evaluate retrieval quality before building agents\n   on top.\n5. **Configure guardrails per use case.** Content filters, PII handling, denied\n   topics — tuned to the application's risk profile, not one-size-fits-all.\n6. **Use agents where tools are AWS-native.** If actions are Lambda functions\n   and APIs in your AWS environment, Bedrock Agents reduce integration work.\n7. **Evaluate and monitor.** Run Bedrock eval jobs on model\u002Fprompt changes;\n   monitor invocation metrics, guardrail interventions, and costs in CloudWatch.\n\nChecklist for Bedrock production:\n- Model availability confirmed in operating regions.\n- IAM least-privilege; VPC endpoints where needed.\n- Knowledge Base retrieval quality evaluated.\n- Guardrails configured per use case.\n- Provisioned throughput sized if SLOs require it.\n\n## Common pitfalls\n\n- **Region availability assumptions.** Designing around a model unavailable in\n  your compliance-required region. Check first, always.\n- **Cross-region inference vs. data residency.** Throughput routing across\n  regions may violate data-residency requirements. Understand where data goes.\n- **IAM over-permissioning.** Broad `bedrock:*` policies. Scope invocation\n  permissions per application and model.\n- **Knowledge Base as magic.** Expecting managed RAG to work without evaluating\n  chunking and retrieval quality on your documents. Test retrieval first.\n- **Guardrails as the only safety.** Managed filters help; they don't replace\n  application-level validation, prompt design, and human oversight where needed.\n- **On-demand for strict SLOs.** Shared on-demand capacity has variability.\n  Provisioned throughput exists for guarantees — use it when SLOs demand.\n- **Cost opacity.** Bedrock usage across many models\u002Fapps without tagging and\n  attribution. Tag resources; monitor per-application spend.\n- **Treating Bedrock as model-agnostic.** Models differ meaningfully; \"we use\n  Bedrock\" isn't a model choice. Benchmark and choose deliberately.\n","## Overview\n\nAmazon Bedrock is AWS's managed service for foundation models: access models\nfrom multiple providers (Anthropic, Meta, Mistral, Amazon's own, and others)\nthrough a unified AWS API, with managed capabilities for agents, knowledge\nbases (RAG), and guardrails — all inside your AWS account with IAM, VPC,\nCloudWatch, and regional controls. The pitch is enterprise GenAI on AWS terms:\nyour data stays in your account boundary, access is IAM-governed, and billing\nflows through AWS.\n\nFor AWS-centric organizations, Bedrock is usually the default starting point —\nnot necessarily because it's the best model API, but because it inherits your\nexisting security, compliance, networking, and procurement posture. The models\nare good; the enterprise integration is the point.\n\nThe mental model: Bedrock brings foundation models into the AWS control plane.\nEvaluate it as AWS infrastructure with model capabilities, not as a model lab\nwith AWS hosting.\n\n## When to use\n\n- AWS-centric organizations building GenAI features (leverage existing IAM,\n  VPC, compliance).\n- Applications needing data to stay within your AWS account\u002Fregion boundary.\n- Managed RAG via Knowledge Bases (OpenSearch\u002FAurora-backed retrieval without\n  building it).\n- Managed agents with action groups for AWS-integrated tool use.\n- Guardrails for content filtering and PII redaction as a managed layer.\n- Procurement through AWS (enterprise agreements, private pricing).\n\n## Core concepts\n\n- **Foundation models on Bedrock**: multiple providers' models behind one API\n  (Converse API for chat). Model access must be enabled per region — check\n  availability in your operating regions first.\n- **Cross-region inference**: some models support routing across regions for\n  throughput. Understand the data-residency implications for your compliance\n  requirements.\n- **Knowledge Bases**: managed RAG — connect S3\u002Fdata sources, Bedrock handles\n  chunking, embeddings, and retrieval against OpenSearch Serverless or Aurora.\n  The fastest compliant RAG on AWS.\n- **Agents for Bedrock**: managed agent orchestration with action groups (Lambda\n  or OpenAPI-defined tools). Useful when your tools are already AWS-native.\n- **Guardrails**: managed content filters, denied topics, PII redaction, and\n  grounding checks. A policy layer independent of the model — configure per\n  use case.\n- **IAM and VPC**: model invocation governed by IAM policies; VPC endpoints\n  keep traffic off the public internet. This is the enterprise control story —\n  use it fully.\n- **Provisioned Throughput**: reserved model capacity for latency\u002Fthroughput\n  guarantees. For production SLOs beyond on-demand variability.\n- **Model evaluation**: managed eval jobs (automatic metrics + human workflows)\n  for comparing models and prompts on your data.\n\n## Practical workflow\n\n1. **Confirm regional availability.** Check model availability in your required\n   regions — Bedrock's catalog varies by region, and compliance may pin you to\n   specific ones.\n2. **Set up IAM properly.** Least-privilege policies for model invocation,\n   scoped per application. Use VPC endpoints where network isolation matters.\n3. **Benchmark candidate models.** Same eval set across Bedrock's model options\n   via the Converse API. Include Amazon's own models — they're often\n   cost-competitive.\n4. **Build RAG with Knowledge Bases.** For document-grounded apps: connect data\n   sources, configure chunking, evaluate retrieval quality before building agents\n   on top.\n5. **Configure guardrails per use case.** Content filters, PII handling, denied\n   topics — tuned to the application's risk profile, not one-size-fits-all.\n6. **Use agents where tools are AWS-native.** If actions are Lambda functions\n   and APIs in your AWS environment, Bedrock Agents reduce integration work.\n7. **Evaluate and monitor.** Run Bedrock eval jobs on model\u002Fprompt changes;\n   monitor invocation metrics, guardrail interventions, and costs in CloudWatch.\n\nChecklist for Bedrock production:\n- Model availability confirmed in operating regions.\n- IAM least-privilege; VPC endpoints where needed.\n- Knowledge Base retrieval quality evaluated.\n- Guardrails configured per use case.\n- Provisioned throughput sized if SLOs require it.\n\n## Common pitfalls\n\n- **Region availability assumptions.** Designing around a model unavailable in\n  your compliance-required region. Check first, always.\n- **Cross-region inference vs. data residency.** Throughput routing across\n  regions may violate data-residency requirements. Understand where data goes.\n- **IAM over-permissioning.** Broad `bedrock:*` policies. Scope invocation\n  permissions per application and model.\n- **Knowledge Base as magic.** Expecting managed RAG to work without evaluating\n  chunking and retrieval quality on your documents. Test retrieval first.\n- **Guardrails as the only safety.** Managed filters help; they don't replace\n  application-level validation, prompt design, and human oversight where needed.\n- **On-demand for strict SLOs.** Shared on-demand capacity has variability.\n  Provisioned throughput exists for guarantees — use it when SLOs demand.\n- **Cost opacity.** Bedrock usage across many models\u002Fapps without tagging and\n  attribution. Tag resources; monitor per-application spend.\n- **Treating Bedrock as model-agnostic.** Models differ meaningfully; \"we use\n  Bedrock\" isn't a model choice. Benchmark and choose deliberately.\n",{"name":5,"category":24,"description":7},"ai-research","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-bedrock-guide",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill bedrock-guide",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill bedrock-guide",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill bedrock-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-bedrock-guide\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]