CtrlK
BlogDocsLog inGet started
Tessl Logo

eventbridge

AWS EventBridge serverless event bus for event-driven architectures. Use when creating rules, configuring event patterns, setting up scheduled events, integrating with SaaS, or building cross-account event routing.

83

1.07x
Quality

78%

Does it follow best practices?

Impact

91%

1.07x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/eventbridge/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

This is a comprehensive and highly actionable EventBridge reference with excellent executable examples covering the key use cases. Its main weaknesses are its monolithic structure (everything in one large file with no progressive disclosure) and some verbosity in explaining concepts Claude already understands. Adding validation checkpoints to multi-step workflows and splitting content into supporting files would significantly improve it.

Suggestions

Split the CLI Reference tables, Best Practices, and Troubleshooting sections into separate bundle files (e.g., CLI_REFERENCE.md, TROUBLESHOOTING.md) and reference them from the main SKILL.md to improve progressive disclosure.

Remove or drastically condense the Core Concepts section — Claude already knows what event buses, rules, patterns, and targets are; just note EventBridge-specific constraints like the 5-target limit.

Add explicit validation steps to the creation workflows, e.g., after creating a rule, verify with `aws events describe-rule` before adding targets, and check `put-events` response for FailedEntryCount.

Remove the Table of Contents and CLI Reference tables to save tokens — these add little value for Claude who can look up CLI commands.

DimensionReasoningScore

Conciseness

The skill is mostly efficient with good code examples, but includes some unnecessary content like the Core Concepts section explaining what event buses, rules, and targets are — concepts Claude already knows. The CLI Reference tables are also somewhat redundant given that Claude knows AWS CLI commands. The Table of Contents adds tokens without much value for a skill file.

2 / 3

Actionability

Excellent actionability with fully executable CLI commands and boto3 code examples throughout. Every pattern includes copy-paste ready commands with realistic ARNs, JSON payloads, and complete parameter sets including often-forgotten steps like Lambda permissions.

3 / 3

Workflow Clarity

The 'Create Custom Event Bus and Rule' section shows a clear multi-step sequence including the often-missed Lambda permission step, and troubleshooting has good debug sequences. However, there are no explicit validation checkpoints or feedback loops — e.g., after creating a rule, there's no step to verify it was created correctly before adding targets, and no error recovery guidance in the creation workflows.

2 / 3

Progressive Disclosure

This is a monolithic file with no bundle files and no content split across references. At ~300 lines, the CLI reference tables, detailed troubleshooting, and best practices sections could be separated into supporting files. The only references are external AWS documentation links, not structured internal navigation.

1 / 3

Total

8

/

12

Passed

Description

100%

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

This is a strong skill description that clearly identifies the technology (AWS EventBridge), lists specific capabilities, and provides explicit trigger guidance via a 'Use when...' clause. It uses proper third-person voice and includes natural keywords that users would employ when seeking help with EventBridge. The description is concise yet comprehensive.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: creating rules, configuring event patterns, setting up scheduled events, integrating with SaaS, and building cross-account event routing. These are distinct, actionable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (AWS EventBridge serverless event bus for event-driven architectures) and 'when' with an explicit 'Use when...' clause listing five specific trigger scenarios.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'EventBridge', 'event bus', 'event-driven', 'rules', 'event patterns', 'scheduled events', 'SaaS', 'cross-account event routing'. These cover the main terms a user working with AWS EventBridge would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with AWS EventBridge as a clear niche. Terms like 'event bus', 'event patterns', 'cross-account event routing' are specific enough to avoid conflicts with other AWS or general serverless skills.

3 / 3

Total

12

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
itsmostafa/aws-agent-skills
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.