Branch: refs/heads/xwiki-openproject-skill Home: https://github.com/xwiki/xwiki-dev-llm Commit: 139971b28feaa6bee16c2b16508644997f955dc0 https://github.com/xwiki/xwiki-dev-llm/commit/139971b28feaa6bee16c2b16508644... Author: Vincent Massol <[email protected]> Date: 2026-09-04 (Fri, 04 Sep 2026) Changed paths: M README.md M xwiki/okf/index.md A xwiki/skills/xwiki-openproject/SKILL.md A xwiki/skills/xwiki-openproject/references/rest-api.md Log Message: ----------- [Misc] Add a skill for op.xwiki.org work packages * Add the `xwiki-openproject` skill: search, view, create, update and comment on OpenProject work packages in op.xwiki.org over REST API v3, with `references/rest-api.md` holding the calls. * Make the `/form` dry run the required step before every write. The form runs the same validation as the real call and persists nothing, so it is what turns "guess a payload and POST it" into "show the developer the resolved fields, then commit". * Discover project, type, status, priority and version ids at call time rather than naming any: they are instance configuration, and OKF's rule is that volatile facts get a verify recipe, not a cached value. * Record the two behaviours that otherwise mislead: a form reports a rejected field as HTTP 200 with `_embedded.validationErrors` and no `_links.commit`, and `status` is workflow-gated, so its allowed set can hold only the status already set. * Note that the instance's MCP server is read-only below OpenProject 17.8, so the skill says to prefer an MCP write tool once one shows up and to fall back to REST otherwise. Every recipe in the reference was run against op.xwiki.org (reads, plus writes validated through the form endpoints, which create nothing). Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications