eventbridge-rule-creator
Eventbridge Rule Creator - Auto-activating skill for AWS Skills. Triggers on: eventbridge rule creator, eventbridge rule creator Part of the AWS Skills skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/eventbridge-rule-creator/SKILL.mdQuality
Discovery
7%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 description is extremely weak — it is essentially just the skill name repeated with boilerplate framing. It provides no concrete actions, no meaningful trigger terms beyond the skill name, and no guidance on when Claude should select this skill. It would be nearly indistinguishable from other AWS-related skills in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates AWS EventBridge rules with event patterns, schedules (cron/rate expressions), and target configurations for Lambda, SQS, SNS, and other AWS services.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create EventBridge rules, set up event-driven triggers, configure CloudWatch Events, define event patterns, or schedule recurring AWS tasks.'
Diversify trigger terms to include common variations users might say: 'EventBridge', 'event rule', 'CloudWatch Events', 'scheduled event', 'event pattern', 'cron schedule', 'event bus rule'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Eventbridge Rule Creator') but does not describe any concrete actions like creating rules, defining event patterns, setting targets, or configuring schedules. It is essentially just a title repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a redundant repetition of the skill name rather than meaningful trigger guidance. There is no explicit 'Use when...' clause with real scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'eventbridge rule creator' repeated twice. It misses natural user phrases like 'create EventBridge rule', 'event pattern', 'CloudWatch Events', 'scheduled event', 'event bus', or 'AWS event routing'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'EventBridge Rule' is somewhat specific to a particular AWS service, which provides some distinctiveness. However, the lack of detail about what specifically it does (vs. other EventBridge-related skills) and the generic 'AWS Skills' category could cause overlap with other AWS skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template/placeholder with no actual content about creating EventBridge rules. It contains only generic boilerplate text that repeats the skill name without providing any actionable guidance, code examples, event pattern definitions, CloudFormation snippets, or AWS CLI commands. It would provide zero value to Claude in performing EventBridge rule creation tasks.
Suggestions
Add concrete, executable examples such as AWS CLI commands (`aws events put-rule`), CloudFormation/CDK templates, or Terraform configurations for creating EventBridge rules with specific event patterns and targets.
Include a clear multi-step workflow: define event pattern → create rule → set target (Lambda, SQS, etc.) → configure IAM permissions → validate with a test event, with explicit validation checkpoints.
Provide specific event pattern examples (e.g., EC2 state changes, S3 events, scheduled expressions) with copy-paste ready JSON patterns.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual technical content that teaches Claude how to create EventBridge rules correctly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'eventbridge rule creator' excessively, and contains zero substantive information about actually creating EventBridge rules. | 1 / 3 |
Actionability | There are no concrete commands, code examples, API calls, CloudFormation templates, or any executable guidance whatsoever. The skill describes what it could do rather than providing any actual instructions for creating EventBridge rules. | 1 / 3 |
Workflow Clarity | There is no workflow, no steps, no sequence, and no validation checkpoints. Creating EventBridge rules involves multiple steps (defining event patterns, targets, IAM roles, etc.) and none of this is addressed. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic placeholder with no structure beyond generic headings. There are no references to supporting files, no bundle files exist, and the sections contain no meaningful content to organize. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.