AWS Bedrock integration for LangChain4j enabling Java applications to interact with various LLM providers through a unified interface
—
Pending
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Pending
The risk profile of this skill
This is an optimized version of the AWS Bedrock integration tile, restructured for better agent usage.
docs/
├── index.md # 443 char overview
├── quickstart/ # Quick getting-started guides
│ ├── basic-chat.md
│ ├── streaming.md
│ └── embeddings.md
├── api/ # Clean API reference
│ ├── chat-models.md
│ ├── embedding-models.md
│ └── parameters.md
├── features/ # Advanced features
│ ├── prompt-caching/
│ │ ├── overview.md
│ │ ├── simple-caching.md
│ │ ├── granular-caching.md
│ │ └── best-practices.md
│ └── guardrails/
│ ├── overview.md
│ ├── configuration.md
│ ├── handling-assessments.md
│ └── use-cases.md
├── guides/ # Task-oriented how-tos
│ ├── thinking-mode.md
│ ├── multimodal.md
│ ├── tool-calling.md
│ ├── error-handling.md
│ └── semantic-search.md
└── reference/ # Factual reference
├── models.md
└── setup.md| Metric | Before | After | Δ |
|---|---|---|---|
| Findability | 6/10 | 9/10 | +3 |
| Progressive Disclosure | 4/10 | 9/10 | +5 |
| Agent Optimization | 5/10 | 9/10 | +4 |
| Overall | 6.4/10 | 9.0/10 | +2.6 |
All original content preserved:
Run this command to compare with original:
diff -r .tessl/tiles/tessl/maven-dev-langchain4j--langchain4j-bedrock/docs ./tiles/maven-dev-langchain4j--langchain4j-bedrock-alt/docs