ps-best-practices
Skill1 starsChanged 5 months agoMITView on GitHub
Suggest Process Street workflow design best practices — naming, field types, conditional logic, stops/approvals, assignments, due dates, automation, organization. Use when the user asks how to design a good workflow, wants recommendations, or how to improve their process design.
In this repository12 other files it gives its agents.
- data-setSkill
- demo-buildSkill
- chrome-recording-to-workflowSkill
- logic-rulesSkill
- ps-auditSkill
- ps-buildSkill
- ps-editSkill
- ps-organizeSkill
- workflow-designSkill
- integration-scopingSkill
- ps-searchSkill
- ps-helpSkill
The file
Files
Process Street best-practice guidance
Give concrete, opinionated workflow design advice grounded in reference/best-practices.md (read it before answering — it's the source of truth for this skill).
How to use it
- General "how should I design X" questions → synthesize the relevant principles from
reference/best-practices.mdinto a short, specific recommendation for their use case. Don't dump the whole guide; pull the 3–5 points that matter here. - "Is my workflow good?" → that's an audit. Hand off to the
ps-auditskill (it scores an existing workflow against the same guide). - "Build me one that follows best practices" → give a quick design sketch, then offer the
ps-buildskill.
Anchor every answer in these themes (full detail in the reference)
- Naming & structure — outcome-based names, 6–15 verb-named steps, one process per workflow, real-sequence order, front-load data capture.
- Field types — use the right type (Select/Date/Number/Members/Email), not free text everywhere; short forms per step; help text on ambiguous fields.
- Control flow — conditional logic to hide the irrelevant; stops/approvals only where they earn their friction; configure approval subject tasks.
- Accountability — an owner per task (assignment rules); dynamic due dates over fixed offsets.
- Automation — Code/AI tasks and webhooks to kill manual re-keying; Data Sets for shared option lists.
- Polish & organization — branded first step, media where it beats text; folders by team/function.
End with the 10-point scorecard from the reference when the user wants a checklist.
Be honest about limits
Required-field flag, brand theming (colors/cover/fonts), org/SSO, and deep native-integration config are set in the Process Street UI, not the API.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.