← 返回 Skills 市场
brucegutman

Pipeworx could-have-been-email

作者 Bruce Gutman · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
75
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install pipeworx-could-have-been-email
功能描述
Analyzes meeting transcripts to determine if the discussion could have been an email, returning filler word count and decisions.
安全使用建议
This skill appears to send meeting transcripts to an external service (gateway.pipeworx.io) and mentions an X-API-Key, but the skill metadata doesn't declare any required credentials or explain where the key comes from. Before installing: 1) Ask the publisher for a homepage, privacy policy, and owner identity. 2) Require the skill to declare the exact env var name for the API key and explain key scopes and storage recommendations. 3) Confirm what transcript data is transmitted, how long it is stored, and whether PII will be retained. 4) Avoid sending sensitive meeting content until you verify the service and the API-key handling. Providing those clarifications would move this assessment toward benign; absent them, treat the skill as suspicious.
功能分析
Type: OpenClaw Skill Name: pipeworx-could-have-been-email Version: 1.0.0 The skill provides a wrapper for an external MCP server (https://gateway.pipeworx.io/could-have-been-email/mcp) to analyze meeting transcripts for filler words and efficiency. The behavior is clearly aligned with the stated purpose in SKILL.md, and there are no indicators of malicious intent, data exfiltration of sensitive system files, or prompt injection.
能力标签
requires-sensitive-credentials
能力评估
Purpose & Capability
The description says it analyzes meeting transcripts and returns filler-word counts and decisions — that capability plausibly requires calling an external service. However SKILL.md explicitly states it "requires X-API-Key" and points to an external gateway (gateway.pipeworx.io) while the skill metadata lists no required environment variables or primary credential. The missing API-key declaration is an incoherence.
Instruction Scope
The runtime instructions are minimal but imply sending meeting transcripts to an external MCP endpoint. They do not specify how the X-API-Key is supplied, what data is sent, or any privacy/retention behavior. Any skill that transmits meeting transcripts externally should explicitly document required credentials and data handling; this one does not.
Install Mechanism
No install spec and no code files are present (instruction-only). That minimizes on-disk installation risk — nothing is downloaded or executed locally by the skill itself.
Credentials
SKILL.md states an API key is required (X-API-Key) but the registry entry declares no env vars or primary credential. Requesting an external API key is plausible, but an undisclosed credential requirement is disproportionate and unclear. There's no indication what scopes/permissions that key has or where it should be stored.
Persistence & Privilege
The skill is not always-on and uses default autonomous invocation settings. There's no indication it requests permanent agent changes or elevated system privileges. Note: autonomous invocation combined with an external API (and an API key) increases data-exfiltration risk, but autonomous invocation itself is expected.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install pipeworx-could-have-been-email
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /pipeworx-could-have-been-email 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.0
Initial release
元数据
Slug pipeworx-could-have-been-email
版本 1.0.0
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 1
常见问题

Pipeworx could-have-been-email 是什么?

Analyzes meeting transcripts to determine if the discussion could have been an email, returning filler word count and decisions. 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 75 次。

如何安装 Pipeworx could-have-been-email?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install pipeworx-could-have-been-email」即可一键安装,无需额外配置。

Pipeworx could-have-been-email 是免费的吗?

是的,Pipeworx could-have-been-email 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Pipeworx could-have-been-email 支持哪些平台?

Pipeworx could-have-been-email 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Pipeworx could-have-been-email?

由 Bruce Gutman(@brucegutman)开发并维护,当前版本 v1.0.0。

💬 留言讨论