CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

81%

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.

A thorough, executable skill with well-sequenced deployment workflows, weakened mainly by speculative API calls and dangling references to non-existent bundle files.

Suggestions

Create the referenced files (references/iam-policies.md, troubleshooting.md, performance-tuning.md) or remove the dangling References links so navigation resolves.

Verify the blue-green/rollback code against the real AgentCore API; replace speculative calls (update_agent_runtime_endpoint, agentcore rollback) and define the run_smoke_tests helper or mark it as a stub.

Move the bulk of each deployment method into one-level-deep reference files and keep SKILL.md as a concise overview pointing to them, to tighten token budget and improve navigation.

DimensionReasoningScore

Conciseness

Mostly lean executable code and commands, but the Overview restates the frontmatter and the "Key Principles"/"Quality Targets" blocks add minor padding that could be trimmed, fitting the efficient-with-minor-over-explanation anchor.

4 / 5

Actionability

Largely copy-paste-ready code across all four methods, but the blue-green/rollback sections rely on a speculative `update_agent_runtime_endpoint` API and an undefined `run_smoke_tests` helper, leaving minor gaps.

4 / 5

Workflow Clarity

Each method is clearly sequenced with numbered steps and real checkpoints (local test, deployed test, CI test job, blue-green smoke gate), though container/IaC methods lack explicit validate-before-proceed steps.

4 / 5

Progressive Disclosure

Clear section structure and a listed References section, but the cited reference files (iam-policies.md, troubleshooting.md, performance-tuning.md) do not exist and the bulk of all four methods is inlined rather than split.

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 clearly states capabilities and explicit use-when triggers with concrete keywords. Only trigger-term breadth (synonyms/extensions) keeps it from a perfect score.

DimensionReasoningScore

Specificity

Names five concrete deployment methods ("starter toolkit, direct code deploy, container deploy, CI/CD pipelines, and infrastructure as code"), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

Explicitly answers both what (the five deployment patterns) and when ("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" give good coverage, but it lacks synonyms/file extensions that would lift it to 5.

4 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche (Amazon Bedrock AgentCore deployment) with distinct triggers and minimal overlap risk versus 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.

Validation13 / 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
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.