agentleFS
Sign inStart free
process-streetprocess-street/ps-skills/skills/build/ps-organize/SKILL.md

ps-organize

Skill1 starsChanged 5 months agoMITView on GitHub

Organize a Process Street library into a clean folder structure — list folders and workflows, propose a structure, create folders, and re-file workflows. Use when the user wants to organize, tidy, or restructure their workflows/folders.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep active templates separate from archived/draft ones.

    line 24
  2. Distinctive:

    Don't over-nest — one clear level is usually enough.

    line 26
  3. Distinctive:

    Create any missing folders:

    line 32
  4. Distinctive:

    Do moves one at a time and confirm each.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Organize the Process Street library

Bring order to a Process Street workspace: propose a sensible folder structure and move workflows into it.

CLI: python3 "${CLAUDE_PLUGIN_ROOT}/scripts/process_street.py" <command> (plugin) or scripts/process_street.py (repo). Needs PROCESS_STREET_API_KEY.

1. Survey what exists

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/process_street.py" folders     # current folders
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/process_street.py" workflows   # all workflows

Group the workflows by what they're for (Sales, Customer Success, Finance, HR, Ops…) and note obvious duplicates, drafts, or stale templates.

2. Propose a structure

Recommend folders by team or function (not by date or person), per reference/best-practices.md:

  • Keep active templates separate from archived/draft ones.
  • Consistent, outcome-based names.
  • Don't over-nest — one clear level is usually enough.

Show the user the proposed folder list and which workflows go where. Get a yes before changing anything.

3. Create folders & re-file

Create any missing folders:

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/process_street.py" folder-create --name "Customer Success"   # note the returned folder ID

Move a workflow into a folder by updating its folder (the API does not return a workflow's current folder/share settings, so --folder-id is required and unspecified sharing flags fall back to defaults — pass them if the workflow has non-default sharing):

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/process_street.py" update-workflow <workflowId> --folder-id <folderId> [--name "..."] [--share-level Run]

Do moves one at a time and confirm each. After re-filing, list folders/workflows again to verify the new structure.

Notes

  • There's no bulk "move" endpoint — re-file workflows individually with update-workflow.
  • You can also set folder permissions: folder-permissions <folderId> --permissions '[{"email":"team@co.com","accessLevel":"Edit"}]'.
  • To delete an empty folder, use the Process Street UI (folder deletion isn't wired into this CLI). Re-filing its workflows first is the safe path.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free