CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bedrock-agentcore-deployment

Amazon Bedrock AgentCore deployment patterns for production AI agents. Covers starter toolkit, direct code deploy, container deploy, CI/CD pipelines, and infrastructure as code. Use when deploying agents to production, setting up CI/CD, or managing agent infrastructure.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable code for all four deployment methods and both CI pipelines, and workflows include genuine validation checkpoints. Its main weaknesses are broken references to nonexistent bundle files and large inlined configurations that belong in separate reference files.

Suggestions

Create the referenced bundle files (references/iam-policies.md, references/troubleshooting.md, references/performance-tuning.md) or remove the References section, since none of them exist in the skill bundle.

Move the full Terraform configuration and at least one CI pipeline into reference files so SKILL.md stays a lean overview with one-level-deep, well-signaled pointers.

Make the blue-green and rollback sections executable: define or remove the run_smoke_tests helper, replace the speculative update_agent_runtime_endpoint call, and verify the `agentcore rollback --to-version` CLI flag actually exists.

DimensionReasoningScore

Conciseness

The body is dense with executable commands and code with little conceptual padding, but includes time-sensitive claims ("validated by AWS December 2025") outside any deprecation section, an Overview that restates the description, and arm64 packaging steps duplicated between Method 2 and the GitLab pipeline.

4 / 5

Actionability

Most guidance is copy-paste ready (pip/agentcore commands, uv packaging, boto3 calls, Dockerfile, Terraform, CI YAML), but the blue-green example calls an undefined run_smoke_tests, uses a speculative update_agent_runtime_endpoint call hedged with "actual rename may require recreate", and includes an unverified `agentcore rollback --to-version` flag.

4 / 5

Workflow Clarity

Each deployment method is clearly sequenced with numbered steps and real checkpoints (test locally before deploy, invoke after deploy, CI test job gating deploy, smoke tests before blue-green cutover). Minor gaps remain: Method 2 has no post-deploy verification and rollback guidance is thin.

4 / 5

Progressive Disclosure

The References section lists references/iam-policies.md, references/troubleshooting.md, and references/performance-tuning.md, but no references/ directory or bundle files exist — all three links are dangling. Additionally, the full Terraform configuration and two complete CI pipelines are inlined in SKILL.md where a leaner overview pointing to separate reference files would be more appropriate.

3 / 5

Total

15

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that names the platform, enumerates concrete deployment methods, and provides an explicit use-when clause with natural trigger phrases. Only minor synonym coverage is missing from the trigger terms.

DimensionReasoningScore

Specificity

The description lists five concrete deployment approaches ("starter toolkit, direct code deploy, container deploy, CI/CD pipelines, and infrastructure as code") in third-person voice ("Covers"), giving comprehensive coverage of the skill's capabilities rather than generic language.

5 / 5

Completeness

It explicitly answers both what it does (five named deployment approaches) and when to use it ("Use when deploying agents to production, setting up CI/CD, or managing agent infrastructure") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural phrases like "deploying agents to production", "setting up CI/CD", and "managing agent infrastructure" map well to what users would say, but common synonyms and variations (e.g., "release", "roll out", "ship agents", "agent runtime") are missing.

4 / 5

Distinctiveness Conflict Risk

"Amazon Bedrock AgentCore" names a specific platform with distinct deployment triggers, creating a clear niche with minimal conflict risk against generic deployment skills.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (630 lines); consider splitting into references/ and linking

Warning

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

13

/

16

Passed

Repository

fernandezbaptiste/Skrillz

Path

skills/bedrock-agentcore-deployment/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.