From Process Street Workflow Toolkit
Audit and optimize an existing Process Street workflow — score it against best practices, surface issues, and optionally apply the fixes. Use when the user wants to review, improve, tighten, or optimize a workflow.
How this skill is triggered — by the user, by Claude, or both
Slash command
/workflow-toolkit:ps-auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze a workflow, score it, recommend improvements grounded in `reference/best-practices.md`, and (with consent) apply the fixes via `ps-edit`.
Analyze a workflow, score it, recommend improvements grounded in reference/best-practices.md, and (with consent) apply the fixes via ps-edit.
CLI: python3 "${CLAUDE_PLUGIN_ROOT}/scripts/process_street.py" <command> (plugin) or scripts/process_street.py (repo). Needs PROCESS_STREET_API_KEY.
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/process_street.py" template-export <workflowId>
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/process_street.py" template-rules <workflowId> --resolve
If you only have a name, process_street.py workflows to find the ID.
Use the scorecard in reference/best-practices.md. For each step and field, check:
Select/Date/Number belongs? fields no one needs? missing required fields?Give a short report:
[quick win] (apply now via API), [redesign] (needs restructuring), or [UI-only] (required flag, theming, integrations).Ask which to implement. For the API-doable ones, build an edit plan and hand off to the ps-edit flow (draft → preview → publish → rollback). Re-export to confirm. List any UI-only items the user must do themselves.
Almost every structural fix is API-applicable: change field types, add logic, add due-date/assignment rules, add/remove steps and fields, add content. Only required-field flagging, theming, org settings, and deep integrations are UI-only.
npx claudepluginhub process-street/workflow-toolkit --plugin workflow-toolkitGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.