agentcore-harness-builder

Solid

Build production-ready AWS Bedrock AgentCore Harness agents end to end — declarative model + prompt, managed/BYO Memory, built-in Browser, Code Interpreter, Web Search and Knowledge Bases (RAG), Gateway/MCP tools + rate limits, inline functions, Skills (incl. AWS catalog), versioning + endpoints, advanced config (truncation, limits, lifecycle, network, inbound auth, BYO S3 Files/EFS mounts or container), Observability (log delivery), Evaluations, Optimizations, Identity (outbound auth, Token Vault, BYO secrets), Policy (Cedar + temporal), Payments, Registry, Runtime Instances (14-day EC2 sessions), Step Functions, export to Strands code. Use whenever the user wants to create, configure, deploy, version, wire, harden, invoke, or troubleshoot an AgentCore Harness — or asks about AgentCore best practices, harness.json, CreateHarness/UpdateHarness/InvokeHarness, endpoints/qualifiers, Memory, knowledge bases/RAG, or observability. Trigger even for a managed declarative Bedrock agent with no "harness" mention.

AI & Automation 10 stars 3 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
35
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# AWS Bedrock AgentCore Harness Builder ## Overview A **Harness** is AWS Bedrock AgentCore's declarative, fully-managed way to run an agent. You hand AWS a JSON configuration — model, system prompt, tools, memory, skills, limits — and AWS runs the agent loop (Strands under the hood) inside a per-session Firecracker microVM with its own filesystem and shell. No container to build by default (a custom image via `environmentArtifact` is an advanced option), no agent loop to write. You change behavior by changing config, not redeploying code, and you can override model/prompt per invocation. This skill builds a **complete, best-practice Harness use case** that exercises every AgentCore capability the user needs, wired correctly the first time. Harness is **generally available** (GA 2026-06-17, all AWS Commercial Regions where AgentCore is available, plus GovCloud US-West since 2026-08; only Payments remains preview), but it is still fast-moving and the real API shapes often differ from the published docs — this skill encodes the hard-won facts so you don't rediscover them through validation errors. ### The two-plane mental model (internalize this first) AgentCore has two distinct API surfaces. Confusing them is the #1 source of wasted time. | Plane | What it is | How you call it | |---|---|---| | **Control plane** | Create/configure/inspect resources (harness, memory, runtimes) | `boto3.client("bedrock-agentcore-control")` — `create_harness`, `update_harness`, `create_memor...

Details

Author
timwukp
Repository
timwukp/agent-skills-best-practice
Created
6 months ago
Last Updated
yesterday
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

harness-engineering

Principles and judgment for designing an "agent harness" — the repo-level scaffolding (docs, feedback loops, constraints, memory, review gates) that lets AI coding agents work reliably and autonomously on a codebase. Use this whenever the user asks to make a repo more agent-friendly, set up or audit AGENTS.md/CLAUDE.md, improve how well Claude Code (or another agent) performs on their project, design feedback loops or verification gates for agents, decide what should go in project docs vs skills vs memory, or is generally trying to get better/more reliable results from AI coding agents on a specific codebase. Do not treat this as a rigid setup script — apply the principles to the specific project's language, size, team, and risk profile, and recommend only what that project actually needs.

0 Updated 6 days ago
Samjoel3101
AI & Automation Listed

harness-eng

Use when designing, evaluating, or simplifying an agent project harness: AGENTS.md/CLAUDE.md rules, startup scripts, progress logs, feature trackers, handoffs, evaluator rubrics, quality documents, repo-local knowledge maps, and mechanical guardrails for coding agents. Especially useful when converting raw agent-workflow notes into a concise, verifiable project control layer.

7 Updated 1 months ago
MasihMoafi
AI & Automation Listed

agent-harness-engineering

Design agent harnesses for typed loops, runtime reconfiguration, provider/tool/module hot swap, state, policy, cancellation, recovery, and delegation. Excludes prompt-only, generic architecture, vendor CLI/config, and evaluation-only work.

11 Updated 3 weeks ago
Xopoko