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
77%
Does it follow best practices?
Impact
91%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/eventbridge/SKILL.mdQuality
Discovery
89%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 well-structured skill description that follows best practices with an explicit 'Use when...' clause and good trigger term coverage. The main weakness is that the capabilities could be more concrete (e.g., 'create cron-based schedules' instead of 'setting up scheduled events'). Overall, it effectively distinguishes itself and provides clear guidance for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AWS EventBridge) and lists several actions (creating rules, configuring event patterns, setting up scheduled events, integrating with SaaS, cross-account event routing), but these are more like feature areas than concrete specific actions like 'extract text' or 'fill forms'. | 2 / 3 |
Completeness | Clearly answers both what (AWS EventBridge serverless event bus for event-driven architectures) and when (explicit 'Use when...' clause with five specific trigger scenarios: creating rules, configuring event patterns, setting up scheduled events, integrating with SaaS, building cross-account event routing). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'EventBridge', 'rules', 'event patterns', 'scheduled events', 'SaaS', 'cross-account', 'event routing', 'event-driven'. These are terms AWS users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with AWS EventBridge as a clear niche. The specific triggers (event patterns, scheduled events, SaaS integration, cross-account event routing) are unique to EventBridge and unlikely to conflict with other AWS or general skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%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 EventBridge reference with excellent actionable code examples in both CLI and Python. The main weaknesses are verbosity in the concepts section, lack of explicit validation steps in workflows, and a monolithic structure that could benefit from splitting detailed reference material into separate files.
Suggestions
Remove or significantly trim the 'Core Concepts' section - Claude knows what event buses, rules, and targets are; focus only on EventBridge-specific constraints (e.g., 5 targets per rule limit)
Add explicit validation steps to workflows: after creating rules, show how to verify they're active with `describe-rule` and test with `test-event-pattern` before adding targets
Split CLI Reference tables and detailed Troubleshooting into separate files (e.g., CLI_REFERENCE.md, TROUBLESHOOTING.md) with clear links from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is generally efficient but includes some unnecessary explanations Claude would know (e.g., defining what an event bus is, explaining that Lambda is a target). The core concepts section could be trimmed significantly. | 2 / 3 |
Actionability | Excellent executable examples throughout with both AWS CLI and boto3 code that is copy-paste ready. Includes complete workflows with Lambda permissions, specific ARN formats, and real command syntax. | 3 / 3 |
Workflow Clarity | Steps are presented but lack explicit validation checkpoints. The create-rule-add-target-add-permission sequence is shown but doesn't include verification steps (e.g., 'verify rule is enabled', 'test with sample event before production use'). | 2 / 3 |
Progressive Disclosure | Good table of contents and section organization, but the document is quite long (~350 lines) with all content inline. The CLI reference tables and troubleshooting sections could be split into separate files with clear references. | 2 / 3 |
Total | 9 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- itsmostafa/aws-agent-skills
- Commit
5df6da7
- 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.