New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Frappe Core Workflow

by Impertio-Studio in Impertio-Studio/Frappe_Claude_Skill_Package

A skill your agent uses when creating or modifying Frappe Workflows, defining states and transitions, adding action conditions, or troubleshooting workflow permission errors.

MITAuto-check passed

Install Frappe Core Workflow

skills CLI
$ npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Impertio-Studio/Frappe_Claude_Skill_Package frappe-core-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/source/core/frappe-core-workflow .claude/skills/frappe-core-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
frappe-core-workflow
GitHub stars
188
Token cost
~2.7k tokens
SKILL.md length
887 words
Files
5 (incl. references)
Skills in repo
61
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when creating or modifying Frappe Workflows, defining states and transitions, adding action conditions, or troubleshooting workflow permission errors.

  • Works in 3 steps: Activation and Field Creation → State Resolution → Applying a Transition
  • Modifying Frappe Workflows
  • SKILL.md covers Quick Reference, How the Engine Works, Workflow and DocStatus… and Workflow States, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Frappe Core Workflow is an agent skill from Impertio-Studio/Frappe_Claude_Skill_Package. Use when creating or modifying Frappe Workflows, defining states and transitions, adding action conditions, or troubleshooting workflow permission errors. Prevents stuck documents from misconfigured transitions, missing state permissions, and circular workflow paths. Covers Workflow DocType, workflow states, transitions, actions, conditions (Python expressions), workflow permissions, workflowstate field, Workflow Action DocType. Keywords: workflow, states, transitions, actions, conditions, workflowstate, Workflow…

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/anti-patterns.md`, `references/api-reference.md` and `references/examples.md`). Compatibility notes: Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.

It works with Python. The repository describes itself as: 60 deterministic Claude AI skills for Frappe Framework & ERPNext v14-v16 development and operations. The licence is MIT.

When your agent uses it

  • Modifying Frappe Workflows
  • Defining states and transitions
  • Adding action conditions
  • Troubleshooting workflow permission errors

Example prompts

  • “/frappe-core-workflow”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Activation and Field Creation
  2. State Resolution
  3. Applying a Transition

What it can do on your machine

Read from SKILL.md and the folder at commit 36cfa80. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.

    From compatibility in the SKILL.md frontmatter.

Context cost

Frappe Core Workflow loads about 2.7k tokens when it runs, and up to ~7.9k if it reads all its reference files. Until then it costs about 168 tokens; SKILL.md has 887 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~168
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Impertio-Studio/Frappe_Claude_Skill_Package at commit 36cfa80, republished under its MIT licence (© Impertio-Studio). 887 words, ~2,656 tokens.

Download SKILL.mdSave it as .claude/skills/frappe-core-workflow/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
frappe-core-workflow
description
Use when creating or modifying Frappe Workflows, defining states and transitions, adding action conditions, or troubleshooting workflow permission errors. Prevents stuck documents from misconfigured transitions, missing state permissions, and circular workflow paths. Covers Workflow DocType, workflow states, transitions, actions, conditions (Python expressions), workflow permissions, workflow_state field, Workflow Action DocType. Keywords: workflow, states, transitions, actions, conditions, workflow_state, Workflow Action, approval, document workflow, approval process, document stuck, cannot change status, workflow not moving, who can approve..
compatibility
Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.
license
MIT
metadata.author
OpenAEC-Foundation
metadata.version
2.0

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
Show full SKILL.md (321 more words)Show less

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:

python
# 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:

python
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

python
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

© Impertio-Studio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/source/core/frappe-core-workflow of Impertio-Studio/Frappe_Claude_Skill_Package.

  • SKILL.md
  • references/.gitkeep
  • references/anti-patterns.md
  • references/api-reference.md
  • references/examples.md

Open the folder on GitHubat commit 36cfa80

Compare with similar skills

Frappe Core Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Frappe Core Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Frappe Core Workflow this skillImpertio-Studio/Frappe_Claude_Skill_Package188—~2.7kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
PDF Processinganthropics/skills180k48 repos~2kAutomated safety check: PassProprietary
NotebookLM Research AssistantPleasePrompto/notebooklm-skill7.8k14 repos~2.4kAutomated safety check: NotesMIT
Manim Video Productionbrowser-use/video-use28k6 repos~3kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • PDF Processing

    anthropics/skills

    Official

    Handles everyday PDF jobs in Python and on the command line: extract text and tables, merge, split, rotate, watermark, fill forms, encrypt and OCR.

    180k GitHub starsUsed in 48 repos~2k tokens
    Documents & OfficeAuto-check passed

  • NotebookLM Research Assistant

    PleasePrompto/notebooklm-skill

    Lets Claude Code ask questions of your Google NotebookLM notebooks through browser automation and return answers grounded in your uploaded sources.

    7.8k GitHub starsUsed in 14 repos~2.4k tokens
    Knowledge ManagementAuto-check: notes

  • Manim Video Production

    browser-use/video-use

    Produces math and technical explainer videos with Manim Community Edition: concept animations, equation derivations, algorithm walkthroughs and data stories.

    28k GitHub starsUsed in 6 repos~3k tokens
    Media & CreativeAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • PPT Master

    hugohe3/ppt-master

    Generates editable PowerPoint decks, rebuilds slides from images, fills .pptx templates and polishes existing presentations through routed workflows.

    58k GitHub starsUsed in 1 repo~2.5k tokens
    Documents & OfficeAuto-check passed

More from Impertio-Studio/Frappe_Claude_Skill_Package

All 61 skills in this repo

  • Frappe Ops Website Deploy

    Impertio-Studio/Frappe_Claude_Skill_Package

    Deploy HTML/CSS websites to ERPNext/Frappe (v15/v16) as Web Pages via the REST API.

    188 GitHub stars~2.5k tokensUpdated 22 days ago
    Auto-check passed

  • Frappe Agent Architect

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when designing multi-app Frappe architectures, deciding whether to split functionality into separate apps, or implementing cross-app communication patterns.

    188 GitHub stars~2.8k tokensUpdated 22 days ago
    Auto-check passed

  • Frappe Agent Debugger

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when debugging Frappe errors, using bench console for live inspection, analyzing tracebacks, or reading Frappe log files.

    188 GitHub stars~2.9k tokensUpdated 22 days ago
    Auto-check passed

  • Frappe Agent Interpreter

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when receiving vague or unclear ERPNext/Frappe development requests that need interpretation.

    188 GitHub stars~3.2k tokensUpdated 22 days ago
    Auto-check passed

  • Frappe Agent Migrator

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when migrating a Frappe app between major versions, detecting breaking API changes, or resolving post-migration errors.

    188 GitHub stars~2.8k tokensUpdated 22 days ago
    Auto-check: notes

  • Frappe Agent Validator

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when reviewing or validating Frappe/ERPNext code against best practices and common pitfalls.

    188 GitHub stars~2.8k tokensUpdated 22 days ago
    Auto-check passed

Works with

Questions about Frappe Core Workflow

What does Frappe Core Workflow do?

A skill your agent uses when creating or modifying Frappe Workflows, defining states and transitions, adding action conditions, or troubleshooting workflow permission errors. Frappe Core Workflow is an agent skill from Impertio-Studio/Frappe_Claude_Skill_Package. Use when creating or modifying Frappe Workflows, defining states and transitions, adding action conditions, or troubleshooting workflow permission errors.

When should I use Frappe Core Workflow?

Frappe Core Workflow fits situations like: modifying Frappe Workflows; defining states and transitions; adding action conditions; troubleshooting workflow permission errors.

How do I install Frappe Core Workflow in Claude Code?

Run `npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-workflow -a claude-code`. Or copy the skill folder (skills/source/core/frappe-core-workflow in Impertio-Studio/Frappe_Claude_Skill_Package) into .claude/skills/frappe-core-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Frappe Core Workflow in Codex?

Run `npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-workflow -a codex`. Or copy the skill folder (skills/source/core/frappe-core-workflow in Impertio-Studio/Frappe_Claude_Skill_Package) into .agents/skills/frappe-core-workflow in your project. Codex loads it when a task matches its description.

Can I use Frappe Core Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frappe-core-workflow, .gemini/skills/frappe-core-workflow, .github/skills/frappe-core-workflow and .opencode/skills/frappe-core-workflow in your project.

What does Frappe Core Workflow need to run?

SKILL.md names no scripts, command-line tools or credentials: Frappe Core Workflow is instructions for the agent only. Our summary lists: Python 3. Compatibility (from SKILL.md): Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16..

Does Frappe Core Workflow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Frappe Core Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Frappe Core Workflow use?

Frappe Core Workflow is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Frappe Core Workflow use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.2k tokens, read only when the agent opens those files.

What are the alternatives to Frappe Core Workflow?

Skills that share tags, products or a category with Frappe Core Workflow: MCP Server Builder (anthropics/skills, 180k stars), PDF Processing (anthropics/skills, 180k stars), NotebookLM Research Assistant (PleasePrompto/notebooklm-skill, 7.8k stars) and Manim Video Production (browser-use/video-use, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Frappe Core Workflow?

Impertio-Studio (a GitHub organization) maintains it in Impertio-Studio/Frappe_Claude_Skill_Package, which has 188 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on September 17, 2026.

Source: Impertio-Studio/Frappe_Claude_Skill_Package on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.