Name: bannerbear
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

bannerbear

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

Quality

64%

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/bannerbear/SKILL.md

Quality

Content

67%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 a well-structured, action-oriented guide dominated by executable Membrane CLI commands and a clear connection workflow with validation feedback loops. It could be tightened by trimming the introductory prose and adding post-run verification guidance.

Suggestions

Trim the opening paragraph explaining what Bannerbear is and the 'so you can focus on the integration logic rather than auth plumbing' aside, since Claude can infer these, improving conciseness.

Add an explicit verification step after running actions or proxy requests (e.g., check the `output` field, confirm `state`, or verify a created resource exists) to strengthen the workflow's feedback loop.

Consider moving the full popular-actions table to a reference file and keeping only the most common actions inline, to improve progressive disclosure for this multi-section skill.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but the opening paragraph explains what Bannerbear is and includes some padded prose ('so you can focus on the integration logic rather than auth plumbing'), fitting the score-3 anchor for mostly-efficient content that could be tightened.	3 / 5
Actionability	It provides concrete, copy-paste-ready bash commands throughout (install, login, connection ensure, action list/run, request) plus a popular-actions table with keys and a proxy-flags table, with only minor placeholder gaps (CONNECTION_ID, actionId), matching the score-4 anchor.	4 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit checkpoints and a feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll after the user acts), though action-running and proxy steps lack explicit post-run verification, fitting the score-4 anchor.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references, and the inline popular-actions table is reasonably placed; there are no bundle files but the structure is good, matching the score-4 anchor with minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

61%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 is clear, in third person, and covers both what the skill does and when to use it, with a distinct trigger tied to the Bannerbear platform. Its main weakness is the generic 'manage data, records, and automate workflows' wording that does not list concrete Bannerbear-specific actions.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Bannerbear actions such as 'generate images and videos from templates, create animated GIFs, and capture screenshots'.

Expand the trigger clause to include natural user phrases and file/resource types, e.g. 'Use when the user wants to generate images or videos, create animated GIFs, or capture screenshots with Bannerbear templates'.

Mention key Bannerbear resource nouns users actually reference (templates, images, videos, screenshots, GIFs) to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Bannerbear integration') but the actions ('Manage data, records, and automate workflows') are minimal and generic, matching the score-2 anchor rather than the more concrete score-3 anchor.	2 / 5
Completeness	Both the 'what' (Bannerbear integration, manage data/records, automate workflows) and an explicit 'Use when...' 'when' clause are present, though the trigger could be more specific, fitting the score-4 anchor.	4 / 5
Trigger Term Quality	It includes the relevant keyword 'Bannerbear' and the phrase 'interact with Bannerbear data', but lacks common variations or synonyms a user might say, matching the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	Bannerbear is a specific named platform with a clear niche ('Bannerbear integration'), giving it distinct triggers and minimal conflict risk with other skills, matching the score-5 anchor.	5 / 5
	Total	14 / 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/bannerbear/SKILL.md
Commit: f484c82

Reviewed: ~1 hour 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.