Name: postgrid
Rating: 59.2 (1 reviews)
Author: membranedev

postgrid

PostGrid integration. Manage Persons, Organizations, Addresses, Letters, Postcards, Templates and more. Use when the user wants to interact with PostGrid data.

Quality

69%

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/postgrid/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 an efficient, actionable CLI integration guide with a strong connection-setup feedback loop, but it lacks verification checkpoints before irreversible mail/batch operations and stays monolithic rather than splitting reference material into bundled files. Good overall, with a clear gap around pre-action validation.

Suggestions

Add an explicit validation/verification checkpoint before running mail-sending, batch, or mutating proxy requests, e.g. "Before sending Letters/Postcards or running Batches, confirm the recipient and template with the user and inspect the action's outputSchema."

Provide at least one fully-worked end-to-end example with concrete values (a real connection id, action id, and --input payload) so the placeholder substitution is unambiguous.

Move the proxy flag reference table and detailed connection state machine into a bundled reference file (e.g. references/proxy.md) and link to it, tightening the main SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands, tables, and state-handling detail that assumes Claude's competence, with only minor trimmable prose (e.g. the somewhat preachy "Best practices" section).	4 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connect, search, run, and proxy with a flags table, but commands rely on placeholders (CONNECTION_ID, <actionId>) and lack a fully-worked end-to-end example with real values.	4 / 5
Workflow Clarity	There is a clear install→login→connect→search→run sequence with a genuine connection-state feedback loop, but PostGrid sends physical mail (irreversible) and exposes Batch/Job and proxy POST/PUT/DELETE with no validation/verification checkpoint before acting, so the destructive/batch cap applies.	3 / 5
Progressive Disclosure	The body has good section headers and no nested references, but it is a monolithic ~143-line single file with no bundle files and a redundant "Popular actions" section, so it is well-organized rather than optimally split.	4 / 5
	Total	15 / 20 Passed

Description

70%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 clearly identifies a niche platform and includes an explicit "Use when..." trigger, but its action vocabulary is narrow (a single generic "Manage") and the trigger clause is generic rather than enumerating concrete use cases. It is solid but not exemplary.

Suggestions

Replace the single generic verb "Manage" with a few concrete actions, e.g. "Create and send Letters and Postcards, manage Persons, Organizations, and Addresses, and run Batches".

Make the "Use when..." clause enumerate concrete triggers, e.g. "Use when the user wants to send letters or postcards, manage contacts and addresses, or run direct-mail batches via PostGrid".

Add the natural synonym "direct mail" so the description activates on the phrasing users actually use for this domain.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Addresses, Letters, Postcards, Templates and more" lists several concrete entities but relies on a single generic action verb ("Manage"), so it names the domain with limited action variety rather than several distinct actions.	3 / 5
Completeness	Both the "what" ("PostGrid integration. Manage ...") and an explicit "Use when the user wants to interact with PostGrid data" trigger are present, but the "when" is generic rather than enumerating concrete trigger phrases.	4 / 5
Trigger Term Quality	Natural entity terms users would say (Letters, Postcards, Addresses, PostGrid) are present, but common synonyms such as "direct mail" or "mail merge" are missing.	4 / 5
Distinctiveness Conflict Risk	"PostGrid integration" is a clear niche tied to a specific named platform with a distinctive trigger, with only minor overlap risk against a generic direct-mail skill.	4 / 5
	Total	15 / 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/postgrid/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.