Guidance Needed: Uploading and Testing Custom Skill Files for ODC Mentor

Gowtham

Question

Hi Everyone,

I have been working on creating a set of custom skill files intended to train and guide Mentor in OutSystems Developer Cloud (ODC). The objective is to establish development standards and best practices so that when a user prompts Mentor with requests such as:

Create a Server Action
Create a Client Action
Create an Entity
Create a List Screen
Create a Dashboard
Implement integrations

Mentor should follow the instructions, conventions, and standards defined in the corresponding skill file and generate outputs that align with our organization's development guidelines.

I have already prepared several skill files covering different development artifacts and patterns. However, I am unsure about the following:

Where should these skill files be uploaded in ODC?
How can these files be associated with Mentor?
Is there a recommended format, location, or repository structure for maintaining skill files?
What is the process for testing whether Mentor is actually using the instructions defined in the skill files?
Are there any tools, logs, or validation mechanisms available to verify that the generated output is influenced by the uploaded skill files?
Has anyone successfully implemented and tested custom skill files with Mentor in ODC? If so, could you share your approach and any lessons learned?

My goal is to create a reusable set of standards that ensure consistency across developers, regardless of the prompt wording used when interacting with Mentor.

Any guidance, documentation links, examples, or real-world experiences would be greatly appreciated.

Thank you in advance for your help!

11 Aug

Daniël Kuhlmann

MVP

Hi,
No of what you ask in your six questions is currently possible in ODC.
You would have to copy/past your guidlines in every session with Mentor in Studio.

Regards,

Daniel

13 Aug

Michael de Guzman

Champion

Hi Gowtham,

@Daniël 's right on all six points. There's no upload mechanism, no association step, no logging or validation layer. You're not missing a hidden feature.

I'll add one thing worth knowing before you settle for copy-pasting into every session. OutSystems announced Agent Experience at their ONE conference this year. It's a platform layer that exposes an MCP server, connecting the ODC Enterprise Context Graph to external AI agents like Claude Code. Once that's wired up, the agent reads your live ODC environment directly. Feed it your skill files, and it applies your standards when it generates a Server Action, an Entity, a screen, whatever you're asking for.

As an example, I used it to standardize our CRUD wrappers across a project. Instead of every developer writing their own version of create/read/update/delete logic with slightly different naming and error handling, I fed the agent our wrapper pattern as a skill file. It picked it up and generated new wrappers that actually matched our convention, not just something structurally similar.

It was open to everyone during the conference, but it's back to EAP now. You'll need a partner environment and a request to your Customer Success Manager to get it turned on.

Until that's available to you, Daniel's approach is the right one. Keep the guidelines in a shared doc your team pastes in each session. Manual, but it works.

13 Aug

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.

See the full guidelines