Name: pandle
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

pandle

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

Quality

64%

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

Quality

Content

67%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 provides concrete, executable Membrane CLI guidance with a genuine connection-state feedback loop and good section structure. It is held back by some padded prose, a dangling 'Step 2' reference, and all content being inlined rather than split into reference files.

Suggestions

Trim explanatory filler such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection' to respect the token budget.

Fix the dangling 'skip to Step 2' reference by numbering the main workflow steps explicitly.

Move the 33-entity overview list and the proxy flag table into a separate reference file (e.g. ENTITIES.md) to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Commands are mostly efficient, but padded prose ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') and filler ('Use action names and parameters as needed') could be tightened, matching anchor 3; not a 4 because several unnecessary explanatory sentences remain.	3 / 5
Actionability	Concrete executable commands (install, login, connection ensure, action list/run, request) with a flags table cover the common cases, matching anchor 4; not a 5 because placeholders (CONNECTION_ID, QUERY) and vague lines leave minor gaps.	4 / 5
Workflow Clarity	The install→auth→connect→poll sequence has a real feedback loop (BUILDING polling, CLIENT_ACTION_REQUIRED re-auth, CONFIGURATION_ERROR handling), matching anchor 4; not a 5 because the 'skip to Step 2' reference is dangling and the flow is not fully numbered.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with an external docs link, matching anchor 4; not a 5 because everything is inlined in one ~170-line file (the long entity list and proxy flag table could live in separate reference files).	4 / 5
	Total	15 / 20 Passed

Description

61%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 names its niche and includes both a 'what' and a 'when' clause, but the listed capabilities are generic ('manage data, records, automate workflows') rather than Pandle-specific, limiting specificity and trigger richness.

Suggestions

Replace generic actions with Pandle-specific ones, e.g. 'create invoices, track expenses, reconcile bank transactions, and submit VAT returns'.

Broaden the trigger with natural user phrasings, e.g. 'Use when the user wants to manage Pandle accounting, invoices, expenses, or bank reconciliation.'

Add file-type or entity cues users would say (invoices, bills, VAT returns) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The actions 'Manage data, records, and automate workflows' name the Pandle domain but are generic, matching the anchor 'Names the domain but actions are minimal or generic'; it is not a 3 because no Pandle-specific concrete actions (e.g. invoicing, bank reconciliation) are listed.	2 / 5
Completeness	It has both a 'what' ('Pandle integration. Manage data, records, and automate workflows') and a 'when' ('Use when the user wants to interact with Pandle data'), matching anchor 4; not a 5 because the trigger is a single scenario rather than comprehensive concrete trigger phrases.	4 / 5
Trigger Term Quality	'Pandle' and 'interact with Pandle data' provide some relevant keywords but miss common variations or synonyms users might say, matching the anchor 'Some relevant keywords but missing common variations'; not a 4 because coverage is thin rather than good.	3 / 5
Distinctiveness Conflict Risk	'Pandle' is a clear named niche with a distinct trigger ('Use when the user wants to interact with Pandle data') and minimal conflict risk, matching the anchor 'Clear niche with distinct triggers; minimal conflict risk'.	5 / 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/pandle/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.