Thanks, John — that explanation and workaround were very helpful.
I reconnected the WPVibe connector in ChatGPT’s plugin settings and started a new chat. The connector still exposes the older fixed name enum, which does not include generatepress, so load_skill({ name: "generatepress" }) would still be rejected by client-side schema validation.
However, I confirmed that the workaround works correctly:
load_skill({ query: "generatepress" })
This successfully loaded the dedicated GeneratePress guidance in the new chat.
So the practical workaround is working, but reconnecting the connector did not appear to refresh the exposed name schema. Please let me know if there is any additional connector or workspace information I can provide to help investigate. Thanks again!
