Name: poof
Rating: 58.4 (1 reviews)
Author: membranedev

poof

Poof integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Poof data.

Quality

67%

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

Quality

Content

60%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 technically actionable with a well-sequenced, validated Membrane connection workflow, but it is undermined by a leaked AI apology artifact, an intro that contradicts the description, and filler lines. It also never demonstrates a Poof-specific action, relying entirely on generic Membrane boilerplate.

Suggestions

Remove the leaked 'I am sorry, I cannot provide an API or developer documentation URL...' sentence and the 'disappearing message app, like Snapchat' intro, which contradict the CRM-style description and waste tokens.

Delete the filler line 'When to use which actions: Use action names and parameters as needed.' and replace it with real Poof action examples (e.g., a concrete `membrane action list --intent='create deal'` call and its output).

Add a validate/verify checkpoint after running actions (e.g., inspect the `output` field and handle errors) so the action-execution workflow matches the connection workflow's validation rigor.

Dimension	Reasoning	Score
Conciseness	Several padded/wrong sections waste tokens: the leaked AI apology ('Official docs: I am sorry, I cannot provide an API or developer documentation URL...'), an unrelated 'disappearing message app, like Snapchat' intro that contradicts the description, and the filler line 'When to use which actions: Use action names and parameters as needed.' Not a 3 because these are more than minor over-explanation — one is a non-answer artifact; not a 1 because the Membrane CLI sections below are mostly lean executable commands.	2 / 5
Actionability	Concrete copy-paste commands cover install, login, connection ensure/wait, action list/run, and proxy requests with a flags table. Not a 5 because no Poof-specific action is demonstrated end-to-end — everything uses unresolved QUERY/CONNECTION_ID/<actionId> placeholders and generic Membrane boilerplate; not a 3 because the commands are genuinely executable, not pseudocode.	4 / 5
Workflow Clarity	A clear sequence (install → auth → connect → poll state → handle CLIENT_ACTION_REQUIRED → search → run → proxy) with validation checkpoints for the connection (poll until READY, branch on CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR/SETUP_FAILED). Not a 5 because action-result handling has no validate/fix/retry feedback loop; not a 3 because the connection workflow genuinely includes explicit state-based validation.	4 / 5
Progressive Disclosure	Single self-contained SKILL.md (no references/scripts/assets bundle exists) organized into clear headed sections. Not a 5 because it exceeds the simple-skill line and contains generic Membrane boilerplate that could live in a shared reference, plus an oddly placed 'Poof Overview' tree; not a 3 because sections are well-structured and there is no nested/buried-reference problem.	4 / 5
	Total	14 / 20 Passed

Description

75%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 cleanly answers both what and when, names a distinctive app plus concrete entities, and uses third person. It is held back from the top band by a single generic verb ('Manage') applied to everything, an 'and more' over-claim, and a trigger clause that is slightly generic.

Suggestions

Replace the single 'Manage' verb with differentiated concrete actions (e.g., 'Create and update Persons, Organizations, Deals, Leads, Projects, and Activities') to lift specificity.

Tighten the trigger clause with concrete phrases users would actually say, e.g., 'Use when the user mentions Poof, or wants to create/update Persons, Deals, Leads, Projects, or Activities in Poof.'

Drop the 'and more' over-claim or replace it with the specific additional capability it implies.

Dimension	Reasoning	Score
Specificity	It enumerates six concrete domains ('Persons, Organizations, Deals, Leads, Projects, Activities') but collapses them under a single generic verb ('Manage ... and more'), so it lists several specifics without distinct, comprehensive actions. Not a 5 because the actions are not differentiated and 'and more' is an over-claim; not a 3 because it names far more than 1-2 concrete items.	4 / 5
Completeness	Both 'what' (Poof integration, manage the listed entities) and 'when' (Use when the user wants to interact with Poof data) are explicitly present. Not a 5 because the 'when' clause is generic rather than packed with concrete trigger phrases; not a 3 because the 'when' is explicit, not merely implied.	4 / 5
Trigger Term Quality	Natural trigger phrasing ('Use when the user wants to interact with Poof data') plus the app name and six entity-type keywords give good coverage. Not a 5 because 'interact with Poof data' is somewhat generic and lacks synonyms/variations users might say; not a 3 because it clearly surpasses a single keyword like 'Works with PDF files'.	4 / 5
Distinctiveness Conflict Risk	The 'Poof' app name and entity list anchor it to a clear niche with low conflict risk. Not a 5 because the CRM-style entities (Deals, Leads, Organizations) could overlap with generic CRM skills; not a 3 because the distinctive 'Poof' brand name substantially reduces overlap.	4 / 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/poof/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.