Add Maia Agent Skills documentation#11203
Conversation
KONRADS098
force-pushed
the
maia-skills-support
branch
from
4b0b1d9 to
930025d
Compare
|
|
||
| ### Other Supported Document Types | ||
|
|
||
| In Studio Pro 11.9, support for enumerations, constants, modules, Java actions, and JavaScript actions was added. In this version, Java actions are read-only; they can be used in microflows and explained. JavaScript actions can only be explained. |
There was a problem hiding this comment.
Suggestion: Should we extend one of the existing tables or add a new table instead of having this very long sentence? I think it will be easier for us to maintain if we use a table. One thing we could do is separate document types from features and group them together that way. Currently you have a capability table on line 26, which includes both document types as well as general Maia features. And then again the same on line 42, which mostly contains features. What do you think? Could we perhaps restructure this?
There was a problem hiding this comment.
One thing we could do is separate document types from features and group them together that way.
I like this idea. The only thing is that if we group the capabilities conceptually, as you suggested, the order will no longer match the navigation menu under Maia Make Capabilities. That’s only a minor drawback, though. In the long run, grouping them conceptually could indeed make future updates easier.
Restructure the capabilities overview into three separate tables: one for supported document types, one for standalone Maia features, and one for general capabilities. This improves clarity by grouping related functionality and making version support easier to track. - Rename section to "Maia Make Capabilities Overview" for consistency - Create "Supported Document Types" subsection with comprehensive table - Create "Maia Features" subsection for standalone features - Consolidate general capabilities into a unified table - Incorporate folder structure support as a capability row - Add "Remarks" column for version-specific notes and limitations
| | [Pages](/refguide/maia-for-pages/) | Generates, modified, and explains pages | Studio Pro 11.8 | | | ||
| | [Microflows](/refguide/maia-for-microflows/) | Generates, modifies, and explains microflows | Studio Pro 11.8 | | | ||
| | [Workflows](/refguide/maia-for-workflows/) | Generates, modifies, and explains workflows | Studio Pro 11.9 | | | ||
| | [OQL](/refguide/maia-for-oql/) | Generates and manages OQL queries | Studio Pro 11.9 | | |
There was a problem hiding this comment.
@petarvukmirovic can it also explain OQL in 11.9? Or was this introduced at a later point?
| | [Microflows](/refguide/maia-for-microflows/) | Generates, modifies, and explains microflows | Studio Pro 11.8 | | | ||
| | [Workflows](/refguide/maia-for-workflows/) | Generates, modifies, and explains workflows | Studio Pro 11.9 | | | ||
| | [OQL](/refguide/maia-for-oql/) | Generates and manages OQL queries | Studio Pro 11.9 | | | ||
| | View entities | Generates and manages view entities. | Studio Pro 11.9 | | |
There was a problem hiding this comment.
@petarvukmirovic Similar question here a1f0350#r3282074396
| | [Workflows](/refguide/maia-for-workflows/) | Generates, modifies, and explains workflows | Studio Pro 11.9 | | | ||
| | [OQL](/refguide/maia-for-oql/) | Generates and manages OQL queries | Studio Pro 11.9 | | | ||
| | View entities | Generates and manages view entities. | Studio Pro 11.9 | | | ||
| | Enumerations | Generates and manages enumerations. | Studio Pro 11.9 | | |
There was a problem hiding this comment.
@Yiyun333 we can also explain the enumerations, that being said, any document that can be generated can also be explained. But, not all documents that can be explained can be generated. Is there a way for us to note this down in a more general way? instead of needing to mention "generate", "modify", "explain" XXX in every entry? Perhaps we could use the remarks to state any deviations from this, e.g. "XXX cannot be modified"
There was a problem hiding this comment.
@KONRADS098 I have this sentence at the beginning of the section: "Maia Make can generate new documents, modify existing documents, and explain app documents and structures through a unified conversational interface." Perhaps we can remove the whole "Description" column for this table and add exceptions as remarks like you said.
There was a problem hiding this comment.
That's an even better suggestion. Would you like to implement the changes or shall I do it?
| | Java actions | Uses Java actions in microflows and explains them. | Studio Pro 11.9 | Read-only; Java actions cannot be generated. | | ||
| | JavaScript actions | Explains and generates JavaScript actions. | Studio Pro 11.9 | Explain-only in Studio Pro 11.9. Generation, adding parameters, and updating the associated JavaScript file available from Studio Pro 11.10. | | ||
| | JavaScript actions | Generates and explains JavaScript actions. | Studio Pro 11.9 | Explain-only in Studio Pro 11.9. Generation, adding parameters, and updating the associated JavaScript file available from Studio Pro 11.10. | | ||
| | Navigation | Generates and updates app-level navigation. | Studio Pro 11.11 | | |
There was a problem hiding this comment.
updates
Should we use consistent wording here, other entries use "modifies"
| | JavaScript actions | Explains and generates JavaScript actions. | Studio Pro 11.9 | Explain-only in Studio Pro 11.9. Generation, adding parameters, and updating the associated JavaScript file available from Studio Pro 11.10. | | ||
| | JavaScript actions | Generates and explains JavaScript actions. | Studio Pro 11.9 | Explain-only in Studio Pro 11.9. Generation, adding parameters, and updating the associated JavaScript file available from Studio Pro 11.10. | | ||
| | Navigation | Generates and updates app-level navigation. | Studio Pro 11.11 | | | ||
| | Menu | Generates and updates menu documents. | Studio Pro 11.11 | | |
There was a problem hiding this comment.
3 participants
No description provided.