procesio-setup
Skill5 starsChanged 3 months agoApache-2.0View on GitHub
Connect this installation to a PROCESIO workspace, so the MCP server and the CLI can reach it. Use on first run, after installing the plugin, when a call fails with auth_required, missing_secrets or no stored credential, when someone asks how to add an API key or a second environment, when switching between PROCESIO environments, or when a tool reports a missing machine prerequisite.
- Installs packages
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-skill-engineerSkill
- procesio-cli-maintainerSkill
- procesio-cliSkill
- procesio-platform-advisorSkill
- sql-server-optimizerSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Every command that needs a secret prompts for it directly, without echoing, when you omit the value.
- Distinctive: line 42
If someone pastes a credential into the conversation anyway, say plainly that it is now in the transcript and should be rotated, then carry …
- Very specific: line 69
Leave --workspace-id out for a personal workspace: the key already resolves to it, so do not ask for a workspace ID there.
- Distinctive: line 131
Add these only when the person needs the feature.
- Distinctive: line 173
Read the error rather than re-running the setup.
- Distinctive: line 185
If a key was minted on one workspace and used against another, it will not work even though both belong to the same account: a key inherits …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Connecting to PROCESIO
New to any of this? PROCESIO is a low-code automation platform for building processes, forms and integrations. procesio-cli is a command-line tool (you run it in a terminal, or an AI agent runs it for you) that drives a PROCESIO workspace from the command line. To reach a workspace it needs a PROCESIO API key: a credential you create in the PROCESIO web app. A PROCESIO API key has TWO parts and you need BOTH - a name/handle (the key's label) and a secret value (the long token) - and you copy each from the PROCESIO UI at the moment you create the key.
Nothing here reaches a PROCESIO workspace until one credential profile exists on this machine. This walks through that, verifies it, and covers the optional extras that individual tools need.
Read this first: never handle the secret yourself
Never ask the person to paste an API key, password or token into the conversation, and never read one back. Anything typed into chat is in the transcript.
Every command that needs a secret prompts for it directly, without echoing, when you omit the value. That prompt belongs to the person, not to you: you print the command, they run it in their own terminal. Do not run it for them, because a prompt you drive is a prompt whose answer passes through you.
The values land in the OS credential store (Windows Credential Manager, macOS Keychain,
Linux keyring) under agents-and-tools:<tool>:<secret>. They are never written to a file
in this repository, and nothing here should ever print one.
If someone pastes a credential into the conversation anyway, say plainly that it is now in the transcript and should be rotated, then carry on with the prompted flow.
The one thing that is required
A PROCESIO credential profile. Without it every procesio_* tool fails; with it, 17 of
the 21 work. Everything below this section is optional and serves a specific feature.
Two kinds, and which one to use is decided by what the person already has:
- API key — the normal choice. A key minted in the PROCESIO UI, sent as a header.
- Username and password — for an account without a key, or where a key cannot be minted.
API key
Give them this to run, with a profile name of their choosing:
python scripts/run-tool.py procesio add-credential --name personal --type apikey --make-defaultA PROCESIO API key has two parts and the CLI needs both: --key is the key's name/handle
(its label in the PROCESIO UI) and --value is the secret token. Omitting both from the
command is deliberate - it then prompts for each without echoing. You get both from the
PROCESIO UI's API-keys page when you create the key.
Leave --workspace-id out for a personal workspace: the key already resolves to it, so do
not ask for a workspace ID there. Add --workspace-id <guid> only to target a specific,
non-personal workspace.
Username and password
python scripts/run-tool.py procesio add-credential --name personal --type userpass --username someone@example.com --make-defaultSame rule: --password is omitted, so it is prompted without echoing.
Installed from the plugin rather than cloned
The plugin runs the procesio-cli package from PyPI through uv, so there is no checkout
and no procesio command on the PATH. The same commands run through uvx:
uvx --from procesio-cli procesio add-credential --name personal --type apikey --make-defaultEverything else on this page works the same way, with uvx --from procesio-cli procesio
in place of python scripts/run-tool.py procesio. Someone who ran
pip install procesio-cli has the procesio command itself and can drop the prefix.
Verify before declaring it done
A stored credential is not a working credential. This hits a live read endpoint:
python scripts/run-tool.py procesio check-authThen confirm it can actually see the workspace:
python scripts/run-tool.py procesio list-processescheck-auth passing while list-processes returns nothing usually means the credential
authenticates against the right account but the wrong workspace. Check --workspace-id.
To see what is stored without revealing anything, list-credentials shows names, types
and workspaces only, and show-credential --name <name> shows one profile's non-secret
fields, with secrets reported only as present or absent.
Environments
Calls go to Main-PROD unless told otherwise. For a client installation or a QA
environment, register it once and bind the credential to it:
python scripts/run-tool.py procesio add-environment --name Acme-QA --web-base https://... --auth-base https://...
python scripts/run-tool.py procesio add-credential --name acme-qa --type apikey --environment Acme-QAlist-environments shows what is registered, which is the default, and which credential
each one is bound to. Individual tool calls can also override per call with
--environment, which is worth reaching for before changing the default.
Optional, per feature
Add these only when the person needs the feature. Each is inert until then, so a first-run setup should not collect them.
| feature | what it needs |
| Building connectors from API docs | a Connector Builder credential |
| Tidying a process canvas | Node.js, plus elkjs |
| Reading or writing a form's code blob | the form-code encryption passphrase |
Connector Builder takes either an API key, or an account login:
python scripts/set-credential.py connector-builder api-keyThat command prompts for the value without echoing. For the login route, store username
and password the same way.
Node and elkjs are machine prerequisites rather than credentials. check-requirements.py
reports what is missing and the install line for each:
python scripts/check-requirements.pyWorth knowing why this is a separate check: these dependencies are imported lazily, so a machine without them still reports the tool ready and still passes the test suite. The failure surfaces at the first real call instead.
The form-code passphrase encrypts a form's Data.code blob:
python scripts/set-credential.py procesio form-code-keyThis one has a sharp edge worth stating before they set it. The passphrase is what decrypts
existing blobs, so changing it makes every form already saved under the old one
undecryptable, and the editing path fails before any write can happen. If that has already
happened, form-set-code --clear is the way back in.
When something still fails
Read the error rather than re-running the setup.
| what comes back | what it means |
missing_secrets | nothing is stored for that tool yet. Store it, above. |
auth_required | a secret is stored but the tool could not use it. |
check-auth fails while a secret is present | the value is present and wrong, or expired, or minted for a different environment. |
| calls succeed but return nothing | authenticated against the right account, wrong workspace. |
A stored secret being present is not the same as it being valid — presence is all an
inventory can see. Probe with check-auth, never by inspecting the store.
If a key was minted on one workspace and used against another, it will not work even though both belong to the same account: a key inherits the permissions of whoever created it, in the place it was created.
What good looks like
Setup is finished when check-auth passes and list-processes returns the workspace the
person expected. Say which profile and which environment that was, so the next session
starts from a known place rather than rediscovering it.
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.

