Name: poool
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

poool

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

Quality

66%

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/poool/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 body is a well-structured, command-driven integration guide with a solid connection-readiness feedback loop and actionable CLI examples. Its main weaknesses are minor verbosity, unlabeled step references, and a lack of split-out reference material for longer detail like the clientAction state machine.

Dimension	Reasoning	Score
Conciseness	The body is command-focused and mostly efficient, with only minor over-explanation ('auth plumbing', 'burn less tokens') that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	It provides concrete, copy-paste CLI commands (login, connection ensure, action list/run, request proxy) plus an options table, with only minor placeholder gaps (CONNECTION_ID, <actionId>), matching the 'mostly executable guidance; concrete code or commands with minor gaps' anchor.	4 / 5
Workflow Clarity	There is a clear install→authenticate→connect→poll→search→run sequence with an explicit state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), though step numbering is slightly incoherent ('Step 2' is referenced but unlabeled), fitting the 'clear sequence with most checkpoints present; minor validation gaps' anchor.	4 / 5
Progressive Disclosure	With no bundle files present, the single-file body is well-organized into clear sections with no nested references and easy in-file navigation, matching the 'good structure; most content appropriately placed; minor organization gaps' anchor.	4 / 5
	Total	16 / 20 Passed

Description

57%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 includes an explicit Use-when trigger and names a distinct platform niche, but its capability verbs are generic ('manage', 'automate workflows') and keyword coverage is thin. It reads as adequate but not vivid or comprehensive.

Suggestions

Replace generic verbs with concrete Poool-specific actions (e.g., 'Create and segment audiences, configure paywall and registration-wall rules, run A/B test experiences').

Broaden trigger terms to natural phrasings users would say, such as 'paywalls', 'membership walls', 'subscriber segments', or 'Poool audiences'.

Make the 'what' more comprehensive by listing 2-3 specific capabilities rather than 'Manage data, records, and automate workflows'.

Dimension	Reasoning	Score
Specificity	The description names the Poool domain but the actions ('Manage data, records, and automate workflows') are generic rather than concrete, matching the 'names domain but actions minimal or generic' anchor.	2 / 5
Completeness	It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Poool data'), though the 'what' is generic, matching the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	'interact with Poool data' and 'Poool' provide some relevant keywords but coverage is narrow and missing common variations or synonyms, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Poool' is a distinct brand niche with clear triggers, giving mostly distinct identity with only minor overlap risk against generic data-management skills.	4 / 5
	Total	13 / 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/poool/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.