bannerbear-automation

Automate Bannerbear tasks via Rube MCP (Composio). Always search tools first for current schemas.

Quality

53%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./composio-skills/bannerbear-automation/SKILL.md

Quality

Discovery

22%

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 too vague to effectively guide skill selection. It names the integration (Bannerbear via Composio) but fails to describe what specific capabilities are available or when the skill should be triggered. The procedural note about searching tools first is implementation detail rather than useful selection criteria.

Suggestions

Add specific capabilities: 'Generate dynamic images from templates, create social media graphics, produce personalized banners and videos'

Add explicit trigger guidance: 'Use when the user mentions Bannerbear, dynamic image generation, automated graphics, or template-based visual content'

Include natural user terms like 'banners', 'social media images', 'dynamic graphics', 'image automation', 'visual content generation'

Dimension	Reasoning	Score
Specificity	The description mentions 'Automate Bannerbear tasks' which is extremely vague - it doesn't specify what tasks can be automated (image generation, template editing, video creation, etc.). 'Always search tools first' is procedural guidance, not a capability description.	1 / 3
Completeness	The 'what' is extremely weak (just 'automate tasks'), and there is no 'when' clause or explicit trigger guidance. Missing a 'Use when...' clause entirely, which per guidelines should cap completeness at 2, but the 'what' is also inadequate.	1 / 3
Trigger Term Quality	Includes 'Bannerbear' which is a specific product name users might mention, and 'Rube MCP' and 'Composio' as technical terms. However, it lacks natural user terms like 'generate images', 'dynamic banners', 'social media graphics', or 'automated visuals'.	2 / 3
Distinctiveness Conflict Risk	'Bannerbear' is a specific product which provides some distinctiveness, but 'automate tasks via Rube MCP (Composio)' is generic enough to overlap with any other Composio-based skill. Without specific task types, it could conflict with other automation skills.	2 / 3
	Total	6 / 12 Passed

Implementation

85%

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

This is a well-structured skill that efficiently teaches the Rube MCP pattern for Bannerbear automation. The workflow is clear with proper validation steps, and the content respects token budget. The main weakness is that actionability could be improved with more concrete Bannerbear-specific examples showing actual image generation or template operations rather than just the generic wrapper pattern.

Suggestions

Add at least one complete, Bannerbear-specific example showing an actual operation (e.g., generating an image from a template) with real tool slugs and arguments that would be returned from RUBE_SEARCH_TOOLS

Include an example of what a successful RUBE_SEARCH_TOOLS response looks like for Bannerbear, so users know what to expect and how to extract the tool slugs and schemas

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding explanations of what Bannerbear or Composio are. Every section provides actionable information without padding or unnecessary context.	3 / 3
Actionability	Provides concrete tool call patterns with parameter examples, but the examples are pseudo-code style rather than fully executable. The actual Bannerbear-specific operations (creating images, templates, etc.) are not shown - only the generic Rube MCP wrapper calls.	2 / 3
Workflow Clarity	Clear 3-step workflow pattern with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status and explicit guidance on when to proceed.	3 / 3
Progressive Disclosure	Well-structured with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to Composio docs is one level deep. Quick reference table provides efficient navigation for common operations.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 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: ComposioHQ/awesome-claude-skills
Commit: 2790447

Reviewed: 2 months 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.