Token导航 LogoToken导航

Agent Skill · 前端设计

ghl-workflow-automation(GHL 工作流程自动化)

ghl-workflow-automation 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

ghl-workflow-automation 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 966。

总安装 9,003周安装 406GitHub Stars 5下载 2,772核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:ghl-workflow-automation(GHL 工作流程自动化)
来源仓库:https://github.com/justin322322/ghl-skills
仓库路径:skills/ghl-workflow-automation
安装命令:
npx skills add https://github.com/justin322322/ghl-skills --skill 'GHL Workflow Automation'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/justin322322/ghl-skills --skill 'GHL Workflow Automation'

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

GHL 工作流程自动化技能用于处理 GitHub 相关协作信息和代码变更流程。适合在项目状态跟踪、分支管理和协作事项整理等开发场景中应用。通过 GitHub 仓库以 npx skills add 方式安装并启用对应技能模块。使用前应核实维护状态,注意可能执行的命令操作和文件修改权限。

ghl-workflow-automation 属于前端设计类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/ghl-workflow-automation

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/justin322322/ghl-skills --skill 'GHL Workflow…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

ghl-workflow-automation 怎么安装?

在终端执行 npx skills add https://github.com/justin322322/ghl-skills --skill 'GHL Workflow Automation…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

ghl-workflow-automation 支持哪些 AI 工具?

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

ghl-workflow-automation 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

ghl-workflow-automation 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

ghl-workflow-automation 用的人多吗?

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

ghl-workflow-automation 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

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

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
ghl-workflow-automation

GHL 工作流程自动化 · 本页

9,0035需要联网未明确通过

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

SKILL.md 原文

GHL Workflow Automation

Overview

GoHighLevel's Workflow Builder is the automation engine powering all marketing, sales, and operational processes. Workflows replace the legacy "Campaigns" and provide a visual, drag-and-drop interface for building complex multi-step automations.


Core Concepts

ConceptDescription
TriggerThe event that starts a workflow (e.g., form submitted, tag added)
ActionThe task performed after a trigger fires (e.g., send SMS, add tag)
Condition (If/Else)Branching logic based on contact data, tags, or custom fields
Wait StepA timed delay between actions (minutes, hours, days, or specific time)
GoalA target state that, when reached, stops the workflow for that contact
Custom ValuesSystem-wide variables for dynamic content (e.g., {{custom_values.company_name}})
Custom FieldsContact-specific data used in merge fields (e.g., {{contact.first_name}})

Triggers Reference

Contact Events

  • Contact Created — New contact added to the system
  • Contact Changed — Any field on a contact is updated
  • Tag Added / Tag Removed — Specific tag applied or removed
  • Contact DND — Do Not Disturb status changed
  • Birthday Reminder — Based on contact's birthday field
  • Note Added / Note Changed — Internal notes activity

Communication Events

  • Customer Replied — Contact responds via any channel (email, SMS, etc.)
  • Form Submitted — A specific GHL form is completed
  • Survey Submitted — A specific survey is completed
  • Trigger Link Clicked — Special tracking link is clicked
  • Email Events — Email opened, clicked, bounced, complained, unsubscribed
  • Facebook Lead Form Submitted — Lead ad form captured

Sales & Booking Events

  • Appointment Status — Booking confirmed, cancelled, no-showed
  • Pipeline Stage Changed — Opportunity moves to a new stage
  • Opportunity Status Changed — Deal won, lost, or abandoned
  • Order Submitted / Order Form Submission
  • Invoice — Invoice created, sent, paid, overdue
  • Payment Received

Membership Events

  • Membership New Signup
  • Product Access Granted / Product Access Removed
  • Offer Access Granted
  • Category Completed / Product Completed

Other Events

  • Task Added / Task Completed / Task Reminder
  • Stale Opportunities — Opportunities inactive for a configured period
  • Inbound Webhook — External systems trigger the workflow via webhook URL
  • Manual / API Trigger — Workflow started manually or via API call
Best Practice: Always apply filters to triggers. For example, filter a Form Submitted trigger to a specific form. Without filters, the workflow fires for ALL forms.

Actions Reference

Communication

  • Send Email — HTML or plain text, with merge fields and attachments
  • Send SMS / MMS — Text messages with optional media
  • Send Voicemail Drop — Ringless voicemail delivery
  • Send to Messenger — Facebook Messenger message
  • Send Internal Notification — Alert team members via email or SMS
  • Send Review Request — Automated review solicitation

