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

Blog Docs Log in Get started

paubox

Paubox integration. Manage data, records, and automate workflows. Use when the user wants to interact with Paubox data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/paubox/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 content is a strong, actionable integration guide with concrete Membrane CLI commands, a clear connect-to-run workflow, and explicit state-based error handling. It is concise and well-organized, with only minor padding and a few opportunities to make validation checkpoints more explicit.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste-ready commands and short prose, e.g. install/auth/connection sections. Minor padding ("so you can focus on the integration logic rather than auth plumbing", "This will burn less tokens") and the brief Paubox intro keep it from a 5.	4 / 5
Actionability	It provides concrete executable commands throughout (npm install, membrane login, connection ensure, action run, the proxy flags table). Most guidance is copy-paste ready with only minor placeholders like CONNECTION_ID, fitting anchor 4 rather than 5 because a couple of common-case examples could be more fully spelled out.	4 / 5
Workflow Clarity	The connect-to-run flow is clearly sequenced (install -> auth -> connect -> poll for state -> search actions -> run) with state-based branching (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop. Not 5 because some checkpoints are implicit rather than framed as explicit validate->fix->retry steps.	4 / 5
Progressive Disclosure	The skill is a single well-organized SKILL.md with clear section headers (Overview, Working with Paubox, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) and no nested references. It is well-structured but the proxy/API-reference detail is all inline with nothing offloaded, so it fits anchor 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

62%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 names a clear niche (Paubox) and includes an explicit Use-when clause, so it answers both what and when. Its weakness is generic, non-concrete action language and missing the natural trigger terms (HIPAA email, secure email, PHI) users would actually say.

Suggestions

Replace generic verbs with concrete Paubox actions, e.g. "Send HIPAA-compliant email, manage message drafts, and access account/user/organization records."

Add natural trigger terms to the Use-when clause, e.g. "Use when the user wants to send secure or HIPAA-compliant email, manage Paubox drafts, or look up Paubox account/user/organization records."

Tie the trigger to the PHI/healthcare context so it activates on the right requests and avoids overlap with generic email skills.

Dimension	Reasoning	Score
Specificity	Names the Paubox domain and a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete Paubox capabilities like email, drafts, or accounts. It clears anchor 3 but not 4 because coverage is non-specific.	3 / 5
Completeness	Both "what" (Paubox integration; manage data, records, automate workflows) and "when" ("Use when the user wants to interact with Paubox data") are present and explicit. Not 5 because the "when" clause lacks concrete trigger contexts (e.g., sending HIPAA/secure email).	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Paubox data" includes the brand keyword and "data", but misses the natural terms a user would actually say (HIPAA email, secure email, PHI). Anchor 3 fits: some relevant keywords, missing common variations.	3 / 5
Distinctiveness Conflict Risk	The brand name "Paubox" in both the what and when clauses gives it a clear niche with low conflict risk, but the generic verbs ("manage data, records") keep it from being fully distinct. Not 5 because the trigger phrasing is not tightly scoped to Paubox-specific use cases.	4 / 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/paubox/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.