Name: amazon-eventbridge
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

amazon-eventbridge

Amazon EventBridge integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amazon EventBridge data.

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/amazon-eventbridge/SKILL.md

Quality

Content

75%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 body is highly actionable with copy-paste CLI commands and a well-sequenced connection workflow that includes state-based polling checkpoints. Its main weakness is conciseness: an unnecessary introductory explanation of EventBridge and light marketing padding, plus an ambiguous 'Step 2' reference in the workflow.

Suggestions

Remove or compress the opening paragraph that explains what Amazon EventBridge is; Claude already knows this and it costs context for no gain.

Fix the 'skip to Step 2' navigation by numbering the steps explicitly (e.g. '### Step 1: Connect', '### Step 2: Search and run actions') so the cross-reference resolves.

Trim marketing phrasing such as 'so you can focus on the integration logic rather than auth plumbing' to keep the guidance purely instructional.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient, copy-paste-ready CLI commands, but the opening paragraph explains what Amazon EventBridge is (a concept Claude already knows) and there is some marketing-style padding around Membrane's auth handling.	3 / 5
Actionability	It provides fully executable, copy-paste-ready `membrane` commands with flags for install, login, connection, action listing/running, and proxying, plus a clear options table covering the common cases.	5 / 5
Workflow Clarity	The install→authenticate→connect→poll→search→run sequence is clear with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the 'skip to Step 2' reference points to a step that is not clearly labeled.	4 / 5
Progressive Disclosure	As a single-file skill with no bundle files, it is well organized into clearly headed sections (Overview, Install, Authentication, Connecting, Searching, Actions, Proxy, Best practices), though some detailed connection-state material could justify a separate reference.	4 / 5
	Total	16 / 20 Passed

Description

57%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 cleanly answers both what the skill does and when to use it with an explicit trigger clause, but its capability phrasing is generic and it lacks EventBridge-specific keywords beyond the product name. Tightening the action list to concrete EventBridge operations and adding synonyms would raise specificity and trigger quality.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete EventBridge operations such as 'create event buses, rules, and archives, put events, and manage connections'.

Add natural trigger synonyms to the 'Use when' clause, e.g. 'when the user mentions EventBridge, event buses, rules, or event-driven workflows'.

Keep the third-person voice and explicit 'Use when' trigger, but make the 'what' clause as specific as the 'when' clause.

Dimension	Reasoning	Score
Specificity	The description names the domain but the actions ('Manage data, records, and automate workflows') are generic rather than concrete EventBridge operations like creating event buses or rules.	2 / 5
Completeness	It states both a 'what' ('Amazon EventBridge integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Amazon EventBridge data.'), though the 'what' is somewhat vague.	4 / 5
Trigger Term Quality	It includes the product name 'Amazon EventBridge' twice but misses common synonyms and variations a user might say such as 'event bus', 'rules', or 'events'.	3 / 5
Distinctiveness Conflict Risk	Naming a specific AWS service gives it a distinct niche with minimal conflict risk, but the generic 'manage data, records' phrasing leaves minor overlap with other data/integration skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/amazon-eventbridge/SKILL.md
Commit: f484c82

Reviewed: 3 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.