amazon-bedrock

Builds generative AI applications on Amazon Bedrock covering model invocation, RAG, agents, and AgentCore.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/dennisvink/yolomancer --skill amazon-bedrock-dennisvink
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amazon-bedrock
Source: https://github.com/dennisvink/yolomancer/tree/main/skills/aws/core-skills/amazon-bedrock
Command: npx skills add https://github.com/dennisvink/yolomancer --skill amazon-bedrock-dennisvink

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires boto3, and includes references (resource) components.

What problem does it solve? Building on Amazon Bedrock involves five separate API endpoints, provider-specific request formats, and frequent model and configuration changes that cause errors like ThrottlingException, AccessDeniedException, and malformed requests. This Skill provides authoritative, up-to-date procedures and reference files so agents invoke models, build RAG pipelines, create agents, and deploy to AgentCore correctly the first time. ## Core Features & Use Cases - Model Invocation: Guides Converse API vs InvokeModel selection, enforces explicit maxTokens to prevent silent quota reservation, and provides Python and TypeScript SDK patterns. - Knowledge Bases (RAG): Step-by-step KB creation, chunking strategy selection, retrieval modes (retrieve-and-generate vs retrieve), and ingestion troubleshooting. - Agents and AgentCore: Covers Bedrock Agents with action groups, migration to AgentCore Harness, Gateway target setup, Memory, Identity, Payments (x402), and observability. - Operations Workflows: Prompt caching setup and debugging, quota health audits, cost tracking by team or model, and Claude generation migration checklists. - Use Case: A developer hits repeated ThrottlingException errors; the Skill diagnoses unset maxTokens reserving excess quota, checks service quotas, and recommends cross-region inference profiles. ## Quick Start Ask the assistant to invoke a Claude model on Bedrock using the Converse API with maxTokens set explicitly, or to walk you through creating a Knowledge Base for your documents.

Frequently Asked Questions about amazon-bedrock

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

FAQPage Schema
How do I invoke a Claude model on Amazon Bedrock?

Use the Converse API via the bedrock-runtime endpoint rather than InvokeModel, and always set maxTokens explicitly. Verify the model ID with aws bedrock list-foundation-models and consider a cross-region inference profile prefix like us. for higher availability.

Converse API vs InvokeModel on Bedrock, which should I use?

Use the Converse API for a unified request and response format across all models. Use InvokeModel only when you need provider-specific features unavailable in Converse, since it requires different body formats per provider such as Anthropic, Titan, Llama, and Nova.

Why am I getting ThrottlingException on Amazon Bedrock?

The most common cause is leaving maxTokens unset, which defaults to the model maximum and silently reserves far more quota than needed. Set maxTokens explicitly, use adaptive retry mode, and check current limits with aws service-quotas get-service-quota.

How do I set up RAG with Bedrock Knowledge Bases?

Follow the seven-step Knowledge Base setup procedure in the skill's reference file, choosing a chunking strategy such as semantic chunking with FM-based parsing for PDFs containing tables. After creation, run start-ingestion-job and wait for completion before querying.

Should I use AgentCore Harness or AgentCore Runtime for my agent?

Choose Harness when you want a managed config-based agent loop with no orchestration code, which is the preferred path for new builds. Choose Runtime when you need a specific framework, full loop control, graph workflows, or bidirectional streaming with your own container.

Why does my Bedrock agent return stale behavior after configuration changes?

You must run prepare-agent after any configuration change to a Bedrock Agent. Skipping this mandatory step leaves the agent running its previous configuration, which is a common cause of stale behavior.