Name: echtpost-postcards
Rating: 60.8 (1 reviews)
Author: membranedev

echtpost-postcards

EchtPost Postcards integration. Manage Postcards, Campaigns, Templates, Users. Use when the user wants to interact with EchtPost Postcards data.

Quality

71%

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

Quality

Content

71%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 concrete CLI commands and clear sections, performing well on actionability and progressive disclosure. Its main gap is workflow clarity: destructive operations like sending postcards proceed without explicit validation or confirmation checkpoints, capping that dimension.

Suggestions

Add an explicit validation/confirmation step before running destructive actions like send-postcard (e.g., list recipients, confirm count and template, then run) to raise workflow_clarity above 3.

Trim explanatory sentences that restate flag behavior already visible in the command and tables to push conciseness toward 5.

Move the large 'Connecting' branch/state detail into a one-level-deep reference file (e.g., REFERENCE.md) to lift progressive_disclosure to 5.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and tables rather than long prose; assumes Claude's competence and avoids explaining basic concepts. Not a 5 because a few explanatory sentences ('The --wait flag long-polls...', 'This is the fastest way to get a connection') and the generic overview ('Use action names and parameters as needed.') could be trimmed. Not a 3 because padding is minor and the bulk is actionable.	4 / 5
Actionability	Provides fully executable, copy-paste-ready CLI commands for install, login, connection, action discovery/running, and proxying, plus a flag table. Not below 5 because concrete examples cover the common cases with real flags and JSON output guidance.	5 / 5
Workflow Clarity	Sequences install -> auth -> connect -> search -> run, but the connection-readiness branch (READY/BUILDING/CLIENT_ACTION_REQUIRED/ERROR) lacks an explicit validate-then-act checkpoint for batch/destructive operations like send-postcard. The 'send-postcard' action in the popular-actions table is a destructive/batch operation with no verification step, which caps clarity at 3 per the destructive-operations guideline. Not a 4 because a destructive action (sending postcards) has no validation or confirm checkpoint before execution.	3 / 5
Progressive Disclosure	Well-organized sections with clear headers (Install, Authentication, Connecting, Searching, Popular actions, Best practices) and an overview that stays concise; no bundle files exist, so all content is appropriately inline at one level. Not a 5 because there is no external reference structure (e.g., a separate API reference file) for the larger detail blocks, and the body inlines a fair amount of reference-style material. Not a 3 because structure is genuinely good and navigable.	4 / 5
	Total	16 / 20 Passed

Description

71%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 integration and provides both a 'what' and a 'when', scoring well on specificity and distinctiveness. The main weakness is generic trigger-term coverage that lacks natural synonyms or concrete user-facing phrasing.

Suggestions

Add concrete verbs and natural trigger phrases (e.g., 'Send physical postcards, create campaigns, manage address book contacts. Use when the user wants to send postcards, schedule campaigns, or manage EchtPost recipients.').

Include common synonyms the user might actually say (e.g., 'postcards', 'recipients', 'mailings', 'greeting cards') to raise trigger-term quality.

Make the 'when' clause more concrete than 'interact with EchtPost Postcards data' by naming representative tasks.

Dimension	Reasoning	Score
Specificity	Names the domain (EchtPost Postcards) and four concrete objects to manage ('Postcards, Campaigns, Templates, Users'), giving several specific actions; minor gap in that actions are framed as object categories rather than verbs. Not a 5 because the actions are not fully enumerated (e.g., create/send/list not spelled out).	4 / 5
Completeness	Has a clear 'what' ('Manage Postcards, Campaigns, Templates, Users') and an explicit 'when' ('Use when the user wants to interact with EchtPost Postcards data'), but the 'when' is generic and could be more specific (e.g., mention sending postcards, address book). Not a 3 because both halves are explicitly present. Not a 5 because the trigger is not concrete enough.	4 / 5
Trigger Term Quality	Includes the brand term 'EchtPost Postcards' and the trigger phrase 'interact with EchtPost Postcards data', but lacks common synonyms or file-extension-style natural terms users would say. Not a 4 because natural variation is thin. The 'Use when' clause ('Use when the user wants to interact with...') is reasonable but narrow.	3 / 5
Distinctiveness Conflict Risk	A clearly niche brand ('EchtPost Postcards') with distinct, specific triggers and a domain unlikely to overlap with other generic skills; conflict risk is minimal. Not below 5 because the trigger is specific enough to avoid colliding with other skills.	5 / 5
	Total	16 / 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/echtpost-postcards/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.