agentcore-harness-builder
SolidBuild 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.
Install
Quality Score: 82/100
Skill Content
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
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.
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.
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.