Token导航 LogoToken导航

Agent Skill · 研究检索

frappe-core-workflow(冰沙核心工作流程)

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

frappe-core-workflow 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,674 个 Skill 里排第 72,323。

总安装 188周安装 8GitHub Stars 79下载 66核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/openaec-foundation/frappe_claude_skill_package --skill frappe-core-workflow

这个 Skill 是做什么的

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

frappe-core-workflow 用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词快速定位候选结果时使用。通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 核验具体用法。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。适用于工作流管理和流程自动化处理场景。

来源仓库内路径:skills/frappe-core-workflow

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

frappe-core-workflow 怎么安装?

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

frappe-core-workflow 支持哪些 AI 工具?

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

frappe-core-workflow 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

frappe-core-workflow 是免费的吗?

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

frappe-core-workflow 用的人多吗?

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

frappe-core-workflow 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

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

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 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调用外部服务未明确有提醒
frappe-core-workflow

冰沙核心工作流程 · 本页

18879只读未明确通过

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

SKILL.md 原文

Workflow Engine

The Frappe Workflow engine is a state machine that controls document lifecycle through configurable states, transitions, and role-based permissions. It governs when and how documents change status, who can perform actions, and what side effects occur on each transition.

Quick Reference

Workflow DocType            → Defines the state machine for a specific DocType
├── states (child table)    → Workflow Document State rows
│   ├── state               → Link to Workflow State
│   ├── doc_status          → 0 (Draft), 1 (Submitted), 2 (Cancelled)
│   ├── allow_edit          → Role that can edit in this state
│   ├── update_field        → Field to update when entering state
│   ├── update_value        → Value to set (literal or expression)
│   └── next_action_email_template → Email Template link
└── transitions (child table) → Workflow Transition rows
    ├── state               → Source state (Link to Workflow State)
    ├── action              → Link to Workflow Action Master
    ├── next_state          → Target state (Link to Workflow State)
    ├── allowed             → Role that can perform this action
    ├── allow_self_approval → Check (default: 1)
    ├── condition           → Python expression (optional)
    └── transition_tasks    → Link to Workflow Transition Tasks

Key Fields on Workflow DocType

FieldTypePurpose
workflow_nameDataUnique identifier
document_typeLink → DocTypeTarget DocType
is_activeCheckOnly ONE workflow per DocType can be active
workflow_state_fieldDataDefault: workflow_state
override_statusCheckPrevent workflow from overriding list view status
send_email_alertCheckEmail notifications with next possible actions

How the Engine Works

1. Activation and Field Creation

When a Workflow is saved with is_active = 1:

  • All other workflows for the same DocType are deactivated automatically
  • A hidden Custom Field (workflow_state_field, default workflow_state) is created on the target DocType if it does not exist
  • The field is type Link to Workflow State, with hidden=1, allow_on_submit=1, no_copy=1
  • Existing documents with empty workflow state get their state set based on their current docstatus

2. State Resolution

Every document under a workflow has a workflow_state field. The engine resolves available transitions by:

  1. Reading current workflow_state from the document
  2. Filtering workflow.transitions where transition.state == current_state
  3. Filtering by user roles: transition.allowed in frappe.get_roles()
  4. Evaluating transition.condition via frappe.safe_eval() (if set)
  5. Returning matching transitions as available actions

3. Applying a Transition

When apply_workflow(doc, action) is called:

  1. Load document from DB (fresh read)
  2. Get available transitions for current user
  3. Find transition matching the requested action
  4. Check self-approval: blocked if allow_self_approval=0 AND user is document owner
  5. Set workflow_state_field to transition.next_state
  6. If update_field is set on the target state, update that field
  7. Execute transition tasks (sync first, then async via frappe.enqueue)
  8. Handle docstatus change based on source/target state doc_status values
  9. Save/Submit/Cancel document accordingly
  10. Add workflow comment

Workflow and DocStatus Interaction

CRITICAL: The workflow engine controls docstatus transitions. You NEVER call doc.submit() or doc.cancel() directly on a workflow-controlled document. The workflow does it.

DocStatus Transition Rules

Source doc_statusTarget doc_statusEngine ActionValid?
0 (Draft)0 (Draft)doc.save()YES
0 (Draft)1 (Submitted)doc.submit()YES
1 (Submitted)1 (Submitted)doc.save()YES
1 (Submitted)2 (Cancelled)doc.cancel()YES
2 (Cancelled)ANYBLOCKEDNO
1 (Submitted)0 (Draft)BLOCKEDNO
0 (Draft)2 (Cancelled)BLOCKEDNO

ALWAYS define your states so that docstatus only moves forward: 0→0, 0→1, 1→1, 1→2. NEVER create a transition from a cancelled state or from submitted back to draft.

