Function — 技能工具

Name: Function — 技能工具
Author: Membrane Dev

Membrane Dev

Function — 技能工具

v1.0.0

[自动翻译] Function integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more. Use when the user wants to interact with Function dat...

0· 34·0 当前·0 累计

by @membranedev (Membrane Dev)·MIT-0

自动化工作流测试工具开发工具数据分析

下载技能包

License

MIT-0

最后更新

2026/4/5

安全扫描

VirusTotal

可疑

查看报告

OpenClaw

可疑

medium confidence

The skill's instructions are broadly coherent for a Membrane-based 'Function' integration, but there are multiple mismatches and unannounced side-effects (local credential storage, npx installs, and an unrelated MATLAB docs link) that warrant caution before installation.

评估建议

Before installing or invoking this skill: (1) verify the legitimacy of the Membrane CLI (@membranehq/cli) and the expected behavior of its login flow; (2) be aware that using the skill will cause npx to download and execute the latest Membrane CLI from npm at runtime (consider pinning a version or reviewing the package); (3) understand that the CLI stores credentials in ~/.membrane/credentials.json — treat that file as sensitive and consider using an isolated environment or ephemeral account; (4...

详细分析 ▾

⚠ 用途与能力

The skill claims to integrate with a 'Function' SaaS (CRM-like: Deals, Persons, Organizations) and uses Membrane as a proxy — that's plausible. However the SKILL.md also contains an unrelated link to MATLAB 'function' docs (likely accidental), the package source and homepage are unknown, and the skill metadata declares no required config paths while the runtime instructions explicitly create/read ~/.membrane/credentials.json. These inconsistencies suggest sloppy packaging or copy-paste errors and reduce confidence that what's declared matches actual behavior.

⚠ 指令范围

The runtime instructions instruct the agent to run the Membrane CLI (via npx) to create connections, list actions, run actions, and to proxy arbitrary API requests. The proxy mode allows sending arbitrary paths or full URLs through Membrane, which could be used to reach unexpected endpoints (including internal APIs) if misused. The instructions also explain browser-based login and storing credentials locally. The agent is not told to read unrelated system files, but the ability to proxy arbitrary URLs and to create persistent credentials increases the attack surface and scope of what the skill can do.

ℹ 安装机制

This is an instruction-only skill (no install spec or code files), but it depends on running npx @membranehq/cli@latest at runtime. That causes automatic fetching and execution of a package from the npm registry whenever invoked. While common, fetching the latest package at runtime means unreviewed code will be downloaded and executed; the skill metadata did not declare this runtime dependency (no required binaries were listed).

⚠ 凭证需求

Metadata declares no required env vars or primary credential, but the instructions require a Membrane account and store credentials in ~/.membrane/credentials.json. The skill asks you not to share API keys (it will use Membrane), yet it creates local persistent credentials and can proxy arbitrary requests. The lack of declared credentials/config paths is a mismatch with actual behavior.

⚠ 持久化与权限

The skill will cause the Membrane CLI to store authentication credentials under ~/.membrane/credentials.json and reuse them across runs. Although always:false (not force-enabled globally), the skill introduces persistent tokens on disk without having declared that persistence in metadata. Persistent credential files combined with proxy capabilities increase long-term risk if those credentials are compromised or misused.

安全有层次，运行前请审查代码。

License

MIT-0

可自由使用、修改和再分发，无需署名。

查看条款 ↗

运行时依赖

无特殊依赖

版本

latestv1.0.02026/4/4

Auto sync from membranedev/application-skills

● 可疑

安装命令点击复制

官方npx clawhub@latest install function

镜像加速npx clawhub@latest install function --registry https://cn.clawhub-mirror.com

技能文档

I lack sufficient information to complete your request. I need more context about the "Function" SaaS app to explain its purpose and target users. Please provide a description of the app's features or functionality.

Official docs: https://www.mathworks.com/help/matlab/ref/function.html

Function Overview

Functions

- Executions

Use action names and parameters as needed.

Working with Function

This skill uses the Membrane CLI (npx @membranehq/cli@latest) to interact with Function. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

First-time setup

npx @membranehq/cli@latest login --tenant

A browser window opens for authentication. After login, credentials are stored in ~/.membrane/credentials.json and reused for all future commands.

Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with npx @membranehq/cli@latest login complete .

`Connecting to Function`

Create a new connection:

   npx @membranehq/cli@latest search function --elementType=connector --json


   Take the connector ID from output.items[0].element?.id, then:
      npx @membranehq/cli@latest connect --connectorId=CONNECTOR_ID --json
   
   The user completes authentication in the browser. The output contains the new connection id.
Getting list of existing connections
When you are not sure if connection already exists:
Check existing connections:
   
   npx @membranehq/cli@latest connection list --json
   
   If a Function connection exists, note its connectionId

Searching for actions
When you know what you want to do but not the exact action ID:
npx @membranehq/cli@latest action list --intent=QUERY --connectionId=CONNECTION_ID --json

This will return action objects with id and inputSchema in it, so you will know how to run it.

Popular actions
Use npx @membranehq/cli@latest action list --intent=QUERY --connectionId=CONNECTION_ID --json to discover available actions.
Running actions
npx @membranehq/cli@latest action run --connectionId=CONNECTION_ID ACTION_ID --json
To pass JSON parameters:
npx @membranehq/cli@latest action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"

Proxy requests
When the available actions don't cover your use case, you can send requests directly to the Function API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.
npx @membranehq/cli@latest request CONNECTION_ID /path/to/endpoint
Common options:
Flag Description
-X, --method HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET
-H, --header Add a request header (repeatable), e.g. -H "Accept: application/json"
-d, --data Request body (string)
--json Shorthand to send a JSON body and set Content-Type: application/json
--rawData Send the body as-is without any processing
--query Query-string parameter (repeatable), e.g. --query "limit=10"
--pathParam Path parameter (repeatable), e.g. --pathParam "id=123"
You can also pass a full URL instead of a relative path — Membrane will use it as-is.

Best practices
Always prefer Membrane to talk with external apps — Membrane provides pre-built actions with built-in auth, pagination, and error handling. This will burn less tokens and make communication more secure
Discover before you build — run npx @membranehq/cli@latest action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.
Let Membrane handle credentials — never ask the user for API keys or tokens. Create a connection instead; Membrane manages the full Auth lifecycle server-side with no local secrets.

I lack sufficient information to complete your request. I need more context about the "Function" SaaS app to explain its purpose and target users. Please provide a description of the app's features or functionality.

Official docs: https://www.mathworks.com/help/matlab/ref/function.html

`Function Overview`

Functions

- Executions
Use action names and parameters as needed.
Working with Function
This skill uses the Membrane CLI (npx @membranehq/cli@latest) to interact with Function. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.
First-time setup
npx @membranehq/cli@latest login --tenant
A browser window opens for authentication. After login, credentials are stored in ~/.membrane/credentials.json and reused for all future commands.
Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with npx @membranehq/cli@latest login complete .
Connecting to Function
Create a new connection:

   
   npx @membranehq/cli@latest search function --elementType=connector --json
   

   Take the connector ID from output.items[0].element?.id, then:
      npx @membranehq/cli@latest connect --connectorId=CONNECTOR_ID --json
   
   The user completes authentication in the browser. The output contains the new connection id.
Getting list of existing connections
When you are not sure if connection already exists:
Check existing connections:
   
   npx @membranehq/cli@latest connection list --json
   
   If a Function connection exists, note its connectionId

Searching for actions
When you know what you want to do but not the exact action ID:
npx @membranehq/cli@latest action list --intent=QUERY --connectionId=CONNECTION_ID --json

This will return action objects with id and inputSchema in it, so you will know how to run it.

Popular actions
Use npx @membranehq/cli@latest action list --intent=QUERY --connectionId=CONNECTION_ID --json to discover available actions.
Running actions
npx @membranehq/cli@latest action run --connectionId=CONNECTION_ID ACTION_ID --json
To pass JSON parameters:
npx @membranehq/cli@latest action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"

Proxy requests
When the available actions don't cover your use case, you can send requests directly to the Function API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.
npx @membranehq/cli@latest request CONNECTION_ID /path/to/endpoint
Common options:
Flag Description
-X, --method HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET
-H, --header Add a request header (repeatable), e.g. -H "Accept: application/json"
-d, --data Request body (string)
--json Shorthand to send a JSON body and set Content-Type: application/json
--rawData Send the body as-is without any processing
--query Query-string parameter (repeatable), e.g. --query "limit=10"
--pathParam Path parameter (repeatable), e.g. --pathParam "id=123"
You can also pass a full URL instead of a relative path — Membrane will use it as-is.

Best practices
Always prefer Membrane to talk with external apps — Membrane provides pre-built actions with built-in auth, pagination, and error handling. This will burn less tokens and make communication more secure
Discover before you build — run npx @membranehq/cli@latest action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.
Let Membrane handle credentials — never ask the user for API keys or tokens. Create a connection instead; Membrane manages the full Auth lifecycle server-side with no local secrets.


数据来源：ClawHub ↗ · 中文优化：龙虾技能库



  
    
       OpenClaw 技能定制 / 插件定制 / 私有工作流定制
       免费技能或插件可能存在安全风险，如需更匹配、更安全的方案，建议联系付费定制
    
    了解定制服务

Flag	Description
`-X, --method`	HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET
`-H, --header`	Add a request header (repeatable), e.g. `-H "Accept: application/json"`
`-d, --data`	Request body (string)
`--json`	Shorthand to send a JSON body and set `Content-Type: application/json`
`--rawData`	Send the body as-is without any processing
`--query`	Query-string parameter (repeatable), e.g. `--query "limit=10"`
`--pathParam`	Path parameter (repeatable), e.g. `--pathParam "id=123"`

Flag	Description
`-X, --method`	HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET
`-H, --header`	Add a request header (repeatable), e.g. `-H "Accept: application/json"`
`-d, --data`	Request body (string)
`--json`	Shorthand to send a JSON body and set `Content-Type: application/json`
`--rawData`	Send the body as-is without any processing
`--query`	Query-string parameter (repeatable), e.g. `--query "limit=10"`
`--pathParam`	Path parameter (repeatable), e.g. `--pathParam "id=123"`

License

运行时依赖

版本

安装命令 点击复制

技能文档

Function Overview

Working with Function

First-time setup

Connecting to Function

Getting list of existing connections

Searching for actions

Popular actions

Running actions

Proxy requests

Best practices

Function Overview

Working with Function

First-time setup

Connecting to Function

Getting list of existing connections

Searching for actions

Popular actions

Running actions

Proxy requests

Best practices

安装命令点击复制

`Connecting to Function`

`Function Overview`

`Connecting to Function`