Name: function
Rating: 52.8 (1 reviews)
Author: membranedev

function

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

Quality

58%

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

Quality

Content

61%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 Membrane CLI integration guidance is concrete and executable, but the body is contaminated by a leaked LLM clarification paragraph and an incorrect MATLAB documentation link that undermine credibility and waste context. Adding validation checkpoints and removing the placeholder/wrong-reference content would substantially raise quality.

Suggestions

Remove the leaked placeholder text ('I lack sufficient information to complete your request...') and the incorrect MATLAB documentation link, which refer to the wrong 'function' concept.

Add validation checkpoints after destructive/batch operations (e.g., confirm a connection was created and verify action output before proceeding) to raise workflow clarity above 3.

Fill the empty 'Function Overview' with the actual Function action categories instead of the placeholder 'Executions' list, or remove the section to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The Membrane CLI section is lean and command-focused, but the leaked LLM clarification paragraph, the near-empty 'Function Overview', and padded best-practice rationale waste tokens that could be trimmed.	3 / 5
Actionability	Provides concrete, copy-paste-ready `npx @membranehq/cli` commands with a full proxy flag table, with only minor gaps such as no concrete Function action example and a vague overview line.	4 / 5
Workflow Clarity	The setup→connect→search→run sequence is present, but there are no validation checkpoints (e.g., confirming a connection succeeded), and proxy/action-run can be destructive, capping clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Single self-contained file with clear sections and no external bundle needed, but the empty overview, stray MATLAB doc link, and leaked placeholder paragraph leave minor organization gaps.	4 / 5
	Total	14 / 20 Passed

Description

55%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 covers both what and when and lists concrete CRM-style entities, but relies on the generic, highly overloaded word 'Function' as its primary trigger, undermining distinctiveness and trigger quality. A more explicit, branded trigger clause with synonyms would markedly improve it.

Suggestions

Add concrete action verbs beyond the generic 'Manage' (e.g., 'Create, update, and query Deals, Persons, and Organizations') to raise specificity.

Rewrite the 'Use when...' clause with concrete natural triggers (e.g., 'Use when the user wants to manage CRM deals, contacts, leads, or pipelines in Function') and add the app category so it is not confused with programming or math 'function' concepts.

Disambiguate the product name 'Function' from generic 'function' usage to reduce conflict risk with unrelated skills.

Dimension	Reasoning	Score
Specificity	Enumerates concrete entities ('Deals, Persons, Organizations, Leads, Projects, Pipelines') but the only action verb is the generic 'Manage', so it names the domain with concrete objects yet minimal action specificity.	3 / 5
Completeness	Both a 'what' (manage the listed entities) and an explicit 'Use when...' clause are present, but the 'when' is generic ('interact with Function data') rather than concrete trigger phrases, so it stops short of a 5.	4 / 5
Trigger Term Quality	Entity names are natural terms, but the trigger 'Function' is a generic English word overloaded with programming/math meanings, and the clause 'interact with Function data' is circular with no synonyms or file extensions.	3 / 5
Distinctiveness Conflict Risk	'Function' is a heavily overloaded generic term (the body even cites MATLAB's function docs), creating very broad overlap and high conflict risk with unrelated skills.	2 / 5
	Total	12 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: membranedev/application-skills
Path: skills/function/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.