Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
351 changes: 0 additions & 351 deletions ProcessMaker/Mcp/McpSystemSkills.php

This file was deleted.

2 changes: 1 addition & 1 deletion ProcessMaker/Mcp/Processes/ProcessPlanner.php
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@ public function plan(User $user, array $input): array
'ready' => $ready,
'goal' => $goal,
'agent_instructions' => $ready
? 'Blueprint is complete enough to design screens (if needed), then author BPMN and call validate-process before create-process. Load process-creation-rules and only the node skills you need. Use list-users / list-groups if any assignment id is still unclear.'
? 'Blueprint is complete enough to design screens (if needed), then author BPMN and call validate-process before create-process. Follow the pm4-process skill (and the connector skills you need). Use list-users / list-groups if any assignment id is still unclear.'
: 'Do not call create-process yet. Ask the human the open_questions (batch a few related ones). After they answer, call plan-process again with the same goal and filled answer fields. Use list-users and list-groups when discussing assignees so the human can pick real people/groups.',
'open_questions' => $open,
'answered' => $answers,
Expand Down
2 changes: 1 addition & 1 deletion ProcessMaker/Mcp/Screens/ScreenConfigValidator.php
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ public function validate(?array $config, ?string $type = null): array
$warnings[] = $this->issue(
null,
'prefer_vue_component_editor',
'FORM screens should use VueComponentRenderTemplate as the main UI (see screen-creation-rules). Native FormSelectList/FormInput layouts are fragile and often miss required options.',
'FORM screens should use VueComponentRenderTemplate as the main UI (see the pm4-screen skill). Native FormSelectList/FormInput layouts are fragile and often miss required options.',
);
}

Expand Down
6 changes: 3 additions & 3 deletions ProcessMaker/Mcp/Servers/DataConnectorsServer.php
Original file line number Diff line number Diff line change
Expand Up @@ -39,15 +39,15 @@
create-data-connector requires name, type, authtype, and data_source_category_id.
endpoints is a map keyed by purpose; each endpoint needs purpose, method, and url.
Credentials are write-only (not returned by get/list).
Load skill `data-connector-creation-rules`. For BPMN Service Task wiring load `data-connector-in-process`
(implementation `package-data-sources/data-source-task-service`, pm:config dataSource + endpoint).
Follow the `pm4-data-connector` skill from the ProcessMaker Skills repository (`npx skills add processmaker/skills`),
including BPMN Service Task wiring (implementation `package-data-sources/data-source-task-service`, pm:config dataSource + endpoint).

