Name: courier
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

courier

Courier integration. Manage data, records, and automate workflows. Use when the user wants to interact with Courier 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/courier/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 clear, state-aware connection workflow including a feedback loop. Its main weaknesses are marketing-style padding in the prose and slightly thin validation guidance for action execution.

Suggestions

Trim the opening overview paragraph and the "focus on integration logic rather than auth plumbing" commentary to reduce padding.

Add a brief validation note after `membrane action run` (e.g. inspect `output` and error fields, handle non-2xx) since actions can be destructive.

Avoid repeating the `action list --intent=QUERY` command in both "Searching for actions" and "Popular actions"; consolidate to remove redundancy.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands throughout, but the opening paragraph ("streamline their notification logic and improve the user experience") and lines like "so you can focus on the integration logic rather than auth plumbing" add marketing-style padding Claude does not need, matching the score-3 anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for the full flow (install, login, connection ensure, action list/run, request proxy) plus a complete flag table, matching the score-5 anchor of fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The connection setup has a clear sequence with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a retry-after-action feedback loop, but action-execution lacks output validation guidance, leaving it just short of the score-5 anchor.	4 / 5
Progressive Disclosure	Content is well-organized into clearly labeled sections with no bundle files to reference; as a single-purpose CLI usage guide it has no content that clearly belongs in separate files, though at ~150 lines some operational detail could be split out, matching score-4 rather than the lean score-5.	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 correctly answers both what and when and is third-person, but its action verbs are generic ("manage data, records, automate workflows") and it omits the notification-channel terms (email, SMS, push, in-app) that users would naturally say.

Suggestions

Replace generic verbs with Courier-specific concrete actions, e.g. "Send notifications across email, SMS, push, and in-app channels, manage templates, lists, and recipients, and audit message delivery."

Add natural trigger terms users would say, such as "send a notification", "email/SMS/push notification", or "notification template", not just "interact with Courier data".

Tighten the 'when' clause to concrete triggers, e.g. "Use when the user wants to send or troubleshoot notifications via Courier."

Dimension	Reasoning	Score
Specificity	It names the domain ("Courier 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 actions.	2 / 5
Completeness	Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Courier data") are present, though the 'when' could be more specific, matching the score-4 anchor and above the score-3 (missing/weak when) case.	4 / 5
Trigger Term Quality	"Courier" and "interact with Courier data" are relevant natural keywords, but common notification-specific synonyms users would actually say (notifications, email, SMS, push) are missing, so it does not reach score 4.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Courier platform gives it a clear niche with low conflict risk, but the generic "manage data, records, automate workflows" phrasing keeps it just short of the fully-distinct score-5 anchor.	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/courier/SKILL.md
Commit: f484c82

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