Name: postalytics
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

postalytics

Postalytics integration. Manage Organizations. Use when the user wants to interact with Postalytics data.

Quality

65%

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

Quality

Content

68%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 content is actionable and well-structured CLI integration guidance with strong connection-setup feedback loops, but it caps on workflow clarity because destructive action/proxy runs lack validation checkpoints, and it stays a single inline file rather than splitting reference material. Adding a validation step for destructive operations and trimming the redundant action-list section would raise the score.

Suggestions

Add an explicit validation/dry-run checkpoint before destructive action runs or proxy requests (e.g., 'For POST/PUT/DELETE, run a GET or --dry-run first to confirm the target'), to lift workflow_clarity above the destructive-operations cap.

Include at least one concrete Postalytics-specific worked example (e.g., 'membrane action list --intent="create campaign" --connectionId=... --json') instead of only the generic 'QUERY' placeholder.

Remove the redundant 'Popular actions' section that repeats the 'action list' command already shown under 'Searching for actions', or merge them to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and command-driven with copy-paste bash snippets and a flag table; minor over-explanation (the marketing-style product intro and the 'action list' command shown twice in different sections) keeps it just below level 5.	4 / 5
Actionability	It provides concrete, executable commands for install, login, connection ensure, action run, and proxy requests, but relies on generic placeholders ('QUERY', '{"key": "value"}') with no Postalytics-specific worked example, leaving a minor gap.	4 / 5
Workflow Clarity	Connection setup is well-sequenced with feedback loops (poll state, handle CLIENT_ACTION_REQUIRED, re-poll, inspect CONFIGURATION_ERROR), but action/proxy execution supports destructive verbs (POST/DELETE) with no validation or dry-run checkpoint, so the destructive-operations cap of 3 applies.	3 / 5
Progressive Disclosure	The single file has a clean section structure (Overview, Install, Auth, Connecting, Searching, Running, Proxy, Best practices), but at ~145 lines with all content inline, no external references, and a redundant 'Popular actions' section, it stops short of the level-5 'appropriately split, one-level-deep references' anchor.	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 correctly pairs a what-statement with an explicit 'Use when' trigger and is highly distinctive thanks to the named platform, but it is thin on concrete capabilities and natural-language trigger synonyms. Expanding the action list and trigger terms would lift the lower dimensions.

Suggestions

Replace the single generic 'Manage Organizations' action with 2-3 concrete Postalytics capabilities (e.g., 'Create and manage campaigns, lists, and templates; send postcards and letters; track deliveries').

Broaden trigger terms beyond the brand name to include natural phrases users say, such as 'direct mail', 'postcards', 'letters', 'campaigns', and 'tracking events'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to send or manage direct mail campaigns, postcards, or letters via Postalytics.'

Dimension	Reasoning	Score
Specificity	The description names the Postalytics domain but offers only a single generic action ('Manage Organizations'), matching the 'names the domain but actions are minimal or generic' anchor rather than the 1-2 concrete actions required for a 3.	2 / 5
Completeness	It explicitly states both a 'what' ('Postalytics integration. Manage Organizations.') and a 'when' ('Use when the user wants to interact with Postalytics data.'), but neither is concrete enough to reach the level-5 anchor requiring concrete trigger phrases.	4 / 5
Trigger Term Quality	It surfaces the brand keyword 'Postalytics' and a trigger phrase ('interact with Postalytics data') but misses natural synonyms and variations users would say, such as direct mail, postcards, letters, or campaigns.	3 / 5
Distinctiveness Conflict Risk	'Postalytics' is a unique named platform giving the skill a clear niche with distinct triggers and minimal conflict risk with other skills.	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/postalytics/SKILL.md
Commit: f484c82

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