## Collections
Use list-collections before creating one.
create-collection requires name, description, create_screen_id, read_screen_id, update_screen_id
(create those screens via Screens MCP first when missing).
Creating a collection may auto-create a matching Data Connector for `/collections/{id}/records`.
Add demo rows with create-collection-records (skill `collection-test-data`).
Add demo rows with create-collection-records (see the `pm4-collection` skill).
MARKDOWN)]
class DataConnectorsServer extends Server
{
Expand Down
5 changes: 2 additions & 3 deletions ProcessMaker/Mcp/Servers/FlowGenieServer.php
Original file line number Diff line number Diff line change
Expand Up @@ -36,9 +36,8 @@
create-flow-genie requires name, description, and flow_genie_category_id.
config is the agent JSON (instructions, model, provider, output_type, tools, mcp_servers, …).
Secrets (provider_api_key, MCP tokens) are write-only — get/list redact them.
After creating a FlowGenie, wire it into BPMN with Processes MCP skill `process-connector-flowgenie`
(`implementation` `package-ai/processmaker-ai-task`, pm:config `flow_genie_id` + `output_variable`).
Load skill `flowgenie-creation-rules`.
After creating a FlowGenie, wire it into BPMN as described in the `pm4-flow-genie` skill from the ProcessMaker Skills repository
(`npx skills add processmaker/skills`): `implementation` `package-ai/processmaker-ai-task`, pm:config `flow_genie_id` + `output_variable`.
MARKDOWN)]
class FlowGenieServer extends Server
{
Expand Down
6 changes: 3 additions & 3 deletions ProcessMaker/Mcp/Servers/ProcessServer.php
Original file line number Diff line number Diff line change
Expand Up @@ -32,15 +32,15 @@
3. Do not load every skill by default. Follow the system prompt and any skills you loaded.

## Designing a new process
When the request is vague or incomplete, call `plan-process` first (load skill `process-planner`).
When the request is vague or incomplete, call `plan-process` first.
Ask the human the returned `open_questions`. Use `list-users` and `list-groups` so they can pick real assignees / process manager.
Re-call `plan-process` with answers until `ready` is true, then build screens/BPMN.

Use list-processes to search before creating one.
create-process requires name and description; bpmn is optional (empty template if omitted — add a start event before running).
For MCP create-process/update-process use numeric pm:screenRef / pm:scriptRef (list-screens after create-screen). Portable ${screen:title} only resolves via package-plg deploy-process.
For package connectors (email, PDF, Slack, FlowGenie, Decision Task, UiPath, DocuSign, Actions By Email, Data Connector) load `process-node-service-task` then the matching `process-connector-*` / `data-connector-in-process` skill — do not invent `implementation` strings.
For FlowGenie Service Tasks: create/configure the asset via FlowGenies MCP (`create-flow-genie`) first, then set numeric `flow_genie_id` in pm:config (skill `process-connector-flowgenie`).
For BPMN structure, node settings, and package connectors (email, PDF, Slack, FlowGenie, Decision Task, UiPath, DocuSign, IDP, Actions By Email, Data Connector), follow the matching `pm4-*` skill from the ProcessMaker Skills repository (`npx skills add processmaker/skills`, start with `pm4-process`). Do not invent `implementation` strings.
For FlowGenie Service Tasks: create/configure the asset via FlowGenies MCP (`create-flow-genie`) first, then set numeric `flow_genie_id` in pm:config.
Call validate-process before create/update when unsure.
update-process changes only the fields you send.
MARKDOWN)]
Expand Down
4 changes: 2 additions & 2 deletions ProcessMaker/Mcp/Servers/ScreenServer.php
Original file line number Diff line number Diff line change
Expand Up @@ -35,8 +35,8 @@
type is usually FORM or DISPLAY.
config is the screen builder page array; every control in page.items must include `"inspector": []` (or a real inspector list) or the designer crashes.
create/update reject configs with empty FormSelectList options (missing optionsList).
Build coherent Vue SFCs only (VueComponentRenderTemplate). Implement file upload, catalog selects (Collections via apiClient), and signature pads inside the Vue component — do not add native FileUpload / FormSelectList / SignaturePad siblings. Load skills screen-creation-rules and screen-vue-fields.
When refactoring an existing traditional screen into Vue, also load skill screen-refactor-parity: preserve every field/variable on request data; keep instructional help (FormImage diagrams, how-to HTML, tip alerts, helper links) restyled/condensed as needed but not omitted; review each native SB control config and reimplement the same behavior in the Vue SFC (validation, visibility, options, events — UI-only keys like colors/CSS may change for redesign); inventory nested screens and recreate them as shared Vue child SFCs reused by every parent that nested them; reimplement calcs and invoke backend scripts / Data Connectors from the Vue SFC (Vue-only screens do not fire SB computed/watchers — leave those arrays empty). Respect original conditionalHide/readonly — do not show always-hidden data-only fields as editable controls.
New FORM/DISPLAY screens are built as a Vue Component Editor mount (VueComponentRenderTemplate with a thin contentVue); do not add native FileUpload / FormSelectList / SignaturePad siblings.
For the full rules (control shape, component registration, domain fields, refactor parity), follow the `pm4-screen` skill from the ProcessMaker Skills repository (`npx skills add processmaker/skills`).
update-screen changes only the fields you send.
delete-screen cannot remove a default screen.
MARKDOWN)]
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@