Contact Management

  • Add / Remove Tag
  • Create / Update Contact
  • Add to / Remove from Workflow
  • Add Internal Note
  • Create Task — Assign follow-up tasks to team members
  • Assign User — Assign contact to a specific team member
  • Update Custom Field — Set or modify any custom field value
  • Math Operation — Increment/decrement numeric fields (e.g., lead score)
  • Set Contact DND

Pipeline & Sales

  • Create / Update Opportunity
  • Move Opportunity Stage
  • Add to / Remove from Campaign

External & Advanced

  • Webhook (Custom) — Send data to external systems (Zapier, Make, custom endpoints)
  • HTTP Request — Make API calls to third-party services
  • Google Sheets — Add rows, update cells
  • If / Else Condition — Branch logic based on data
  • Go To Step — Jump to a different action in the workflow
  • Wait — Delay for a specified time or until a specific day/time

Custom Values vs. Custom Fields

FeatureCustom ValuesCustom Fields
ScopeSystem-wide (same for everyone)Per-contact (unique to each person)
Use CaseCompany name, phone, address, brandingContact name, email, lead score
UpdateChange once → updates everywhereChanges per individual contact
Merge Syntax{{custom_values.field_name}}{{contact.field_name}}
Best ForSnapshots, templates, global brandingPersonalization, segmentation

Custom Values Best Practices

  1. Group by category — Create folders like "Business Info", "Branding", "Social Links"
  2. Use for snapshots — Store client-specific details that can be easily swapped
  3. Naming convention — Use snake_case with clear prefixes (e.g., biz_phone, biz_email)
  4. Keep them current — Review and update quarterly

Workflow Design Best Practices

Planning

  1. Map the journey first — Sketch the trigger → action flow on paper before building
  2. Start simple — Begin with 3-5 steps, then add complexity
  3. One trigger per workflow — Avoid multiple triggers causing confusion
  4. Use descriptive names — Name workflows clearly: [Niche] - [Purpose] - [Channel] (e.g., Dental - New Lead Follow-Up - SMS)

Building

  1. Use if/else branches — Personalize paths based on tags, custom fields, or contact behavior
  2. Add wait steps — Space out messages naturally (don't send 5 SMS in 1 minute)
  3. Set time windows — Configure delivery hours (e.g., 9 AM–6 PM in contact's timezone)
  4. Use goals — Stop the workflow when the desired outcome is achieved (e.g., appointment booked)
  5. Add internal notifications — Alert team members at critical workflow points

Testing

  1. Test with a real contact — Create a test contact and run through the entire workflow
  2. Verify all links — Check every URL, tracking link, and redirect
  3. Check merge fields — Ensure all {{variables}} resolve correctly
  4. Test edge cases — Verify if/else branches with different contact data
  5. Monitor after launch — Watch the first 10-20 enrollments for errors

Performance

  1. Review weekly — Check open rates, click rates, and reply rates
  2. A/B test messages — Experiment with different copy, subject lines, and timing
  3. Archive unused workflows — Deactivate and archive workflows no longer in use
  4. Document your automations — Maintain an internal wiki or spreadsheet listing all active workflows

Common Workflow Templates

Speed-to-Lead (New Lead Response)

Trigger: Form Submitted
→ Send SMS (Immediate): "Thanks {{contact.first_name}}! We'll be in touch shortly."
→ Send Email: Welcome + value proposition
→ Internal Notification: Alert sales rep
→ Wait 5 min
→ If/Else: Contact replied?
   → Yes: End workflow
   → No: Send SMS follow-up
→ Wait 24 hours
→ Send Email: Case study / testimonial
→ Wait 48 hours
→ If/Else: Appointment booked?
   → Yes: End workflow
   → No: Send SMS with booking link

Appointment Reminder Sequence

Trigger: Appointment Status → Confirmed
→ Send SMS: "Your appointment is confirmed for {{appointment.date}}!"
→ Wait until 24hrs before appointment
→ Send SMS: "Reminder: Your appointment is tomorrow at {{appointment.time}}"
→ Wait until 1hr before appointment
→ Send SMS: "See you in 1 hour! Here's the address: {{custom_values.biz_address}}"

Review Request Automation

Trigger: Pipeline Stage Changed → "Completed" / "Delivered"
→ Wait 2 days
→ Send SMS: "How was your experience? We'd love a review! {{custom_values.review_link}}"
→ Wait 3 days
→ If/Else: Review received?
   → Yes: Send thank you SMS
   → No: Send Email: Gentle review reminder

Key Resources

平台分布

Codex

35.24%
按下载量换算977

Claude

32.49%
按下载量换算901

Cursor

18.28%
按下载量换算507

Gemini CLI

9.58%
按下载量换算266

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills