setup

Set up the AWS DevOps Agent and AWS Security Agent connections. Use when the user says "set up", "configure", "connect", or when MCP tools are missing.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 content is a tight, well-structured orchestrator that routes to two named sub-skills with a sensible conditional. Its only real gap is the absence of any verification step to confirm each agent connection succeeded before declaring setup complete.

Suggestions

Add a brief verification step after each invocation (e.g., confirm the DevOps Agent MCP connection responds and the Security Agent workspace/IAM role/S3 bucket exist) to raise actionability and workflow clarity.

Note the expected outcome or failure signal if a sub-skill cannot complete, so Claude knows when to stop versus retry.

Dimension	Reasoning	Score
Conciseness	Four lean lines with zero padding and no explanation of concepts Claude already knows; every token earns its place. This matches the anchor 5 'lean and efficient' example.	5 / 5
Actionability	Names the two specific skills to invoke and what each configures (MCP connection; agent space/IAM role/S3 bucket), plus a single-agent conditional, giving mostly executable guidance. It falls short of 5 because there is no verification step and only one edge case is addressed.	4 / 5
Workflow Clarity	A clear ordered 1-then-2 sequence with a single-agent conditional; this is a non-destructive orchestration skill so the validation cap does not apply. It is not a 5 because there are no explicit validation or feedback-loop checkpoints.	4 / 5
Progressive Disclosure	The body is under 50 lines, requires no external bundle references (none exist), and is well-organized with a numbered list and a conditional note. Per the rubric's simple-skill guidance this qualifies for anchor 5.	5 / 5
	Total	18 / 20 Passed

Description

78%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.

The description is strong: it answers both 'what' and 'when' with concrete, natural trigger phrases and a specific AWS-agent niche. Its main weakness is that the action vocabulary is a single generic verb ('set up') repeated, limiting specificity and creating slight overlap risk with other setup skills.

Suggestions

Add one or two more concrete verbs to the 'what' clause (e.g., 'Set up, link, and verify the AWS DevOps Agent and AWS Security Agent connections') to lift specificity and distinctiveness.

Tie the generic triggers more tightly to the niche (e.g., 'Use when the user asks to set up or connect the AWS DevOps or Security Agent, or when those MCP tools are missing') to reduce overlap with unrelated setup skills.

Dimension	Reasoning	Score
Specificity	Names the domain (AWS DevOps/Security Agent connections) and one concrete action ('Set up...connections'), but does not enumerate several distinct actions. It sits at anchor 3 rather than 4 because the single 'set up' action is repeated across two agents rather than expanded into multiple capabilities.	3 / 5
Completeness	Explicitly states both what the skill does ('Set up the AWS DevOps Agent and AWS Security Agent connections') and when to use it with concrete trigger phrases, matching the anchor 5 example. It clears the 'Use when...' clause requirement rather than capping at 3.	5 / 5
Trigger Term Quality	Includes natural user phrases 'set up', 'configure', 'connect' plus the diagnostic cue 'when MCP tools are missing', giving good keyword coverage. It is not a 5 because it lacks synonyms and file/extension-style variants.	4 / 5
Distinctiveness Conflict Risk	The AWS DevOps/Security Agent pairing is a clear niche, but the trigger verbs 'set up', 'configure', and 'connect' are generic and could overlap with other setup skills, leaving minor conflict risk. It is mostly distinct but not minimal-risk like a 5.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: aws/agent-toolkit-for-aws
Path: plugins/aws-agents-for-devsecops/skills/setup/SKILL.md
Commit: 8ea26bd

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.