#[Name('create-collection-records')]
#[Title('Create Collection Records')]
#[Description('Adds one or more test/demo records to a collection. Pass records (array of data objects) or data (single object). Load skill collection-test-data.')]
#[Description('Adds one or more test/demo records to a collection. Pass records (array of data objects) or data (single object). See the pm4-collection skill.')]
class CreateCollectionRecordsTool extends RespondingTool
{
public function handle(Request $request, CollectionCatalog $catalog): Response|ResponseFactory
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@

#[Name('create-collection')]
#[Title('Create Collection')]
#[Description('Creates a collection. Requires name, description, and create/read/update screen ids. May auto-create a Data Connector for records. Load skill collection-creation-rules first.')]
#[Description('Creates a collection. Requires name, description, and create/read/update screen ids. May auto-create a Data Connector for records. See the pm4-collection skill.')]
class CreateCollectionTool extends RespondingTool
{
public function handle(Request $request, CollectionCatalog $catalog): Response|ResponseFactory
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@

#[Name('create-data-connector')]
#[Title('Create Data Connector')]
#[Description('Creates a REST/SOAP Data Connector. Requires name, type, authtype, data_source_category_id. Load skill data-connector-creation-rules first.')]
#[Description('Creates a REST/SOAP Data Connector. Requires name, type, authtype, data_source_category_id. See the pm4-data-connector skill.')]
class CreateDataConnectorTool extends RespondingTool
{
public function handle(Request $request, DataConnectorCatalog $catalog): Response|ResponseFactory
Expand Down
2 changes: 1 addition & 1 deletion ProcessMaker/Mcp/Tools/FlowGenies/CreateFlowGenieTool.php
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@

#[Name('create-flow-genie')]
#[Title('Create FlowGenie')]
#[Description('Creates a FlowGenie asset. Requires name, description, flow_genie_category_id. Prefer validate-flow-genie then set config.instructions. Load skill flowgenie-creation-rules.')]
#[Description('Creates a FlowGenie asset. Requires name, description, flow_genie_category_id. Prefer validate-flow-genie then set config.instructions. See the pm4-flow-genie skill.')]
class CreateFlowGenieTool extends RespondingTool
{
public function handle(Request $request, FlowGenieCatalog $catalog): Response|ResponseFactory
Expand Down
2 changes: 1 addition & 1 deletion ProcessMaker/Mcp/Tools/Processes/ValidateProcessTool.php
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@

#[Name('validate-process')]
#[Title('Validate Process')]
#[Description('Validates BPMN without saving. Pass bpmn XML and/or an existing process id. Returns ok, errors, and warnings (schema + semantic checks). Load process-validation skill for the full checklist.')]
#[Description('Validates BPMN without saving. Pass bpmn XML and/or an existing process id. Returns ok, errors, and warnings (schema + semantic checks). See the pm4-process skill (verify.md) for the full checklist.')]
#[IsReadOnly]
#[IsIdempotent]
class ValidateProcessTool extends ProcessTool
Expand Down
2 changes: 1 addition & 1 deletion ProcessMaker/Mcp/Tools/Screens/ValidateScreenTool.php
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@

#[Name('validate-screen')]
#[Title('Validate Screen')]
#[Description('Validates a Screen Builder config without saving. Pass config and optional type, and/or an existing screen id. Returns ok, errors, and warnings (select options, Vue component wiring). Load screen-creation-rules for the checklist.')]
#[Description('Validates a Screen Builder config without saving. Pass config and optional type, and/or an existing screen id. Returns ok, errors, and warnings (select options, Vue component wiring). See the pm4-screen skill for the checklist.')]
#[IsReadOnly]
#[IsIdempotent]
class ValidateScreenTool extends ScreenTool
Expand Down
55 changes: 0 additions & 55 deletions ProcessMaker/Mcp/skills/collection-creation-rules.md

This file was deleted.

46 changes: 0 additions & 46 deletions ProcessMaker/Mcp/skills/collection-test-data.md

This file was deleted.

87 changes: 0 additions & 87 deletions ProcessMaker/Mcp/skills/data-connector-creation-rules.md

This file was deleted.

Loading
Loading