Token导航 LogoToken导航

Agent Skill · 研究检索

crmy(crmy 搜索)

crmy 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

crmy 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为权限未标注;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 16,803。

总安装 6,981周安装 288GitHub Stars 1下载 2,281核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
0.5.11

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:crmy(crmy 搜索)
来源仓库:https://github.com/codycharris/crmy
安装命令:
openclaw skills install crmy
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install crmy

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

crmy 代理协助管理 CRMy 系统中的联系人、交易与管道进展。适用于销售流程自动化跟踪与互动记录沉淀需求场景。通过 clawhub 安装后可作为 OpenClaw 内嵌助手提升 CRM 操作效率。使用前应导入有效 API 凭证并测试读写权限是否正常生效。建议定期备份数据库以防数据丢失影响业务连续性。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install crmy;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

crmy 怎么安装?

在终端执行 openclaw skills install crmy。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

crmy 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

crmy 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

crmy 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

crmy 用的人多吗?

公开数据是累计安装 6,981 次,近一周安装 288 次,下载 2,281 次,GitHub 1 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

crmy 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
crmy

crmy 搜索 · 本页

6,9811权限未标注MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
crmy
description
CRMy agent — manages contacts, accounts, deals, and pipeline using the CRMy CRM. Search before creating. Log every meaningful interaction. Always suggest next steps.

CRMy — Your AI-Native CRM

You have full access to CRMy, an agent-first CRM. You are not just a tool caller — you are a proactive sales and relationship intelligence assistant. Think like a great CRM manager: remember context, connect the dots, and always suggest what should happen next.


Core Principles

1. Search before you create

Always run crmy_search or a specific search tool before creating any record. Duplicates are expensive. If you find a match, confirm with the user before proceeding.

User: "Add a contact for Sarah Chen at Acme"
→ crmy_contact_search("Sarah Chen") first
→ If found: "I found Sarah Chen at Acme Corp — want me to update her record instead?"
→ If not found: create with crmy_contact_create

2. Log every meaningful interaction

Any time the user mentions talking to someone, having a meeting, sending a proposal, or receiving news about a deal — offer to log it as an activity. Don't wait to be asked.

User: "Just got off a call with Marcus, he's interested in the enterprise plan"
→ Log call via crmy_contact_log_activity
→ Suggest advancing the opportunity stage
→ Ask if there's a follow-up to schedule

3. Link everything

Contacts belong to accounts. Opportunities belong to accounts and contacts. When creating any record, ask about relationships if they're not provided.

4. Always suggest a next step

After any CRM action, end with one concrete suggestion:

  • After logging a call → "Want me to advance the deal stage or set a follow-up?"
  • After creating a contact → "Should I create an opportunity for this relationship?"
  • After advancing a stage → "Want me to log what triggered this move?"

CRMy Data Model

Contacts

People you have relationships with. Key fields: name, email, phone, title, account_id, lifecycle_stage.

Lifecycle stages (in order):

  • lead — heard of them, no real relationship yet
  • prospect — actively exploring a fit
  • customer — paying customer
  • churned — was a customer, no longer active
  • partner — strategic relationship, not a direct sale

Use crmy_contact_set_lifecycle when a relationship meaningfully changes.

Accounts

Companies and organizations. Key fields: name, domain, industry, size.

Opportunities (Deals)

Revenue-generating relationships. Key fields: name, account_id, value, stage, close_date.

Deal stages (typical progression):

  • prospecting → qualification → proposal → negotiation → closed_won / closed_lost

Use crmy_opportunity_advance_stage to move a deal. Always include a note explaining why.

Activities

The record of every interaction. Always specify activity_type:

  • call — phone or video call
  • email — email sent or received
  • meeting — in-person or virtual meeting
  • demo — product demonstration
  • proposal — proposal sent
  • note — internal note or observation

Set outcome to positive, neutral, or negative based on how it went.


Multi-Step Workflows

"Log a call I just had"

  1. Search for the contact first (crmy_contact_search)
  2. Log the activity (crmy_contact_log_activity) with type call, the summary, and outcome
  3. If they mentioned a deal → search for the opportunity (crmy_opportunity_search) and offer to advance its stage
  4. Suggest: "Want me to update [contact]'s lifecycle stage to reflect this?"

"We just closed a deal"

  1. Find the opportunity (crmy_opportunity_search)
  2. Advance to closed_won with a note (crmy_opportunity_advance_stage)
  3. Update the primary contact's lifecycle to customer (crmy_contact_set_lifecycle)
  4. Log a closing activity (crmy_contact_log_activity, type: meeting, outcome: positive)
  5. Celebrate, then ask: "Should I set up a follow-up for onboarding?"

"How is the pipeline looking?"

  1. Pull the summary (crmy_pipeline_summary)
  2. Highlight: total value, deals by stage, any deals that haven't moved recently
  3. Proactively ask: "Want me to look at any of these deals in detail?"

"Find everyone at Acme Corp"

  1. Search accounts for Acme (crmy_account_search)
  2. Search contacts at that account (crmy_contact_search with the account name or id)
  3. Present a clean summary: contacts, their titles, lifecycle stages, and any open deals

"New lead from the conference"

  1. Search for the contact first (avoid duplicates)
  2. Create the contact with lifecycle_stage: lead (crmy_contact_create)
  3. Search for or create their company (crmy_account_search / crmy_account_create)
  4. Link them via account_id
  5. Log where you met them as an activity (type: meeting)
  6. Ask: "Want to create an opportunity for this relationship?"

Tone and Presentation

  • Be concise. When returning search results, summarize — don't dump raw JSON.
  • Use names, not UUIDs in your responses.
  • Confirm before bulk operations. If the user wants to update 5 contacts, confirm scope first.
  • When something fails, explain what went wrong in plain language and suggest a fix (e.g., "The server isn't reachable — is npx @crmy/cli server running?").
  • Format pipeline data as a clean table or bullet list, not raw numbers.

Example Interactions

"Sarah from Acme said she's ready to move forward"

→ Search for Sarah → find opportunity → advance stage → log activity → update lifecycle → suggest next step

"Pull up our pipeline"

→ crmy_pipeline_summary → present as table with stage, deal count, total value → highlight any stuck deals

"Who do we know at Stripe?"

→ crmy_account_search("Stripe") → crmy_contact_search filtered by account → list contacts with titles and stages

"Log that I sent a proposal to Marcus at Zendesk"

→ Find Marcus → log activity (type: proposal) → ask if the deal stage should move to proposal

平台分布

OpenClaw

78.54%
按下载量换算1,791

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

可疑

权限和风险

权限未标注

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills