Token导航 LogoToken导航TokenDH.com
效率敏感数据clawhub未标认证来源可访问clear审计通过

sophiiesophiie 效率

Agent Skill

sophiie 用于辅助前端页面、组件、样式和交互逻辑开发,适合在 OpenClaw 中需要维护前端项目、生成组件或检查界面实现时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

20,394

周安装

825

GitHub Stars

2

下载量

6,402
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install sophiie

简介

通过 Sophiie REST API 管理您的 Sophiie 销售渠道 - 潜在客户、查询、预约、常见问题解答、政策、短信和电话。

SKILL.md

name
sophiie
description
Manage your Sophiie sales pipeline — leads, inquiries, appointments, FAQs, policies, SMS, and calls via the Sophiie REST API.
metadata
openclaw
requires
env
bins
primaryEnv
SOPHIIE_API_KEY
emoji
📞
homepage
https://docs.sophiie.ai
files

Sophiie — Sales Pipeline Management

Sophiie is a B2B SaaS platform for sales pipeline management. Organizations get AI-powered virtual assistant agents that handle calls, SMS, and lead management. This skill lets you manage your Sophiie pipeline via natural language.

Authentication

All requests use Authorization: Bearer <key> where the key is SOPHIIE_API_KEY. Keys are prefixed sk_live_* (production) or sk_test_* (sandbox).

  • Base URL: https://api.sophiie.ai
  • Rate limit: 60 requests/minute
  • All responses: JSON

External Endpoints

MethodURLData Sent
GEThttps://api.sophiie.ai/v1/leadsQuery: page, limit
GEThttps://api.sophiie.ai/v1/leads/{id}None
POSThttps://api.sophiie.ai/v1/leadsBody: firstName, lastName, email, phone, suburb, businessName, socials
PUThttps://api.sophiie.ai/v1/leads/{id}Body: firstName, lastName, email, phone, suburb, businessName, socials
DELETEhttps://api.sophiie.ai/v1/leads/{id}None
GEThttps://api.sophiie.ai/v1/leads/{id}/notesQuery: page, limit
GEThttps://api.sophiie.ai/v1/leads/{id}/activitiesQuery: page, limit
GEThttps://api.sophiie.ai/v1/inquiriesQuery: page, limit, leadId, expand
GEThttps://api.sophiie.ai/v1/inquiries/{id}None
GEThttps://api.sophiie.ai/v1/appointmentsQuery: page, limit, leadId
POSThttps://api.sophiie.ai/v1/callsBody: name, phoneNumber, mode, custom_instructions
POSThttps://api.sophiie.ai/v1/smsBody: userId, leadId, message, messageThreadId
GEThttps://api.sophiie.ai/v1/faqsQuery: page, limit
POSThttps://api.sophiie.ai/v1/faqsBody: question, answer, isActive
PUThttps://api.sophiie.ai/v1/faqs/{id}Body: question, answer, isActive
DELETEhttps://api.sophiie.ai/v1/faqs/{id}None
GEThttps://api.sophiie.ai/v1/policiesQuery: page, limit
POSThttps://api.sophiie.ai/v1/policiesBody: title, content, isActive
PUThttps://api.sophiie.ai/v1/policies/{id}Body: title, content, isActive
DELETEhttps://api.sophiie.ai/v1/policies/{id}None
GEThttps://api.sophiie.ai/v1/membersQuery: page, limit
GEThttps://api.sophiie.ai/v1/organizationNone
GEThttps://api.sophiie.ai/v1/organization/availabilityNone
GEThttps://api.sophiie.ai/v1/organization/membersQuery: page, limit
GEThttps://api.sophiie.ai/v1/organization/servicesNone
GEThttps://api.sophiie.ai/v1/organization/productsNone

Security & Privacy

  • The SOPHIIE_API_KEY is never logged, printed, or echoed in output
  • All requests use HTTPS only
  • No data is cached locally — every command fetches live from the API
  • All user input is sanitized via jq -n (never string-interpolated into JSON bodies)
  • The skill has read-only access to SOPHIIE_API_KEY — it cannot modify or delete the environment variable

Command Reference

All commands are run via scripts/sophiie.sh <domain> <action> [options].

Leads

leads list — List all leads in the pipeline

--page <n>    Page number (default: 1)
--limit <n>   Items per page (default: 50, max: 100)

Use when the user wants to see their pipeline, check leads, or browse contacts.

leads get <id> — Get full details for a specific lead Use when the user asks about a specific lead by name or ID. Lead IDs start with ld_.

leads create — Create a new lead

--firstName <name>      Required (min 2 chars)
--suburb <suburb>       Required
--lastName <name>       Optional
--email <email>         Optional (valid email)
--phone <number>        Optional (E.164 format, e.g. +61412345678)
--businessName <name>   Optional
--instagram <handle>    Optional
--facebook <handle>     Optional

Use when the user wants to add a new contact or lead to their pipeline.

leads update <id> — Update an existing lead Same options as create, but all are optional. At least one field must be provided. Use when the user wants to change lead details.

leads delete <id> — Delete a lead (soft delete) Use when the user explicitly asks to remove a lead. Always confirm before deleting.

leads notes <id> — List notes for a lead

--page <n>    Page number (default: 1)
--limit <n>   Items per page (default: 50, max: 100)

Use when the user asks about notes or history on a specific lead.

leads activities <id> — List activity log for a lead

