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.
Install with Tessl CLI
npx tessl i github:itsmostafa/aws-agent-skills --skill eventbridgeOverall
score
78%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 strong skill description that clearly identifies its AWS EventBridge focus and provides explicit 'Use when' guidance with multiple trigger scenarios. The main weakness is that the capabilities listed are somewhat high-level task categories rather than granular concrete actions. Overall, it should effectively enable Claude to select this skill when appropriate.
| 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 task categories 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 listing five specific trigger scenarios: creating rules, configuring event patterns, scheduled events, SaaS integration, cross-account routing). | 3 / 3 |
Trigger Term Quality | Includes good natural keywords users would say: 'EventBridge', 'event bus', 'event-driven', 'rules', 'event patterns', 'scheduled events', 'SaaS', 'cross-account'. These cover common terms users would naturally use when working with this AWS service. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific AWS service name (EventBridge) and domain-specific triggers (event patterns, event bus, cross-account event routing). Unlikely to conflict with other skills due to the narrow, well-defined AWS service focus. | 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 solid, actionable skill with excellent executable examples for AWS EventBridge operations. The main weaknesses are verbosity in conceptual sections that Claude doesn't need, and missing validation checkpoints in multi-step workflows. The document would benefit from being split into overview + detailed reference files.
Suggestions
Add explicit validation steps after each operation (e.g., 'Verify rule created: aws events describe-rule --name my-rule') before proceeding to next steps
Remove or significantly trim the 'Core Concepts' section - Claude knows what event buses, rules, and targets are
Split CLI Reference and Troubleshooting into separate files (CLI_REFERENCE.md, TROUBLESHOOTING.md) and link from main skill
Remove the CLI reference tables entirely - Claude can look up command names; focus on the patterns and gotchas
| 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 CLI reference tables and some conceptual sections could be trimmed. | 2 / 3 |
Actionability | Excellent executable examples throughout with complete CLI commands and boto3 code. All examples are copy-paste ready with realistic ARNs and proper JSON formatting. Includes both CLI and Python approaches for key operations. | 3 / 3 |
Workflow Clarity | Multi-step processes like creating event bus + rule + target + permissions are shown but lack explicit validation checkpoints. The troubleshooting section helps but workflows don't include 'verify this worked before proceeding' steps. | 2 / 3 |
Progressive Disclosure | Good table of contents and section organization, but the document is quite long (~350 lines) with content that could be split into separate files (CLI reference, troubleshooting). References section links to external docs but no internal file references for advanced topics. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.