Non-Submittable DocTypes

If the target DocType is NOT submittable, ALL states MUST have doc_status = 0. The engine validates this and throws an error if any state has doc_status = 1 or 2 on a non-submittable DocType.

Workflow States

Workflow State is a separate DocType used as a master list. Each state has:

FieldPurpose
stateDisplay name of the state
styleCSS class for badge display (Primary, Success, Warning, Danger, Info, Inverse)
iconFont Awesome icon class

State Row Fields (Workflow Document State)

FieldPurpose
stateLink to Workflow State
doc_statusSelect: 0, 1, or 2
allow_editLink to Role — ONLY this role can edit the document in this state
update_fieldField to update when document enters this state
update_valueValue to set (string or Python expression if evaluate_as_expression=1)
is_optional_stateCheck — optional states are skipped in get_next_possible_transitions
send_emailCheck (default 1) — send email notification on entering this state
next_action_email_templateLink to Email Template
messageText message for the email notification

Workflow Transitions

Each transition row defines one possible action:

FieldPurpose
stateSource state (MUST exist in states table)
actionLink to Workflow Action Master (e.g., "Approve", "Reject", "Review")
next_stateTarget state (MUST exist in states table)
allowedLink to Role — ONLY users with this role see this action
allow_self_approvalCheck (default 1) — if 0, document owner cannot perform this action
conditionPython expression evaluated with frappe.safe_eval()
transition_tasksLink to Workflow Transition Tasks (v15+)

Condition Expressions

Conditions are Python expressions evaluated in a sandboxed environment. Available globals:

# Available in condition expressions:
frappe.db.get_value(doctype, name, fieldname)
frappe.db.get_list(doctype, filters, fields)
frappe.session.user
frappe.session.roles  # NOT available — use frappe.get_roles() outside conditions
frappe.utils.now_datetime()
frappe.utils.add_to_date(date, **kwargs)
frappe.utils.get_datetime(datetime_str)
frappe.utils.now()
doc.fieldname  # Access any field on the document (as dict)

Example conditions:

doc.grand_total > 50000
doc.department == "HR"
doc.grand_total > 50000 and doc.department != "Finance"

Workflow Actions

Workflow Action Master

Simple DocType with just a workflow_action_name field. Common actions: Approve, Reject, Review, Send Back, Cancel. Create these first before defining transitions.

Workflow Action DocType

Tracks pending actions for users. Created automatically when a document enters a state with outgoing transitions.

FieldPurpose
statusOpen or Completed
reference_doctypeThe DocType of the document
reference_nameThe document name
workflow_stateCurrent workflow state
userAssigned user
permitted_rolesTable MultiSelect of roles that can act
completed_byUser who completed the action
completed_by_roleRole used to complete

Workflow Actions appear in the user's "Workflow Action" list and can be acted on via email links.

Self-Approval Control

def has_approval_access(user, doc, transition):
    return (user == "Administrator"
            or transition.get("allow_self_approval")
            or user != doc.get("owner"))
  • Administrator ALWAYS has approval access regardless of settings
  • If allow_self_approval = 1 (default): document owner CAN approve
  • If allow_self_approval = 0: document owner CANNOT approve their own document

Decision Tree

Need workflow on a DocType?
├── Is DocType submittable?
│   ├── YES → States can use doc_status 0, 1, 2
│   └── NO  → ALL states MUST have doc_status = 0
├── Define states → Create Workflow State records first
├── Define transitions → Need Workflow Action Master records first
├── Who can edit in each state? → Set allow_edit per state
├── Need conditional transitions?
│   └── Use Python expressions with doc.field access
├── Need to block self-approval?
│   └── Set allow_self_approval = 0 on specific transitions
└── Need email notifications?
    └── Set send_email_alert on Workflow + email templates on states

Common Errors

ErrorCauseFix
WorkflowStateErrorDocument has no workflow_state setEnsure workflow sets initial state on creation
WorkflowTransitionErrorAction not valid for current state/roleVerify transitions table covers all needed paths
WorkflowPermissionErrorUser lacks role for transition, or self-approval blockedCheck allowed role and allow_self_approval
"Illegal Document Status"Invalid docstatus transition (e.g., 0→2)Fix state doc_status values
"Cannot cancel before submitting"Transition from draft (0) to cancelled (2)Add intermediate submitted (1) state

See Also

  • API Reference — Complete workflow Python API
  • Examples — Workflow configuration examples
  • Anti-Patterns — Common mistakes and how to avoid them
  • frappe-impl-workflow — Step-by-step implementation guide

平台分布

Codex

34.82%
按下载量换算23

Claude

28.51%
按下载量换算19

Cursor

17.76%
按下载量换算12

Gemini CLI

9.08%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills