Name: project-broadcast
Rating: 64.8 (1 reviews)
Author: membranedev

project-broadcast

Project Broadcast integration. Manage Persons, Organizations, Lists, Broadcasts, Templates, Numbers and more. Use when the user wants to interact with Project Broadcast data.

Quality

77%

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

Quality

Content

76%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 executable CLI commands and a clean structure, but lacks validation checkpoints for batch/broadcast operations and could offload some reference material to bundle files.

Suggestions

Add a validation checkpoint before running broadcast/send actions, e.g. "Confirm the recipient list and message before running send/broadcast actions; verify the connection with `connection list` first."

Trim the opening product framing paragraph and merge the redundant "Popular actions" section into the searching-actions section.

Move the proxy flag reference table to a references/ file and link to it, keeping only the most common flags inline.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and command-driven, with only minor trimmable padding such as the product framing paragraph, "focus on the integration logic rather than auth plumbing", and the redundant "Popular actions" restatement.	4 / 5
Actionability	Copy-paste-ready `npx @membranehq/cli@latest` commands cover setup, connect, list, search, run, and proxy, with a full flag table and clearly signaled placeholders.	5 / 5
Workflow Clarity	A clear sequence (setup → connect → discover → run → proxy) is present, but there are no validation/verification checkpoints and Broadcasts are inherently batch operations, so the destructive/batch cap at 3 applies.	3 / 5
Progressive Disclosure	Content is well-organized into clear headed sections with no nested references, but at ~110 lines with no external bundle files, parts like the proxy flag table could be split out, fitting anchor 4 over the simple-skill 5 exception.	4 / 5
	Total	16 / 20 Passed

Description

78%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 specific, third-person, and clearly distinguishes a named product niche with an explicit use-when clause. Its main weakness is a generic "when" trigger and absence of synonym coverage like SMS or text marketing.

Suggestions

Expand the "when" clause with concrete trigger phrases, e.g. "Use when the user wants to send SMS broadcasts, manage contact lists, or interact with Project Broadcast data."

Replace the generic verb "Manage" with more specific actions (create, search, update, send) for the listed entities.

Add natural synonyms (SMS marketing, text campaigns, drip campaigns) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Lists, Broadcasts, Templates, Numbers and more" names the domain and several concrete entities, though the verb "Manage" is generic and "and more" leaves minor coverage gaps.	4 / 5
Completeness	Both a clear "what" (manage the listed entities) and an explicit "when" are present, but the "when" is generic rather than packed with concrete trigger phrases, fitting anchor 4 over 5.	4 / 5
Trigger Term Quality	"Project Broadcast" and "Use when the user wants to interact with Project Broadcast data" give good natural-term coverage, but synonyms like SMS, text marketing, or drip campaigns are missing.	4 / 5
Distinctiveness Conflict Risk	"Project Broadcast" is a specific named platform with a clear niche and distinct triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: membranedev/application-skills
Path: skills/project-broadcast/SKILL.md
Commit: f484c82

Reviewed: ~21 hours 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.