尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證The official SDRPilot plugin for Claude Code: a playbook skill plus the MCP connection to your own workspace, with live help docs.
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
Let Claude work inside your own SDRPilot workspace, and know what it is doing while it is there.
1. The connection. The MCP server for your workspace, authenticated with your own API key.
2. A skill. The playbook Claude reads first: how SDRPilot is put together (your ICP, scoring, the connection queue, conversations), the common workflows step by step, and what it must ask you before doing.
3. Live help docs. The server gives Claude docs_search, docs_read and docs_list, which read the help site as it is today. When we ship a feature and document it, Claude can look it up the same day.檢視完整 README ↗Let Claude work inside your own SDRPilot workspace, and know what it is doing while it is there.
The plugin bundles three things:
docs_search, docs_read and docs_list, which read the help site as it is today. When we ship a feature and document it, Claude can look it up the same day.You need Claude Code, an SDRPilot workspace and your API key. In SDRPilot, open Settings, then API and AI assistants.
claude plugin marketplace add sdrpilot/claude-plugin
claude plugin install sdrpilot@sdrpilot
Then give the plugin your key. Start claude and run:
/plugin configure sdrpilot@sdrpilot
Paste the key when it asks. It is stored in your system keychain, not in a file. Restart Claude Code afterwards so the connection picks it up.
Check that it works: start claude, run /mcp and look for the server marked connected, then ask something like "how is my outreach doing this week?".
The skill tells Claude to preview before it applies, to show you what will change, and to get your explicit go before anything that reaches a real person on LinkedIn (a connection request, a message, accepting a request, publishing a post), anything that cannot be undone, and anything that spends credits. It is also told to put the safety of your LinkedIn account first: no switching off warm-up, no raising limits unless you ask.
Your API key is the access control: Claude can do what the key can do.
claude plugin marketplace update sdrpilot, then claude plugin update sdrpilot@sdrpilot. The help docs need no update, Claude reads them live.claude plugin uninstall sdrpilot@sdrpilot.python3 scripts/check.py --live # wording rules, every tool name the skill mentions exists on the live server
claude plugin validate . --strict # the marketplace
claude plugin validate ./plugins/sdrpilot --strict # the plugin
Every statement in the skill must be backed by the help docs, and anything that can change (limits, prices, what is in beta) belongs in the docs, not in the skill. Bump version in plugins/sdrpilot/.claude-plugin/plugin.json when the skill or the MCP config changes, otherwise installed copies do not update.