--page <n>    Page number (default: 1)
--limit <n>   Items per page (default: 50, max: 100)

Use when the user wants to see what happened with a lead (timeline, events).

Inquiries

inquiries list — List all inquiries

--page <n>       Page number (default: 1)
--limit <n>      Items per page (default: 50, max: 100)
--leadId <id>    Filter by lead ID (ld_...)
--expand <type>  Expand related data: "external", "lead", or "both"

Use when the user asks about incoming inquiries, messages, or calls received.

inquiries get <id> — Get full inquiry details with source data Returns the inquiry with expanded source data (call transcripts, SMS messages, webform submissions, etc.) depending on the inquiry source type (CALL, SMS, EMAIL, CHATBOT, WEBFORM). Use when the user wants details on a specific inquiry.

FAQs

faqs list — List all FAQs

--page <n>    Page number (default: 1)
--limit <n>   Items per page (default: 50, max: 100)

Use when the user wants to see their knowledge base or FAQ entries.

faqs create — Create a new FAQ

--question <text>    Required (max 255 chars)
--answer <text>      Required
--isActive <bool>    Optional (true/false)

Use when the user wants to add to their AI agent's knowledge base.

faqs update <id> — Update an FAQ (ID is a number) Same options as create, all optional. Use when the user wants to change an existing FAQ entry.

faqs delete <id> — Delete an FAQ (soft delete) Always confirm before deleting.

Policies

policies list — List all policies

--page <n>    Page number (default: 1)
--limit <n>   Items per page (default: 50, max: 100)

Use when the user asks about their business policies.

policies create — Create a new policy

--title <text>      Required (min 2, max 255 chars)
--content <text>    Required (min 2 chars)
--isActive <bool>   Optional (true/false)

Use when the user wants to add a business policy for their AI agent.

policies update <id> — Update a policy (ID is a number) Same options as create, all optional.

policies delete <id> — Delete a policy (soft delete) Always confirm before deleting.

Communication

calls send — Initiate an outbound AI call

--name <name>                 Required — name of person being called
--phoneNumber <number>        Required — E.164 format (e.g. +61412345678)
--mode <mode>                 Optional — "normal" (default) or "transfer_only"
--custom_instructions <text>  Optional — required when mode is "transfer_only"

Use when the user wants to call someone. Always confirm the phone number before calling.

sms send — Send an SMS message

--userId <id>             Required — sender user ID (usr_...)
--leadId <id>             Required — recipient lead ID (ld_...)
--message <text>          Required — message text (min 2 chars)
--messageThreadId <n>     Optional — existing thread ID (number); omit to start new thread

Use when the user wants to text a lead. You need to know the userId — use members list first if needed.

Appointments

appointments list — List all appointments

--page <n>       Page number (default: 1)
--limit <n>      Items per page (default: 50, max: 100)
--leadId <id>    Filter by lead ID (ld_...)

Use when the user asks about upcoming appointments or scheduled meetings.

Organization

org get — Get organization details (name, timezone, currency, etc.) Use when the user asks about their org settings or business info.

org availability — Get business hours / availability schedules Use when the user asks about working hours or availability.

org members — List organization members with roles

--page <n>    Page number (default: 1)
--limit <n>   Items per page (default: 50, max: 100)

Use when the user asks about team members (returns membership-level data with positions/avatars).

org services — List services offered (grouped by category) Use when the user asks about their service offerings.

org products — List products offered (grouped by category) Use when the user asks about their product catalog.

Members

members list — List all organization members

--page <n>    Page number (default: 1)
--limit <n>   Items per page (default: 50, max: 100)

Use when you need user IDs (usr_...) for operations like sending SMS. Returns user-level data with roles.

Decision Guide

User intentCommand(s)
"Check my pipeline" / "Show leads"leads list
"Tell me about [lead name]"leads list → find by name → leads get <id>
"Add a new lead" / "New contact"leads create
"Update [lead]'s phone number"leads update <id> --phone <number>
"Remove this lead"leads delete <id> (confirm first)
"What inquiries came in?"inquiries list
"Show me that call transcript"inquiries get <id>
"Any appointments today?"appointments list
"Call [person]" / "Ring [number]"calls send (confirm number first)
"Text [lead] about [topic]"members list → get userId → sms send
"Update the knowledge base"faqs list → then faqs create or faqs update
"Add a refund policy"policies create
"What are our business hours?"org availability
"Who's on the team?"members list or org members
"What services do we offer?"org services

Pagination

All list endpoints return paginated responses:

{
  "items": [...],
  "totalPages": 5,
  "currentPage": 1,
  "totalCount": 237
}
  • Default: page 1, 50 items per page
  • Maximum: 100 items per page
  • Always check totalPages — if there are more pages, tell the user and offer to fetch the next page

Error Reference

CodeMeaningWhat to tell the user
401Invalid or missing API key"Your API key appears to be invalid. Check SOPHIIE_API_KEY."
404Resource not found"That [lead/inquiry/etc.] wasn't found. Double-check the ID."
409Conflict (duplicate lead)"A lead with that info already exists."
429Rate limited"Too many requests. Wait a moment and try again."
500Server error"Something went wrong on Sophiie's end. Try again shortly."

Error responses have this shape:

{
  "success": false,
  "message": "...",
  "error": { "status": 401, "message": "..." }
}

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

85.77%
按下载量换算5,491

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills