Name: pancake-crm
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

pancake-crm

Pancake CRM integration. Manage Recordses. Use when the user wants to interact with Pancake CRM 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/pancake-crm/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 highly actionable with concrete, executable Membrane CLI commands and a well-validated connection workflow, but it loses conciseness points to redundant action-discovery sections and could split its reference material into a separate file.

Suggestions

Remove the redundant "Popular actions" section that repeats the `action list` command from "Searching for actions", or merge them into one discovery section.

Add an explicit verification/confirmation step for destructive record operations (e.g., delete) to satisfy the workflow validation expectation.

Move the proxy request flag table and bulk action reference into a separate REFERENCE.md and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and efficient, but it includes notable redundancy: the "Popular actions" section repeats the `action list` command already shown in "Searching for actions", and "Best practices" restates "Discover before you build", which could be tightened.	3 / 5
Actionability	It provides copy-paste-ready commands for every stage — login, connection ensure, polling, action list/run with JSON input, and proxy requests with a full flag table — covering the common cases with executable specifics.	5 / 5
Workflow Clarity	The connect-and-poll workflow has a clear sequence with explicit validation checkpoints and feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll after the user acts); it is not a 5 because destructive record operations (delete) lack explicit verification steps.	4 / 5
Progressive Disclosure	The body is well-organized with clear section headers and one-level structure (no nested references), and no bundle files are needed; it is not a 5 because at over 50 lines the proxy/options reference and duplicated action discovery content could be split out.	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 correctly includes an explicit "Use when" trigger and names a specific product, giving it solid completeness and distinctiveness, but it is weakened by a single vague action ("Manage Recordses") and missing natural entity keywords users would say.

Suggestions

Replace "Manage Recordses" with concrete actions and the real entity names, e.g. "Manage clients, leads, invoices, and proposals in Pancake CRM: create, read, update, delete, and list records."

Add natural trigger terms users actually say, such as "Use when the user wants to manage Pancake CRM clients, leads, invoices, or proposals."

Fix the non-word "Recordses" — use "records" or the specific entity names to avoid confusing trigger matching.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Pancake CRM integration") and a single generic action ("Manage Recordses"), but offers only one minimal, oddly pluralized action with no concrete CRUD detail, matching the anchor where actions are minimal or generic.	2 / 5
Completeness	Both a "what" ("Manage Recordses") and an explicit "when" ("Use when the user wants to interact with Pancake CRM data") are present; it is not a 5 because the "what" is vague and the "when" trigger is generic rather than concrete.	4 / 5
Trigger Term Quality	"Pancake CRM" is a natural product keyword and "interact with Pancake CRM data" is a usable phrase, but the natural entity terms users would actually say (clients, leads, invoices, proposals) are missing and "Recordses" is an unnatural term, leaving common synonyms uncovered.	3 / 5
Distinctiveness Conflict Risk	"Pancake CRM" names a specific product niche with minimal conflict risk, but the generic "interact with Pancake CRM data" trigger keeps it from being a fully distinct, sharply triggered 5.	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/pancake-crm/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.