技能详情（站内镜像，无评论）
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v0.1.0
统计：⭐ 0 · 485 · 2 current installs · 2 all-time installs
⭐ 0
安装量（当前） 2
🛡 VirusTotal ：可疑 · OpenClaw ：可疑
Package：danielfoch/pipedrive-crm-openclaw
安全扫描（ClawHub）
- VirusTotal ：可疑
- OpenClaw ：可疑
OpenClaw 评估
The skill's code and instructions match a Pipedrive API helper, but the registry metadata omits the required credentials/config declarations — this mismatch is unexpected and worth attention before installing.
目的
The skill's name, description, SKILL.md, and scripts all consistently implement a Pipedrive API helper (CRUD, search, pipeline movement, raw request passthrough). However the registry metadata lists no primary credential or required environment variables even though the code and documentation clearly expect PIPEDRIVE_API_TOKEN or PIPEDRIVE_ACCESS_TOKEN and PIPEDRIVE_COMPANY_DOMAIN. That metadata omission is an inconsistency.
说明范围
SKILL.md and the scripts limit actions to Pipedrive API calls and setup prompts. Runtime instructions do not direct the agent to read unrelated local files, system credentials, or call external endpoints beyond Pipedrive. Safety rules in SKILL.md explicitly warn not to echo raw tokens.
安装机制
No install spec or third-party downloads; the skill is instruction/code-only and uses only stdlib Python (urllib). No remote installers or archives are fetched.
证书
The skill legitimately requires secrets (PIPEDRIVE_API_TOKEN or PIPEDRIVE_ACCESS_TOKEN) and PIPEDRIVE_COMPANY_DOMAIN, but the registry metadata declares none and does not set a primary credential. That mismatch reduces transparency and could lead a user to unknowingly provide credentials to an undeclared skill surface. The number and type of env vars requested by the code are proportionate to the stated purpose, but they are not surfaced in th…
持久
The skill does not request always:true, does not modify other skills or global agent config, and runs only when invoked. It does not request elevated or persistent system privileges.
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Pipedrive CRM (OpenClaw)」。简介：Manage Pipedrive CRM from OpenClaw using API v1, including people, organization…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/danielfoch/pipedrive-crm-openclaw/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
---
name: pipedrive-crm-openclaw
description: Manage Pipedrive CRM from OpenClaw using API v1, including people, organizations, deals, leads, activities, notes, pipelines, and custom endpoint actions. Use when a user wants to perform CRM operations by API instead of the Pipedrive UI.
---
# Pipedrive CRM for OpenClaw
Use this skill to run day-to-day CRM operations in Pipedrive through API calls, including CRUD, search, pipeline movement, activity logging, and any unsupported operation via raw endpoint requests.
## Required Environment
Set one authentication mode:
- `PIPEDRIVE_API_TOKEN` for API token auth (simplest)
- `PIPEDRIVE_ACCESS_TOKEN` for OAuth bearer auth
Set base routing:
- `PIPEDRIVE_COMPANY_DOMAIN` (for example: `acme` for `https://acme.pipedrive.com`)
Optional:
- `PIPEDRIVE_API_BASE` to override full API base URL (defaults to `https://<company>.pipedrive.com/api/v1`)
- `PIPEDRIVE_TIMEOUT` request timeout in seconds (default `30`)
## Setup
If the user asks to connect or validate credentials:
```bash
python3 skills/pipedrive-crm-openclaw/scripts/setup-wizard.py
```
## Primary Script
Run:
```bash
python3 skills/pipedrive-crm-openclaw/scripts/pipedrive-api.py <command> [args]
```
Core commands:
- `test_connection`
- `list <entity> [--start N] [--limit N]`
- `get <entity> <id>`
- `create <entity> <json_payload>`
- `update <entity> <id> <json_payload> [--method PUT|PATCH]`
- `delete <entity> <id>`
- `search <entity> <term> [--limit N] [--fields csv] [--exact-match]`
- `move_deal_stage <deal_id> <stage_id> [--status open|won|lost|deleted]`
- `add_note <content> [--deal-id ID] [--person-id ID] [--org-id ID] [--lead-id UUID]`
- `request <METHOD> <path> [--query '{...}'] [--body '{...}']`
Supported entities:
- `persons`
- `organizations`
- `deals`
- `leads`
- `activities`
- `notes`
- `products`
- `users`
- `pipelines`
- `stages`
## Practical OpenClaw Playbooks
### Lead Intake and Qualification
1. `search persons "name or email"` to deduplicate.
2. `create persons '{...}'` if no match.
3. `create deals '{...}'` and link person/org.
4. `add_note "summary" --deal-id <id>` to preserve context.
### Pipeline Management
1. `list deals` with filters through `request` query.
2. `move_deal_stage <deal_id> <stage_id>`.
3. `create activities '{...}'` for next follow-up.
### Daily Follow-Up Queue
1. `list activities` and `search persons`.
2. `update activities <id> '{"done":1}'` after completion.
3. Log interaction with `add_note`.
## Safety Rules
- Never print or echo raw tokens in chat output.
- Read before write when user intent is ambiguous.
- Validate IDs from API responses before destructive actions.
- If response is `401` or `403`, stop and request corrected credentials/scopes.
- Use `request` for endpoints not yet wrapped by helper commands.
## References
Load as needed:
- `references/entity-playbooks.md`
- `references/pipedrive-v1-notes.md`