pflow skill command group publishes saved workflows as Agent Skills that AI coding tools can discover and use.
pflow creates symlinks from tool skill directories to your saved workflows, keeping ~/.pflow/workflows/ as the single source of truth.
Supported tools
Commands
pflow skill save
Publish a saved workflow as a skill for AI coding tools.WORKFLOW_NAME- Name of a saved workflow (required)
By default, saves to Claude Code. Use multiple flags to save to multiple tools at once.
Examples:
save again on an existing skill updates the enrichment (idempotent):
What happens during save
What happens during save
When you run
pflow skill save, two things happen:-
Workflow enrichment - pflow adds a
## Usagesection to your workflow file with instructions for AI agents, and addsnameanddescriptionfields to the frontmatter. -
Symlink creation - pflow creates a
SKILL.mdsymlink in the tool’s skill directory pointing to your workflow file.
## Usage section.pflow skill list
List all pflow-managed skills across all tools.pflow skill remove
Remove a workflow’s skill from tool directories.WORKFLOW_NAME- Name of the skill to remove (required)
By default, removes from Claude Code. Use multiple flags to remove from multiple tools.
Examples:
Removing a skill only deletes the symlink. The saved workflow in
~/.pflow/workflows/ is unchanged, including any enrichment added during skill save.Workflow requirements
Before publishing a workflow as a skill, you must save it to the global library:Project vs personal skills
Project skills (default) are stored in the current project directory and are typically version-controlled with your project. Use these for project-specific workflows. Personal skills (--personal) are stored in your home directory and are available across all projects. Use these for general-purpose workflows you want everywhere.
Related
- Workflow commands - Save and manage workflows
- Claude Code integration - Set up pflow with Claude Code
- Cursor integration - Set up pflow with Cursor

